[instruments] updated README and test plan for widgets (aces#6484)

Resolves aces#6437

modules/dashboard/test/TestPlan.md

@@ -23,34 +23,31 @@
    page with the following Selection Filter: Site not set and Pending Approval set to 'Yes'. 
    Check that you are taken to that page (with the Selection Filter correctly set) when you
    click on the task.
-   [Automate Test on Travis_CI]
-6. Verify that if a user has 'Data entry' permission, the reports menu is displayed and the number of incomplete
-   forms show in the tasks list.
    [Automate Test]
-7. Verify that the issue tracker panel is accessible if and only if a user has the 'issue_tracker_reporter'
+6. Verify that the issue tracker panel is accessible if and only if a user has the 'issue_tracker_reporter'
    or the 'issue_tracker_developer' permission.
    [Automate Test on Travis_CI]
-8. Verify that if a user has 'User Management / Survey Participant Management' permission, the number of pending
+7. Verify that if a user has 'User Management / Survey Participant Management' permission, the number of pending
    account approvals is displayed in the My Task panel. This should be the number of entries in the User Account
    page with the following Selection Filter: Site set to the user's site and Pending Approval set to 'Yes'. The
    Site displayed will be 'All user sites'. Check that you are taken to that page (with the Selection Filter
    correctly set) when you click on the task.
    [Automate Test on Travis_CI]
-9. Verify that a user with 'Violated Scans: View all-sites Violated Scans' permission has a task with the number
+8. Verify that a user with 'Violated Scans: View all-sites Violated Scans' permission has a task with the number
    of violated scans displayed. This is the number of entries on the MRI Violated Scans page. The Site displayed will
    always be 'All'. Check that clicking on the task takes you to the Violated Scans page.
    [Automate Test on Travis_CI]
-10. Verify that if a user has the 'View and upload files in Document Repository' or 'Delete files in Document Repository'
-11. Check that if a document notification occurred since the last login, it is labeled as 'New' in the Document
+9. Verify that if a user has the 'View and upload files in Document Repository' or 'Delete files in Document Repository'
+10. Check that if a document notification occurred since the last login, it is labeled as 'New' in the Document
     Repository panel.
     [Automate Test]
-12. Check that a 'New' notification is not labeled 'New' anymore after login in again.
+11. Check that a 'New' notification is not labeled 'New' anymore after login in again.
     [Manual Test]
-13. Check performance on the raisin bread dataset: make sure the dashboard page displays within 5 seconds or less.
+12. Check performance on the raisin bread dataset: make sure the dashboard page displays within 5 seconds or less.
     [Manual Test]
-14. When there are no candidates registered (i.e. first time install), the system should display a message indicating
+13. When there are no candidates registered (i.e. first time install), the system should display a message indicating
     that there are no candidates in the DB yet instead of showing the candidates chart.
     [Manual Test]
-15. When there are no scans done, the system should display a message indicating that no scans were made instead of
+14. When there are no scans done, the system should display a message indicating that no scans were made instead of
     showing the scans chart.     
     [Manual Test]

modules/instruments/README.md

@@ -41,3 +41,8 @@ instruments, but does not load through this module.
 
 `bvl_feedback` threads for an instrument may be created on this
 module.
+
+### Dashboard Widget
+
+The total `Incomplete forms` will be shown inside the Dashboard widget, 
+named "My Tasks" and with a link redirecting to statistics/statistics_site.

modules/instruments/test/TestPlan.md

@@ -43,3 +43,18 @@ instrument for that candidate. Enter a date (same a step 4) posterior to the DoD
 11. Verify Validity flags are functioning for instruments.
     - **Validity:** can be marked as “Valid”, “Questionable”, or “Invalid”. Whether or not this flag is shown for an instrument is by the boolean $ValidityEnabled. Whether the field is required before flagging an instrument as complete is determined by $ValidityRequired.
     - You can test the forgoing flags by switching the corresponding boolean of the test instruments to either `true` or `false`.
+
+### Visit the Dashboard module.
+   1. Dashboard Widget - "My Tasks" for Incomplete forms 
+      - Ensure the total of Incomplete forms correspond with the correct 
+            number of candidates inside the statistics/statistics_site module.
+      - Click on the total number of Incomplete forms and check if redirection
+            to the statistics/statistics_site module succeeds.
+
+### Visit the Candidate Dashboard module.
+   1. Candidate Widget - "Behavioural Data" for Candidate instruments entry.
+      - Ensure the appropriate visit labels are visible for the candidate. 
+      - The visit status, subproject status, site, date of visit, and age should be shown.
+      - Clicking on a visit should redirect to the instrument_list module for the candidate.
+      - Test making a new Time Point for a candidate and assign an instrument to the time point. 
+        The Behavioural Data widget should update accordingly.