-
Notifications
You must be signed in to change notification settings - Fork 10
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 Case Type Filter to Case Search #10569
Comments
Pre-refinement
|
Test Cases1) External non-logged in user accesses the Case Search page; New dropdown for Case type is displayed.
Expected Results:
2) External non-logged in user types in a Case Title/Petitioner name, makes a selection for Case type, and clicks Search; Results are filtered appropriately.
Expected Results:
*Repeat this test with all of the different case types to ensure that search results are filtered appropriately 3) External non-logged in user searches for a sealed case using a combination of case title and case type filter; Standard "No matches found" message displays
Expected Results:
4) Logged in Private Practitioner accesses the Case Search page; New dropdown for Case type is displayed.
Expected Results:
5) Private Practitioner types in a Case Title/Petitioner name, makes a selection for Case type, and clicks Search; Results are filtered appropriately.
Expected Results:
*Repeat this test with all of the different case types to ensure that search results are filtered appropriately 6) Private Practitioner searches for a sealed case that they do not have access to using a combination of case title and case type filter; Standard "No matches found" message displays
Expected Results:
7) Private Practitioner searches for a sealed case that they have access to using a combination of case title and case type filter; Case displays in the search results.
Expected Results:
8) Repeat test cases 4-7 with an IRS and DOJ practitioner.
9) Internal Court user accesses the Case Search page; New dropdown for Case type is displayed.
Expected Results:
10) Court user types in a Case Title/Petitioner name, makes a selection for Case type, and clicks Search; Results are filtered appropriately.
Expected Results:
*Repeat this test with all of the different case types to ensure that search results are filtered appropriately 11) Court User searches for a sealed case using a combination of case title and case type filter; Case displays in the search results.
Expected Results:
12) Regression - Ensure no Disclosure ("D") cases display in the search results
Expected Results:
13) Repeat test cases 1-12 on a mobile device
14) Terminal user accesses the Case Search page; New dropdown for Case type is displayed.
Expected Results:
15) Terminal user types in a Case Title/Petitioner name, makes a selection for Case type, and clicks Search; Results are filtered appropriately.
Expected Results:
*Repeat this test with all of the different case types to ensure that search results are filtered appropriately 16) Terminal user searches for a sealed case using a combination of case title and case type filter; Standard "No matches found" message displays
Expected Results:
|
Currently we do not have "Small" or "Small CDP Lien/Levy" as case types. How should we handle this? |
Based on discussion with Chris on Feb 20, we will be handling Case types "Small" and "Small CDP Lien/Levy" as part of another future story. |
As a user of case search, so that I can refine my search criteria, I need to be able to select the case type as an optional criterion in the Case Search.
Currently the "Search By Name" Case Search can only use the petitioner's filing location and/or filing date as additional search criteria. We would like to add the Case Type as an additional search criterion. For this functionality, we would like to add only the case types which result in the docket number having a letter suffix appended as potential search criteria.
The case types we want to allow as criteria:
Pre-Conditions
#10502
Acceptance Criteria
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:
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
Engineering
efcms-local.json
, 3 local s3 files corresponding to that docketEntryId have been added toweb-api/storage/fixtures/s3/noop-documents-local-us-east-1
test
environment if prod-like data is required. Otherwise deployed to anyexperimental
environment.staging
environment.The text was updated successfully, but these errors were encountered: