Skip to content

Commit

Permalink
[conflict_resolver] Update test plan and README to test widgets
Browse files Browse the repository at this point in the history
Fixes aces#6434
  • Loading branch information
driusan committed Apr 28, 2020
1 parent 3ddf0df commit bf1ed49
Show file tree
Hide file tree
Showing 2 changed files with 27 additions and 0 deletions.
3 changes: 3 additions & 0 deletions modules/conflict_resolver/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,3 +66,6 @@ If the `conflicts_unresolved` table somehow becomes out of sync
with the data in LORIS, the `tools/recreate_conflicts.php` script
can be used to re-compare single and double data entry values
and repopulate the `conflicts_unresolved` table.

The conflict resolver registers modules on the dashboard and the
`candidate_profile` dashboard.
24 changes: 24 additions & 0 deletions modules/conflict_resolver/test/TestPlan.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,3 +44,27 @@
- Also check and make sure that the instrument and its corresponding DDE are updated accordingly
- Ensure if Date_taken is changed, the candidate age in the instrument is updated accordingly
- Make sure the scoring_fields are re-calculated in the given instrument once the conflict is resolved

## Dashboard Widget

1. Go to the LORIS dashboard.
- Ensure that the "My Tasks" "My Tasks" on the LORIS dashboard has a "Data entry conflicts"
item
- Ensure that the `access_all_profiles` permission changes the label from "Sites: All"
to "Sites: User sites" and the number associated with the task is updated accordingly.
2. Clicking on the entry in the task in the dashboard should navigate to the conflict resolver
module

## Candidate Profile Widget
1. Go to the `candidate_profile` module through the "Candidate -> Access Profile (beta)" and
access a candidate with at least 1 conflict.
- Ensure that there is a "Unresolved Conflicts" card if the user has the `conflict_resolver`
permission
- Ensure that the card does *not* appear (but no other cards are affected) after removing
the `conflict_resolver` permission
2. With appropriate permission, ensure that there is a bar graph of the number of conflicts per instrument,
grouped by visit.
- Ensure that clicking a bar in the bar graph brings you to the conflict resolver module
with the filters preset to filter for that instrument and visit
- Ensure that clicking on an instrument in the legend takes you to the conflict resolver
with the menu filter preset for that instrument (but no filter for visit)

0 comments on commit bf1ed49

Please sign in to comment.