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

Add Docket Suffix to Custom Case Report Results #10571

Open
33 tasks
cholly75 opened this issue Dec 17, 2024 · 1 comment
Open
33 tasks

Add Docket Suffix to Custom Case Report Results #10571

cholly75 opened this issue Dec 17, 2024 · 1 comment

Comments

@cholly75
Copy link
Collaborator

As a Court employee, so that I can see at a glance whether a docket number is a specific type of case, I need suffixes added to the docket numbers on the Custom Case Report results.

This is part of our effort to make suffix displays uniform across the system, particular in search/report functionality.

Pre-Conditions

Acceptance Criteria

  • Docket numbers displayed on the Custom Case Report results display the appropriate suffixes when present.

Notes

Tasks

Test Cases

Story Definition of Ready (updated on 12/23/22)

The following criteria must be met in order for the user story to be picked up by the Flexion development team.
The user story must:

  • Is framed in business/user need, the value has been addressed.
  • Includes acceptance criteria
  • Has been refined
  • Pre conditions have been satisfied.

Process:
Flexion developers and designers will test if the story meets acceptance criteria and test cases in Flexion dev and staging environments (“standard testing”). If additional acceptance criteria or testing scenarios are discovered while the story is in progress, a new story should be created, added to the backlog and prioritized by the product owner.

Definition of Done (Updated 5-19-22)

Product Owner

UX

  • Business test scenarios have been refined to meet all acceptance criteria
  • Usability has been validated
  • Wiki has been updated (if applicable)
  • Story has been tested on a mobile device (for external users only)

Engineering

  • Automated test scripts have been written, including visual tests for newly added PDFs.
  • Field level and page level validation errors (front-end and server-side) integrated and functioning.
  • Verify that language for docket record for internal users and external users is identical.
  • New screens have been added to pa11y scripts.
  • All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html.
  • READMEs, other appropriate docs, and swagger/APIs fully updated.
  • UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required).
  • Interactors should validate entities before calling persistence methods.
  • Code refactored for clarity and to remove any known technical debt.
  • If new docket entries have been added as seed data to efcms-local.json, 3 local s3 files corresponding to that docketEntryId have been added to web-api/storage/fixtures/s3/noop-documents-local-us-east-1
  • Acceptance criteria for the story has been met.
  • If there are special instructions in order to deploy into the next environment, add them as a comment in the story.
  • If the work completed for the story requires a reindex without a migration, or any other special deploy steps, apply these changes to the following flexion branches:
    • experimental1
    • experimental2
    • experimental3
    • experimental4
    • experimental5
    • experimental6
    • develop
  • Reviewed by UX on a deployed environment.
  • Reviewed by PO on a deployed environment. Can be deployed to the Court's test environment if prod-like data is required. Otherwise deployed to any experimental environment.
  • Deployed to the Court's staging environment.
@cholly75 cholly75 moved this to Product Backlog/Bugs in US Tax Court Board Dec 17, 2024
@cholly75 cholly75 moved this from Product Backlog/Bugs to Needs Test Cases in US Tax Court Board Dec 18, 2024
@ttlenard
Copy link
Collaborator

Test Cases

1) Court user runs the custom case report; Results list displays docket number suffixes.

  • Log in as a court user
  • Click on the Reports menu
  • Select Custom Case Report
  • Leave the default filters, and click Run Report button

Expected Results:

  • NEW FUNCTIONALITY - The docket number column now displays the docket number suffix if there is one on all pages of results.

2) Court user applies filters to the Custom Case Report; Results list displays docket number suffixes.

  • Continuing from the previous test
  • Apply various filters to the report
  • Click the Run Report button

Expected Results:

  • NEW FUNCTIONALITY - The docket number column now displays the docket number suffix if there is one on all pages of results.

*Repeat this test with various filters

3) Court user exports the results list to csv; Docket number suffixes are displayed in the csv and match the results in the UI.

  • Continuing from the previous test
  • Export the results
  • Open the CSV file
  • Review the data, and compare it with the data in the UI

Expected Results:

  • NEW FUNCTIONALITY - The docket number column in the CSV file now displays the docket number suffix if there is one and matches the data in the UI.

4) Repeat the tests above with all Court users

  • This test passes

@cholly75 cholly75 moved this from Needs Test Cases to Ready for Engineering in US Tax Court Board Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Ready for Engineering
Development

No branches or pull requests

2 participants