Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reprocessed Modal: Submission History #3343

Merged
merged 15 commits into from
Dec 17, 2024
Merged

Reprocessed Modal: Submission History #3343

merged 15 commits into from
Dec 17, 2024

Conversation

elipe17
Copy link

@elipe17 elipe17 commented Dec 6, 2024

Summary of Changes

How to Test

List the steps to test the PR
These steps are generic, please adjust as necessary.

cd tdrs-frontend && docker-compose up --build
cd tdrs-backend && docker-compose up
  1. Open http://localhost:3000/ and sign in.
  2. Submit some files.
  3. Note that the Reprocessed button isn't visible in submission history
  4. Reparse some/all of the files you submitted
  5. You should now see the Reprocessed button is visible in submission history for the files you reparsed
  6. Click the button and you should see a modal with the latest reparse date and explanation

In the raft environment use the following STT, year, and quarter to easily view the changes: Arizona Year:2021 and Quarter:1

Deliverables

More details on how deliverables herein are assessed included here.

Deliverable 1: Accepted Features

Checklist of ACs:

  • Submitted on/by columns are combined
  • Dialog has a close button
  • Dialog contains paragraph explainer on reprocessing
  • Dialog contains date time stamp for last reprocessing event
  • Dialog opens when trigger in Submitted on column is clicked
  • UX has been pinged to ticket knowledge center revisions to capture these changes
  • Testing Checklist has been run and all tests pass
  • README is updated, if necessary

Deliverable 2: Tested Code

  • Are all areas of code introduced in this PR meaningfully tested?
    • If this PR introduces backend code changes, are they meaningfully tested?
    • If this PR introduces frontend code changes, are they meaningfully tested?
  • Are code coverage minimums met?
    • Frontend coverage: [insert coverage %] (see CodeCov Report comment in PR)
    • Backend coverage: [insert coverage %] (see CodeCov Report comment in PR)

Deliverable 3: Properly Styled Code

  • Are backend code style checks passing on CircleCI?
  • Are frontend code style checks passing on CircleCI?
  • Are code maintainability principles being followed?

Deliverable 4: Accessible

  • Does this PR complete the epic?
  • Are links included to any other gov-approved PRs associated with epic?
  • Does PR include documentation for Raft's a11y review?
  • Did automated and manual testing with iamjolly and ttran-hub using Accessibility Insights reveal any errors introduced in this PR?

Deliverable 5: Deployed

  • Was the code successfully deployed via automated CircleCI process to development on Cloud.gov?

Deliverable 6: Documented

  • Does this PR provide background for why coding decisions were made?
  • If this PR introduces backend code, is that code easy to understand and sufficiently documented, both inline and overall?
  • If this PR introduces frontend code, is that code easy to understand and sufficiently documented, both inline and overall?
  • If this PR introduces dependencies, are their licenses documented?
  • Can reviewer explain and take ownership of these elements presented in this code review?

Deliverable 7: Secure

  • Does the OWASP Scan pass on CircleCI?
  • Do manual code review and manual testing detect any new security issues?
  • If new issues detected, is investigation and/or remediation plan documented?

Deliverable 8: User Research

Research product(s) clearly articulate(s):

  • the purpose of the research
  • methods used to conduct the research
  • who participated in the research
  • what was tested and how
  • impact of research on TDP
  • (if applicable) final design mockups produced for TDP development

- Add ReprocessedModal component
- Use new component for submission history tables
@elipe17 elipe17 added frontend dev raft review This issue is ready for raft review a11y-review PR is ready for accessibility review labels Dec 6, 2024
@elipe17 elipe17 self-assigned this Dec 6, 2024
Copy link

codecov bot commented Dec 6, 2024

Codecov Report

Attention: Patch coverage is 77.41935% with 7 lines in your changes missing coverage. Please review.

Project coverage is 91.57%. Comparing base (08c346a) to head (defdbea).
Report is 9 commits behind head on develop.

Files with missing lines Patch % Lines
.../components/SubmissionHistory/ReprocessedModal.jsx 60.00% 4 Missing ⚠️
tdrs-frontend/src/components/Modal/Modal.jsx 50.00% 2 Missing ⚠️
...ponents/SubmissionHistory/TotalAggregatesTable.jsx 80.00% 0 Missing and 1 partial ⚠️
Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #3343      +/-   ##
===========================================
- Coverage    91.61%   91.57%   -0.05%     
===========================================
  Files          298      298              
  Lines         8520     8526       +6     
  Branches       621      621              
===========================================
+ Hits          7806     7808       +2     
- Misses         602      606       +4     
  Partials       112      112              
Flag Coverage Δ
dev-backend 91.42% <100.00%> (ø)
dev-frontend 92.65% <76.66%> (-0.35%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
tdrs-backend/tdpservice/data_files/serializers.py 96.29% <100.00%> (ø)
tdrs-frontend/src/components/Reports/Reports.jsx 87.61% <100.00%> (+0.22%) ⬆️
...mponents/SubmissionHistory/CaseAggregatesTable.jsx 92.85% <100.00%> (ø)
...components/SubmissionHistory/SubmissionHistory.jsx 100.00% <100.00%> (ø)
...ntend/src/components/SubmissionHistory/helpers.jsx 80.95% <100.00%> (ø)
...ponents/SubmissionHistory/TotalAggregatesTable.jsx 69.23% <80.00%> (ø)
tdrs-frontend/src/components/Modal/Modal.jsx 70.96% <50.00%> (-1.45%) ⬇️
.../components/SubmissionHistory/ReprocessedModal.jsx 60.00% <60.00%> (-27.50%) ⬇️

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ae340de...defdbea. Read the comment docs.

@elipe17 elipe17 marked this pull request as ready for review December 6, 2024 19:49
@reitermb reitermb added the Deploy with CircleCI-raft Deploy to https://tdp-frontend-raft.app.cloud.gov through CircleCI label Dec 6, 2024
@elipe17 elipe17 added Deploy with CircleCI-raft Deploy to https://tdp-frontend-raft.app.cloud.gov through CircleCI and removed Deploy with CircleCI-raft Deploy to https://tdp-frontend-raft.app.cloud.gov through CircleCI labels Dec 10, 2024
Copy link

@victoriaatraft victoriaatraft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screenshot 2024-12-10 at 10 44 14 AM LGTM from an a11y perspective. @elipe17. Is it possible for the modal to also close of the user selects the grayed out area in addition to the "close" button?

- Fixed bug in Modal that caused it to crash when tabbing or shift tabbing with only one button
@elipe17 elipe17 added Deploy with CircleCI-raft Deploy to https://tdp-frontend-raft.app.cloud.gov through CircleCI and removed Deploy with CircleCI-raft Deploy to https://tdp-frontend-raft.app.cloud.gov through CircleCI labels Dec 11, 2024
Copy link

@jtimpe jtimpe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works as written! I have a suggestion regarding the structuring of the components that I would like your thoughts on before I approve, but I'll let you decide whether to move forward with it or not.

Copy link

@raftmsohani raftmsohani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@ADPennington ADPennington added Deploy with CircleCI-qasp Deploy to https://tdp-frontend-qasp.app.cloud.gov through CircleCI and removed Deploy with CircleCI-raft Deploy to https://tdp-frontend-raft.app.cloud.gov through CircleCI labels Dec 16, 2024
@@ -474,4 +486,42 @@ describe('SubmissionHistory', () => {
}
}
)

it('Shows Reprocessed button', () => {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@elipe17 do we need more tests here to capture the following scenarios:

  • reprocessing tribal TANF file
  • reprocessing SSP file
  • no reprocessing

Asking because I noticed that reprocessing indicators are not appearing for tribal TANF and SSP files. evidence below.

Screenshot 2024-12-16 124333
Screenshot 2024-12-16 123500

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be the same exact logic regardless of TANF, SSP, Tribal. I just tested SSP locally and it was fine. Let me checkout the deployed env

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ADPennington I just tested in the Raft env since it is still deployed there and it is working as expected for TANF, SSP, and Tribal. Maybe we can deploy this back to qasp when you are ready and check it out together?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you @elipe17 -- one thing i forgot to mention is that I was testing aggregate and stratum files for SSP and tribal TANF.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Roger. I tested active, closed, and aggregate for TANF. Active and aggregate for SPP. Only active for Tribal. Let me know when you are ready to test it out and we can hop on a call or work async via the deployment

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@elipe17 re-deploying now

Copy link
Collaborator

@ADPennington ADPennington left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changes requested re: reprocessing on tribal and SSP files.

@ADPennington ADPennington added Blocked Label for Pull Requests that are currently blocked by a dependency Deploy with CircleCI-qasp Deploy to https://tdp-frontend-qasp.app.cloud.gov through CircleCI raft review This issue is ready for raft review and removed Deploy with CircleCI-qasp Deploy to https://tdp-frontend-qasp.app.cloud.gov through CircleCI QASP Review labels Dec 16, 2024
@elipe17 elipe17 added the Deploy with CircleCI-qasp Deploy to https://tdp-frontend-qasp.app.cloud.gov through CircleCI label Dec 17, 2024
@ADPennington
Copy link
Collaborator

@ttran-hub -- do you have some time today for a11y testing for this PR?

we need a11y testing on data file page > submission history tab, in the areas highlighted in the screenshot below. This branch is in qasp env.

Screenshot 2024-12-17 114759

@klinkoberstar can you remind me -- is there a release note associated with this?

@ttran-hub
Copy link
Collaborator

@ttran-hub -- do you have some time today for a11y testing for this PR?

we need a11y testing on data file page > submission history tab, in the areas highlighted in the screenshot below. This branch is in qasp env.

Screenshot 2024-12-17 114759

@klinkoberstar can you remind me -- is there a release note associated with this?

a111y LGTM!

@ttran-hub ttran-hub closed this Dec 17, 2024
@ADPennington ADPennington reopened this Dec 17, 2024
Copy link
Collaborator

@ADPennington ADPennington left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀 🚀 🚀

@ADPennington ADPennington added Ready to Merge and removed raft review This issue is ready for raft review Blocked Label for Pull Requests that are currently blocked by a dependency Gov A11y Review Deploy with CircleCI-qasp Deploy to https://tdp-frontend-qasp.app.cloud.gov through CircleCI labels Dec 17, 2024
@elipe17 elipe17 merged commit 4598fa1 into develop Dec 17, 2024
24 checks passed
@elipe17 elipe17 deleted the 3271-reparse-dialog branch December 17, 2024 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Reprocessed on enhancement (3014 follow-on)
8 participants