Process completed with exit code 1.

Judge assignment to attorney and judge Cannot view assigned cases queue of attorneys in other teams attempt to view other team's attorney's cases fails visiting other attorney's assigned cases page Failure/Error: expect(page).to have_content("Additional access needed") expected to find text "Additional access needed" in "CaseflowQueue\n | Switch product\nSearch cases\nCSSID4179036 (VACO)\nAssign 0 Cases for CSSID4179035\nCases to Assign (0)\nSwitch views\nUnable to load cases\nAttorney is not part of the specified judge's team.\nSend feedback" Shared Example Group: "accessing assigned queue for attorney in other team" called from ./spec/feature/queue/judge_assignment_spec.rb:142

Judge assignment to attorney and judge Cannot view assigned cases queue of attorneys in other teams attempt to view other team's attorney's cases succeeds after user is added to SpecialCaseMovementTeam Failure/Error: expect(page).to have_content("#{attorney_one.full_name}'s Cases") expected to find text "Moe Syzlak's Cases" in "CaseflowQueue\n | Switch product\nSearch cases\nCSSID4194048 (VACO)\nAssign 0 Cases for CSSID4194047\nCases to Assign (0)\nSwitch views\nUnable to load cases\nAttorney is not part of the specified judge's team.\nSend feedback"

Process completed with exit code 1.

User organization When user is admin of the organization Adds and removes users from the organization Failure/Error: expect(page).to_not have_content(user_without_role.full_name) expected not to find text "without role" in "CaseflowQueue\nSearch cases\nCSSID4316307 (VACO)\nTeam management for Test organization\nAdd new team members\n with role (CSSID4316308)\nwithout role (CSSID4316309)\n\nEdit current team members\nAdd / Remove admin rights: Determines which users have access to the team queue and the ability to manage the team membership.\nRemove from team: Remove a user from this team.\nFilter by username or CSS ID\nLauren Roth (CSSID4316307)\nRemove admin rightsRemove from team\nSend feedback"

ColocatedTask attorney assigns task to vlj support staff, vlj returns it to attorney after completion should return attorney task to active state Failure/Error: expect(page).to have_content("You have assigned an administrative action (#{action})") expected to find text "You have assigned an administrative action (POA clarification)" in "CaseflowQueue\nSearch cases\nCSSID4496673 (VACO)\nSubmit admin action\nSelect the type of administrative action you'd like to assign:\nPOA clarification\nProvide instructions and context for this action\nnote\n+ Add another action\nCancel\nAssign Action\nSend feedback"

Process completed with exit code 1.

NonComp Report Page Form submission should submit several types of status reports successfully and generate CSVs for each submission Failure/Error: expect(number_of_rows).to eq(17) expected: 17 got: 5 (compared using ==)

Process completed with exit code 1.

Case Assignment flows given a valid legacy appeal and an attorney user adds colocated tasks Failure/Error: expect(page).to have_content("You have assigned an administrative action (#{selected_opt_0})") expected to find text "You have assigned an administrative action (Extension)" in "CaseflowQueue\nSearch cases\nCSSID4475417 (VACO)\nSubmit admin action\nSelect the type of administrative action you'd like to assign:\nExtension\nProvide instructions and context for this action\nVPXjfSu SyZwVKj RUJVzt qXkcX uKI\n+ Add another action\nCancel\nAssign Action\nSend feedback"

CaseMovementTeam task actions during Quality Review produces error and user can't reassign to attorney Failure/Error: expect(page).to have_content("Error assigning tasks") expected to find text "Error assigning tasks" in "CaseflowQueue\n | Switch product\nSearch cases\nSANFORDBVAM (VACO)\nYour cases\nSwitch views\nAssigned (0)On hold (0)Completed\nCases assigned to you:\nViewing 0-0 of 0 total\nCase Details\nTasks\nTypes\nDocket\nDays Waiting\n\nVeteran Documents\nViewing 0-0 of 0 total\nSend feedback"

Process completed with exit code 1.

Attorney checkout flow given a valid ama appeal submits draft decision Failure/Error: expect(page).to have_content(COPY::JUDGE_CHECKOUT_DISPATCH_SUCCESS_MESSAGE_TITLE % appeal.veteran_full_name) expected to find text "Thank you for reviewing Bob Smithfeeney's decision." in "CaseflowError 500\nMenu\nSomething went wrong.\nIf you continue to see this page, please contact the Caseflow team via the VA Enterprise Service Desk at 855-673-4357 or by creating a ticket via YourIT.\nError code:\nSend feedback"

Process completed with exit code 1.

BVA Dispatch Return Flow An appeal at BVA Dispatch is sent back Failure/Error: expect(page).to have_content(COPY::JUDGE_CHECKOUT_DISPATCH_SUCCESS_MESSAGE_TITLE % appeal.veteran_full_name, wait: 5) expected to find text "Thank you for reviewing Dorothy Slezak's decision." in "CaseflowError 500\nMenu\nSomething went wrong.\nIf you continue to see this page, please contact the Caseflow team via the VA Enterprise Service Desk at 855-673-4357 or by creating a ticket via YourIT.\nError code:\nSend feedback"

Task queue JudgeTask when it was created from a QualityReviewTask behaves like create an admin action should be able to be sent to VLJ support staff Failure/Error: expect(page).to have_content(format(COPY::ADD_COLOCATED_TASK_CONFIRMATION_TITLE, "an", "action", action)) expected to find text "You have assigned an administrative action (IHP)" in "CaseflowQueue\nSearch cases\nCSSID4171748 (VACO)\nSubmit admin action\nSelect the type of administrative action you'd like to assign:\nIHP\nProvide instructions and context for this action\nPlease complete this task\n+ Add another action\nCancel\nAssign Action\nSend feedback" Shared Example Group: "create an admin action" called from ./spec/feature/queue/task_queue_spec.rb:908

Admin UI user is a Case Distro Algorithm Control admin the lever control page operates correctly Failure/Error: expect(page).to have_field(ama_direct_reviews_field, with: "123") expected to find visible field "ama_direct_review_docket_time_goals" that is not disabled with value "123" but there were no matches. Also found "", which matched the selector but not all filters. Expected value to be "123" but was "363"

Process completed with exit code 1.

Task queue JudgeTask when it was created from a BvaDispatchTask should display an option of Ready for Dispatch Failure/Error: expect(page).to have_content(COPY::JUDGE_CHECKOUT_DISPATCH_SUCCESS_MESSAGE_TITLE % appeal.veteran_full_name) expected to find text "Thank you for reviewing Bob Smithbaumbach's decision." in "CaseflowError 500\nMenu\nSomething went wrong.\nIf you continue to see this page, please contact the Caseflow team via the VA Enterprise Service Desk at 855-673-4357 or by creating a ticket via YourIT.\nError code:\nSend feedback"

Task queue JudgeTask when it was created from a BvaDispatchTask behaves like create an admin action should be able to be sent to VLJ support staff Failure/Error: expect(page).to have_content(format(COPY::ADD_COLOCATED_TASK_CONFIRMATION_TITLE, "an", "action", action)) expected to find text "You have assigned an administrative action (IHP)" in "CaseflowQueue\nSearch cases\nCSSID4202776 (VACO)\nSubmit admin action\nSelect the type of administrative action you'd like to assign:\nIHP\nProvide instructions and context for this action\nPlease complete this task\n+ Add another action\nCancel\nAssign Action\nSend feedback" Shared Example Group: "create an admin action" called from ./spec/feature/queue/task_queue_spec.rb:1024

Task queue JudgeTask judge user's queue table view should be able to add admin actions from case details Failure/Error: expect(page).to have_content(format(COPY::ADD_COLOCATED_TASK_CONFIRMATION_TITLE, "an", "action", action)) expected to find text "You have assigned an administrative action (IHP)" in "CaseflowQueue\nSearch cases\nCSSID4220795 (VACO)\nSubmit admin action\nSelect the type of administrative action you'd like to assign:\nIHP\nProvide instructions and context for this action\nPlease complete this task\n+ Add another action\nCancel\nAssign Action\nSend feedback"

Judge checkout flow given an AMA appeal that is selected for quality review prevents appeal dispatch when judge performs checkout again Failure/Error: expect(page).to have_content(COPY::JUDGE_CHECKOUT_DISPATCH_SUCCESS_MESSAGE_TITLE % appeal.veteran_full_name) expected to find text "Thank you for reviewing Lashaunda O'conner's decision." in "CaseflowError 500\nMenu\nSomething went wrong.\nIf you continue to see this page, please contact the Caseflow team via the VA Enterprise Service Desk at 855-673-4357 or by creating a ticket via YourIT.\nError code:\nSend feedback"

Judge checkout flow given a valid ama appeal with single issue starts dispatch checkout flow Failure/Error: expect(page).to have_content(COPY::JUDGE_CHECKOUT_DISPATCH_SUCCESS_MESSAGE_TITLE % appeal.veteran_full_name) expected to find text "Thank you for reviewing Bob Smithweber's decision." in "CaseflowError 500\nMenu\nSomething went wrong.\nIf you continue to see this page, please contact the Caseflow team via the VA Enterprise Service Desk at 855-673-4357 or by creating a ticket via YourIT.\nError code:\nSend feedback"

Judge checkout flow given a valid ama appeal with single issue starts dispatch checkout flow Failure/Error: expect(page).to have_content(COPY::JUDGE_CHECKOUT_DISPATCH_SUCCESS_MESSAGE_TITLE % appeal.veteran_full_name) expected to find text "Thank you for reviewing Bob Smithhills's decision." in "CaseflowError 500\nMenu\nSomething went wrong.\nIf you continue to see this page, please contact the Caseflow team via the VA Enterprise Service Desk at 855-673-4357 or by creating a ticket via YourIT.\nError code:\nSend feedback"

Judge checkout flow given a valid legacy appeal with single issue where work product is draft decision starts dispatch checkout flow Failure/Error: expect(page).to have_content(COPY::JUDGE_CHECKOUT_DISPATCH_SUCCESS_MESSAGE_TITLE % appeal.veteran_full_name) expected to find text "Thank you for reviewing Bob Smith's decision." in "CaseflowError 500\nMenu\nSomething went wrong.\nIf you continue to see this page, please contact the Caseflow team via the VA Enterprise Service Desk at 855-673-4357 or by creating a ticket via YourIT.\nError code:\nSend feedback"

Judge checkout flow when an acting judge is checking out an AMA appeal allows the acting judge to complete judge checkout Failure/Error: expect(page).to have_content(COPY::JUDGE_CHECKOUT_DISPATCH_SUCCESS_MESSAGE_TITLE % appeal.veteran_full_name) expected to find text "Thank you for reviewing Bob Smithbeatty's decision." in "CaseflowError 500\nMenu\nSomething went wrong.\nIf you continue to see this page, please contact the Caseflow team via the VA Enterprise Service Desk at 855-673-4357 or by creating a ticket via YourIT.\nError code:\nSend feedback"

Judge checkout flow when an acting judge is checking out a legacy appeal starts dispatch checkout flow Failure/Error: expect(page).to have_content(COPY::JUDGE_CHECKOUT_DISPATCH_SUCCESS_MESSAGE_TITLE % appeal.veteran_full_name) expected to find text "Thank you for reviewing Bob Smith's decision." in "CaseflowError 500\nMenu\nSomething went wrong.\nIf you continue to see this page, please contact the Caseflow team via the VA Enterprise Service Desk at 855-673-4357 or by creating a ticket via YourIT.\nError code:\nSend feedback"

SCM Team access to judge movement features Non-SCM user should not see judge assign queue page if they are not the judge logged in user is some user visits 'Assign' view Failure/Error: expect(page).to have_content(COPY::ACCESS_DENIED_TITLE) expected to find text "Additional access needed" in "CaseflowQueue\nSearch cases\nCSSID4392296 (VACO)\nAssign 0 Cases for CSSID4392290\nCases to Assign (0)\nCases to Assign\nSelect a user\nAssign 0 cases\nRequest more cases\nViewing 0-0 of 0 total\nSelect\nCase Details\nTypes\nDocket\nIssues\nDays Waiting\n\nVeteran Documents\nViewing 0-0 of 0 total\nSend feedback"

SCM Team access to judge movement features Non-SCM user should not see judge assign queue page if they are not the judge logged in user is attorney on the team visits 'Assign' view Failure/Error: expect(page).to have_content("Additional access needed") expected to find text "Additional access needed" in "CaseflowQueue\nSearch cases\nCSSID4405307 (VACO)\nAssign 0 Cases for CSSID4405303\nCases to Assign (0)\nCases to Assign\nSelect a user\nAssign 0 cases\nRequest more cases\nViewing 0-0 of 0 total\nSelect\nCase Details\nTypes\nDocket\nIssues\nDays Waiting\n\nVeteran Documents\nViewing 0-0 of 0 total\nSend feedback"

SCM Team access to judge movement features Non-SCM user should not see judge assign queue page if they are not the judge logged in user is attorney on the team with judge role visits 'Assign' view Failure/Error: expect(page).to have_content("Additional access needed") expected to find text "Additional access needed" in "CaseflowQueue\nSearch cases\nCSSID4418319 (VACO)\nAssign 0 Cases for CSSID4418315\nCases to Assign (0)\nCases to Assign\nSelect a user\nAssign 0 cases\nRequest more cases\nViewing 0-0 of 0 total\nSelect\nCase Details\nTypes\nDocket\nIssues\nDays Waiting\n\nVeteran Documents\nViewing 0-0 of 0 total\nSend feedback"

SCM Team access to judge movement features SCM user can view judge's queue with both ama and legacy case Failure/Error: expect(page).to have_content("Assign 2 Cases for #{judge_one.css_id}") expected to find text "Assign 2 Cases for CSSID4431327" in "CaseflowQueue\nSearch cases\nCSSID4431330 (VACO)\nAssign 0 Cases for CSSID4431327\nCases to Assign (0)\nSwitch views\nCases to Assign\nSelect a user\nAssign 0 cases\nRequest more cases\nViewing 0-0 of 0 total\nSelect\nCase Details\nTypes\nDocket\nIssues\nDays Waiting\n\nVeteran Documents\nViewing 0-0 of 0 total\nSend feedback"

SCM Team access to judge movement features SCM user can view judge's queue can perform the same case movement actions as a judge on ama appeals Failure/Error: expect(page).to have_content("Assign 1 Cases for #{judge_one.css_id}") expected to find text "Assign 1 Cases for CSSID4444339" in "CaseflowQueue\nSearch cases\nCSSID4444342 (VACO)\nAssign 0 Cases for CSSID4444339\nCases to Assign (0)\nSwitch views\nCases to Assign\nSelect a user\nAssign 0 cases\nRequest more cases\nViewing 0-0 of 0 total\nSelect\nCase Details\nTypes\nDocket\nIssues\nDays Waiting\n\nVeteran Documents\nViewing 0-0 of 0 total\nSend feedback"

SCM Team access to judge movement features SCM user can view judge's queue can perform the same case movement actions as a judge on legacy appeals Failure/Error: click_on(legacy_appeal.veteran_file_number) Capybara::ElementNotFound: Unable to find link or button "444440300"

Metrics::V2::LogsController pdf_page_render_time_in_ms Feature toggle enabled create a metric for pdf_page_render_time_in_ms Failure/Error: expect(metric).to be_present # New metric is created expected `nil.present?` to return true, got false

Process completed with exit code 1.

Users management page When marking a user inactive allow a BVA Admin to toggle a user's status Failure/Error: find("div", class: "cf-select__option", text: active_user.full_name).click Capybara::Ambiguous: Ambiguous match, found 3 elements matching visible css "div" with text "Lauren Roth" with classes [cf-select__option]

Process completed with exit code 1.

Schedule Veteran For A Hearing with an authorized user with enable_time_slots feature disabled with schedule direct to video/virtual feature enabled behaves like scheduling an AMA hearing Can create multiple admin actions and reassign them Failure/Error: expect(page).to have_content( format( COPY::ADD_COLOCATED_TASK_CONFIRMATION_TITLE, "2", "actions", [HearingAdminActionIncarceratedVeteranTask.label, HearingAdminActionContestedClaimantTask.label].join(", ") ) ) expected to find text "You have assigned 2 administrative actions (Veteran is incarcerated, Contested claimant issue)" in "CaseflowQueue\n | Switch product\nSearch cases\nBVATWARNER (VACO)\nSubmit admin action\nSelect the type of administrative action you'd like to assign:\nVeteran is incarcerated\nProvide instructions and context for this action\nIncarcerated veteran task instructions\nRemove this action\nSelect the type of administrative action you'd like to assign:\nContested claimant issue\nProvide instructions and context for this action\nContested claimant task instructions\nRemove this action\n+ Add another action\nCancel\nAssign Action\nSend feedback" Shared Example Group: "scheduling an AMA hearing" called from ./spec/feature/hearings/schedule_veteran/build_hearsched_spec.rb:1066

Schedule Veteran For A Hearing with an authorized user with enable_time_slots feature disabled with schedule direct to video/virtual feature enabled behaves like scheduling an AMA hearing Schedule Veteran for a video hearing with admin actions that can be put on hold and completed Failure/Error: expect(page).to have_content("You have assigned an administrative action") expected to find text "You have assigned an administrative action" in "CaseflowQueue\n | Switch product\nSearch cases\nBVATWARNER (VACO)\nSubmit admin action\nSelect the type of administrative action you'd like to assign:\nVeteran is incarcerated\nProvide instructions and context for this action\nAction 1\n+ Add another action\nCancel\nAssign Action\nSend feedback" Shared Example Group: "scheduling an AMA hearing" called from ./spec/feature/hearings/schedule_veteran/build_hearsched_spec.rb:1066

Schedule Veteran For A Hearing with an authorized user with enable_time_slots feature enabled behaves like scheduling an AMA hearing Can create multiple admin actions and reassign them Failure/Error: expect(page).to have_content( format( COPY::ADD_COLOCATED_TASK_CONFIRMATION_TITLE, "2", "actions", [HearingAdminActionIncarceratedVeteranTask.label, HearingAdminActionContestedClaimantTask.label].join(", ") ) ) expected to find text "You have assigned 2 administrative actions (Veteran is incarcerated, Contested claimant issue)" in "CaseflowQueue\n | Switch product\nSearch cases\nBVATWARNER (VACO)\nSubmit admin action\nSelect the type of administrative action you'd like to assign:\nVeteran is incarcerated\nProvide instructions and context for this action\nIncarcerated veteran task instructions\nRemove this action\nSelect the type of administrative action you'd like to assign:\nContested claimant issue\nProvide instructions and context for this action\nContested claimant task instructions\nRemove this action\n+ Add another action\nCancel\nAssign Action\nSend feedback" Shared Example Group: "scheduling an AMA hearing" called from ./spec/feature/hearings/schedule_veteran/build_hearsched_spec.rb:1101

Schedule Veteran For A Hearing with an authorized user with enable_time_slots feature enabled behaves like scheduling an AMA hearing Schedule Veteran for a video hearing with admin actions that can be put on hold and completed Failure/Error: expect(page).to have_content("You have assigned an administrative action") expected to find text "You have assigned an administrative action" in "CaseflowQueue\n | Switch product\nSearch cases\nBVATWARNER (VACO)\nSubmit admin action\nSelect the type of administrative action you'd like to assign:\nVeteran is incarcerated\nProvide instructions and context for this action\nAction 1\n+ Add another action\nCancel\nAssign Action\nSend feedback" Shared Example Group: "scheduling an AMA hearing" called from ./spec/feature/hearings/schedule_veteran/build_hearsched_spec.rb:1101

Process completed with exit code 1.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

api/v2/appeals /api/v2/appeals get successful returns a 200 response Skipped: No reason given

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

ClaimHistoryService.build_events with filters days waiting filter equal to number of days should only return events for tasks that match the days waiting filter Skipped: Flakey test

The process '/usr/bin/git' failed with exit code 128

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

NonComp Reviews Queue with an existing organization filtering reviews by appeal type Skipped: No reason given

NonComp Reviews Queue with an existing organization filtering reviews by issue type Skipped: No reason given

NonComp Reviews Queue Issue Type filtering and sorting edge cases The Issue type column should orderable and filterable at the same time Skipped: No reason given

Establish Claim - ARC Dispatch As a caseworker For a full grant When there is an existing 070 EP Assigning it to complete the claims establishment Skipped: Test is hanging in GHA

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

IntakeStartValidator#validate when BGS shows a station conflict sets error_code "veteran_not_modifiable" when BGS shows a station conflict Skipped: Flaky test

IntakeStartValidator#validate when BGS shows a station conflict for an Appeal intake user is on the BVA Intake team sets a veteran_not_modifiable error code Skipped: Flaky test

The process '/usr/bin/git' failed with exit code 128

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues behaves like it_should_respond_with_legacy_present should respond with legacy_appeals_present Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues behaves like it_should_respond_with_associated_request_issues should respond with the associated request issues Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues behaves like it_should_respond_with_same_multiple_decision_issues_per_request_issue should respond with the same multiple decision issues per request issue Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_number_of_paginated_issues should only show number of request issues listed in the paginates_per value on first page Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_remaining_issues should only show remaining request issues on next page Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_page_1_when_page_0 should show page 1 when attempting to get page 0 Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_default_to_page_1 should default to page 1 Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_first_page_if_page_negatvie should show the first page if page is negative Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_last_page_if_page_larger_than_total should show last page if page larger than total Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_correct_total_number_of_pages_and_max_request_issues_per_page_on_per_change should show correct total number of pages and max request issues per page on per change Skipped: Flakey test

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

BgsPowerOfAttorney record expirations by_file_number record is expired Skipped: Test is flaky

BgsPowerOfAttorney record expirations by_file_number record is not expired Skipped: Test is flaky

BgsPowerOfAttorney.find_or_create_by_claimant_participant_id when concurrent calls cause a race condition does not raise an error on unique constraint violation Skipped: Test is flaky

BgsPowerOfAttorney.find_or_create_by_file_number when concurrent calls cause a race condition does not raise an error on unique constraint violation Skipped: Test is flaky

The process '/usr/bin/git' failed with exit code 128

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

FetchAllActiveLegacyAppealsJob#find_and_create_appeal_state_for_active_legacy_appeals when there are both OPEN & CLOSED Legacy Appeals in the database only OPEN Legacy Appeal records will be added to the Appeal States table Skipped: Flaky test

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

PushPriorityAppealsToJudgesJob.distribute_non_genpop_priority_appeals using Automatic Case Distribution module should only distribute the ready priority cases tied to a judge Skipped: Temporarily skipped with xit

PushPriorityAppealsToJudgesJob.distribute_non_genpop_priority_appeals using By Docket Date Distribution module without using Docket Levers should only distribute the ready priority cases tied to a judge Skipped: Temporarily skipped with xit

PushPriorityAppealsToJudgesJob.distribute_non_genpop_priority_appeals using By Docket Date Distribution module using Excluding Appeals by Docket Type and Priority from Automatic Case Distribution levers all Exluding levers turned to Include should distribute the ready priority cases Skipped: Temporarily skipped with xit

PushPriorityAppealsToJudgesJob.distribute_non_genpop_priority_appeals using By Docket Date Distribution module using Excluding Appeals by Docket Type and Priority from Automatic Case Distribution levers all Exluding levers turned to Exclude should not distribute the ready priority cases Skipped: Temporarily skipped with xit

The process '/usr/bin/git' failed with exit code 128

No files were found with the provided path: ./tmp/capybara. No artifacts will be uploaded.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Hearing Schedule Daily Docket for RO ViewHearSched User cannot view docket notes Skipped: Flaky test

BgsShareErrorFixJob BGS::ShareError RIU when EPE has established_at date clears the BGS::ShareError on the RIU Skipped: flaky test

BgsShareErrorFixJob BGS::ShareError RIU when EPE does not have established_at date does not clear the BGS::ShareError on the RIU Skipped: flaky test

BgsShareErrorFixJob BGS::ShareError RIU when the RIU does not have the BGS::ShareError does not attempt to clear the error Skipped: flaky test

The process '/usr/bin/git' failed with exit code 128

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

Case details attorney case details view veteran records have been merged and Veteran has multiple active phone numbers in SHARE access the appeal's case details Skipped: This test fails in GHA but not locally

MailTasks Hearing Postponement Request Mail Task mark as complete ruling is granted schedule immediately AMA appeal unscheduled hearing sends proper notifications Skipped: test is failing in local env and github actions

MailTasks Hearing Postponement Request Mail Task mark as complete ruling is granted schedule immediately AMA appeal scheduled hearing sends proper notifications Skipped: test is failing in local env and github actions

MailTasks Hearing Postponement Request Mail Task mark as complete ruling is granted schedule immediately Legacy appeal unscheduled hearing sends proper notifications Skipped: test is failing in local env and github actions

MailTasks Hearing Postponement Request Mail Task mark as complete ruling is granted schedule immediately Legacy appeal scheduled hearing sends proper notifications Skipped: test is failing in local env and github actions