Ticket: MB-61 - Add Petitions Area to the Judicial Viewer
...
Understanding the Flow
Steps:
User Logs In: The user logs into accesses the Benchmark Web Application.
Access Navigates to Judicial Viewer: The user navigates to the Judicial Viewer and opens a specific case in the Judicial Viewer.
Check System Checks User Rights:
The system checks verifies if the user has the "View Petitions" right.
It also The system checks the Court Type ID in
tblCourtTypePresentationto ensure that the if the court type of the case allows petitions to be displayed.
Display Displays Petitions Section:
If IIf the logged in user has the necessary right to view petitions and the court type supports of the case is configured to display petitions, the Petitions Area is displayedthe petition section should be added to the summary screen.
The Petitions section can be either collapsed or expanded depending on user settings.
...
Web view case detail should be the same as window case detail view with Petition tab like mentioned below.
...
User Interaction:
...
The user can expand or collapse the Petitions section.
...
The user can view detailed petition information (e.g., petition type, date filed, status, etc.).
...
Petitions are visible, default to collapsed or expanded, and can specify the order they see the petition section in the summary screen.
The user can customize the order in which the Petitions section appears in the summary screen.
Expected Fields in the Petitions Section:
Petition Type
Petition Date
Disposition
Disposition Date.
Save Settings: Users can customize the visibility, collapsed/expanded state, and order of the Petitions section in the Case Summary settings.
...
Test Cases
ORDER | SECTION | VISIBLE | COLLAPSED | |
|---|---|---|---|---|
12 | Petitions |
|
|
|
13 | Motions |  | |  |
To be added to below Case Summary :
...
Web view case detail should be the same as window case detail view with Petition tab like mentioned below.
...
Use Case 1: View Petitions
Primary Actor: Case Manager.
Precondition: The user has the "View Petitions" right, and the court type allows petitions.
Trigger: The user navigates to the Judicial Viewer and opens a case.
Main Success Flow:
The system checks if the user 's rights and court type configurationhas the "View Petitions" right.
The system checks if the court type is configured to show petitions.
The Petitions Area Section is displayed based on the user’s settings (either collapsed or expanded as per user settings).
The user views the petition details, including Petition Type, Petition Date, Disposition, Disposition Date, and any other relevant fields.
Alternate Flow:
If the user lacks the "View Petitions" right or the court type does not allow petitions, the Petitions section is not displayed.
Use Case 2: Edit Petitions
Primary Actor: Case Manager
Precondition: The user has update access to the case.
Trigger: The user navigates to the Petitions Area and clicks to edit.
Main Success Flow:
The user selects a petition and edits the details.
The system validates the input data.
The changes are saved and reflected in the petition details.
Alternate Flow:
If the user does not have update access, the system does not allow edits.
3. Test Cases for MB-61
Test Case 1: Verify Display of Petitions Area
Test Step: Log in as a user with the "View Petitions" right and navigate to a case.
Expected Result: The Petitions Area is visible in the case summary.
Negative Test: Log in as a user without the "View Petitions" right. The Petitions Area should not be displayed.
Test Case 2: Verify Edit Functionality for Petitions
Test Step: Log in as a user with update access and navigate to a case.
Expected Result: The user can modify the petition details and save changes.
Test Case 3: Verify Configuration of Petitions Area
Test Step: Adjust the Petitions section’s visibility, collapsed/expanded state, and order in the Case Summary settings.
- Expected Result: The configuration is applied correctly, and the Petitions Area reflects the chosen settings
Section will not be displayed.