[WEBCLIENT-166] Printable Query Report Feature Created: 17/Dec/15  Updated: 25/Jan/16  Resolved: 31/Dec/15

Status: Closed
Project: i2b2 Web Client
Component/s: None
Affects Version/s: None
Fix Version/s: 1.7.07

Type: New Feature Priority: Major
Reporter: Nich Assignee: Janice Donahoe
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

i2b2 Sponsored Project/s:
i2b2 Web Client
Testing Notes: TEST STATUS: Completed
COMPLETION DATE: 12/31/2015

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
TEST DATE: 12/31/2015
TESTED BY: Janice Donahoe
BUILD NUMBER: 1.7.07.0009
TEST STATUS: Passed Testing


CLIENTS TESTED:
     i2b2 Web Client

ENVIRONMENTS TESTED:
     Browsers: Chrome, Firefox, Internet Explorer, and Safari
     Databases: Not applicable for this test
     Client OS: Windows and Macintosh


TEST COMMENTS:
Tested this with the latest i2b2 Web Client and it appears to be working correctly.


SCENARIOS TESTED
1. Obfuscated User. Verified the following:
     -- Clicking on the Query Reports tab displays the query information.
     -- The totals all display the obfuscated results and NOT the real results.
     -- The graphs display the obfuscated totals and NOT the real results.
     -- Clicking on the Print Report button opens the Print window.
     -- The report prints correctly with all the appropriate data.

2. Aggregated User. Verified the following:
     -- Clicking on the Query Reports tab displays the query information.
     -- The totals all display the correct results and NOT obfuscated results.
     -- The graphs display the correct totals and NOT obfuscated results.
     -- Clicking on the Print Report button opens the Print window.
     -- The report prints correctly with all the appropriate data.

Scenario 2 is repeated with users who have the following access levels:
       Limited Data Set User
       De-identified User
       Protected Access User

3. Test with a user who is a Manager to verify in the query information/summary section of the report, the "query was performed by" displays the correct user name. Making sure it does not display the person running the report (in this case the manager).

NOTE: Scenario 3 is done because managers can view queries run by another user. All the other items in Scenario 2 are also verified when logged in as a manger.


ISSUES FOUND:
No issues were found.


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
TEST DATE: 12/29/2015
TESTED BY: Janice Donahoe
BUILD NUMBER: 1.7.07.0008
TEST STATUS: Failed Testing


CLIENTS TESTED:
     i2b2 Web Client


ENVIRONMENTS TESTED:
     Browsers: Chrome, Firefox, Internet Explorer, and Safari
     Databases: Not applicable for this test
     Client OS: Windows and Macintosh


TEST COMMENTS:
Tested this with the latest i2b2 Web Client and found the report is not working correctly for obfuscated users. (See ISSUES FOUND).


SCENARIOS TESTED
1. Obfuscated User. Verified the following
     -- Clicking on the Query Reports tab displays the query information.
     -- The totals all display the obfuscated results and NOT the real results.
     -- The graphs display the obfuscated totals and NOT the real results.


ISSUES FOUND:
When an obfuscated user views the report, the totals will all display undefined # instead of the obfuscated results.

See comment entered on 12/29/2015 for more details on the issue.


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Test Date: 12/22/2015
Tested By; Reeta Metta
Build Number:1.7.07
Test Status: Completed (Passed Testing)
Clients Tested :
     i2b2 Web Client
     Environments Tested :
     Browsers: Chrome, Firefox, Internet Explorer, and Safari
     Databases: Not applicable for this test
     Client OS: Windows, Mac
Test Comments:
Working as expected
ISSUES FOUND:None
Participant/s:

 Description   
A new report feature to display and print the query information has been made available in version 1.7.07 of the i2b2 Web Client. This new report will include the following:

1. Query Definition - The criteria defined when the query was run.
2. Query Results - The results that were returned when the query was run.

In the results section of the report, the breakdown will display in a table format while the associated graphs will display below them.

The report can be accessed by clicking on the new tab that will appear in the Query Status view section that displays below the Query Tool. This new tab will be labeled "Query Report" and will display next to the View Graphs tab.

The report can be printed by clicking on the Print Report button that displays at the top of the report.



 Comments   
Comment by Janice Donahoe [ 29/Dec/15 ]
This is not working for obfuscated users. When an obfuscated clicks on the Query Report tab, the counts will all be "undefined #" instead of the obfuscated result. Also, the graphs that display below the tables are blank; presumably this is because there are no counts available in the report.

This report should work the same way as the other query tabs in that the counts should display the obfuscated results with a +/- whatever number is defined in the configuration/parameters. In the demo data this +/- number is 3. The graphs should also display the obfuscated results the same as the Graph Results tab.


STEPS TO REPRODUCE:

1. Log into the Web Client as an obfuscated user.
2. Run a query in which all the breakdowns are selected (if you have a previous query that meets this criteria you can use this instead).
3. Once the query completes the Graph Results tab should be active.
4. Make note of how the obfuscated results appear correctly on this tab.
5. Click on the Query Report tab.
6. Notice all the counts are "undefined #" and the graphs are empty.
Comment by Janice Donahoe [ 25/Jan/16 ]
On 01/22/2016, the 1.7.07 Release was made available at the following locations.

https://www.i2b2.org/software/
 - zip files for release 1.7.07 are available on this site. This includes both the code and documentation.

https://github.com/i2b2
 - source code has been tagged with v1.7.07.
Generated at Mon Apr 06 07:46:17 UTC 2020 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.