Page tree
Skip to end of metadata
Go to start of metadata

Application - Researcher

#Test caseExpected ResultNotes
1.Verify that user is able to log in the DSA-Researcher application after entering valid credentials

 

  • URL should launch properly
  • Error is not expected after entering valid credentials
2.Verify that Topic and History sections are available on the left side of the page

  • Topics page should also be the landing page after logging in. User can switch to 'History' tab by clicking it
  • Topics created by currently logged in user should appear on this page
3.Under Topics tab: Verify that user is able to create a new topic after clicking 'New' button available at the bottom right corner of the page and entering required information

  • New Button should always be clickable.
  • Topic Name and Query Description- both are mandatory fields, so Submit button should not get enabled without filling them
4.Under Topics tab: Verify that user is able to view the Topic details like state, ID, Date created/updated etc. and also edit the topic(only possible in Pending state) by clicking the 'View' button available next to status column

  • View button should be available for all the Topic states i.e. Pending, Approved and Rejected
  • User should only be able to Edit the Topic details for pending state topics
5.Verify that User is able to log out successfully by clicking the Logout button available under User information dropdown appearing at the top right corner

  • Logout functionality should work properly and take user back to Login page

Application - Steward

#Test caseExpected ResultNotes
1.Verify that user is able to log in the DSA-Steward application after entering valid credentials

    • URL should launch properly
    • Error is not expected after entering valid credentials
2.Verify that Topic, History and Statistics sections are available on the left side of the page

  • Topics page should also be the landing page after logging in. User can switch to 'History' and 'Statistics' tab by clicking it
  • Topics created by all the researchers should appear on this page
3.Under Topics tab: Verify that all 3 types of topics are available under their specific tab

  • Pending, Approved and Rejected topics should appear under their specific state tab only
4.

Under Topics tab: Verify that Steward is able to view the Topic details like state, ID, Date created/updated etc. by clicking the View button.

Also, Steward can Edit the current state of the Topic after clicking the 'Edit' button and selecting the desired state from the dropdown(Pending, Approved, Rejected)

 

  • Steward should have the rights to change the Topic state to Approved, Pending or Rejected
5.Under Statistic tab: Verify that Steward can check out the Query count by User and Query Topics by Status data available for last 7 days by default

  • Query count by user and query count by status should always show correct data
  • By default, End and Start Date should display 1-week old data starting from the present Date
6.Under Statistic tabVerify that Steward can also filter the Query count by User and Query Topics by Status data after applying the Start and End Date Range

  • Steward should be able to filter the results by applying the different Date range through calendar widget
7.Under Statistic tab: Verify that Steward can also visualize any researcher's ontology usage by checking out the Query digest window and further filter it by topic

  • Correct query count should appear on the user's query count by user bar
  • Filter by topic dropdown should only display topics created by the specific user
8.Verify that User is able to log out successfully by clicking the Logout button available under User information dropdown appearing at the top right

  • Logout functionality should work properly and take user back to the Login page


 

Application - Webclient

#Test caseExpected ResultNotes
1.Verify that user is able to log in the Web client application after entering valid credentials

  • URL should launch properly
  • Error should not appear after entering valid credentials
2.

Verify that below mentioned 4 major sections are appearing on webclient landing page
1. Navigate/Find Terms
2. Query Tools
3. Previous Queries
4. Query Status

  • All the sections should appear in minimized view by default
3.

Under Query tool section: Verify that user can request a new topic by clicking the 'Request New Topic' button available under Query tool section

DSA Application should open up and user should be able to create a topic successfully

 

  • Request New topic should be enabled always and should take the user to DSA login page
4.

Under Query tool section: Verify that a drop down consisting all Approved topics are appearing


  • Only Approved topics from the Steward for that particular Researcher should appear in this dropdown
5.

Under Navigate/Find terms: Verify that user is able to run following set of queries successfully

  • Query in each data element (demographics, dx, etc)
  • Query terms that are folders, leaf nodes, modifiers
  • Run date limited query for dx term
  • Run multipanel query
  • Run multipanel query with excluded term
  • Multiple terms in 1 panel
  • Multi-event query

  • User should be able to drag all the fields available in the Ontology section
  • New groups can be created
6.Under Quey status: Verify that User is able to see the running query status under Query Status tab

  • Compute time and status should be visible on this page for all the sites
  • A site retrieving error should also be available under this tab
7.

Under Quey status: Verify that User can also visualize/download the query status in different formats by clicking the following tabs

  • Graph Results
  • Query Report
  • Download Results

  • User can also zoom the graph by clicking the zoom graph link
  • Each site should be represented with unique color
  • User can also print the report by clicking the 'Prine Report' link
  • An option to download results in CSV format is also available
8.Verify that User is able to log out successfully by clicking the Logout button available on the top right corner of the application

  • Logout functionality should work properly and take user back to Login page

 

Application - Admin Dashboard

#Test caseExpected ResultNotes
1.Verify that user is able to log in the Web client application after entering valid credentials

  • URL should launch properly
  • Error is not expected after entering valid credentials
2.

Verify that following tabs are available in the left section of the page

  1. Summary
  2. i2b2 Connections
  3. Keystore
  4. Hub
  5. Adapter
  6. QEP
  7. Config
  8. Remote Dashboard
  9. Problem Log

  • Al these 9 tabs should be available on Hub node
3.Under Summary tab: Verify that current SHRINE version along with the built-in Time/Date is available under Version info section

  • Correct version info should be available under Summary
4.Under Summary tab: Verify that system health for all the component looks good

  • Errors are not expected
5.

Under i2b2 Connections: Verify that correct i2b2 End-point URL'S and Hive credentials are appearing

  • Incorrect information is not expected here
6.Under Keystore tab: Verify that Keystore page is showing all information correctly and errors are not appearing

  • Correct information is expected on Keystore page
7.Under Hub Node: Verify that correct downstream node information is available on Hub page

  • Correct downstream node information is expected here
8.Under Adapter Node: Verify that correct adapter configuration, Query test, and mapping files are available on this page

  • Correct adapter information is expected here
9.Under QEP tab: Verify that SHRINE data steward is in enabled state and its correct information is available on this page

  • Correct QEP information is expected here
10.Under config tab: Verify that correct config file information in the form of tree structure is available on this page

  • Correct config file information is expected here
11.Under Remote Dashboard: Verify that an admin is able to navigate to hub and other downstream nodes through this available Remote Dashboard functionality

  • Going back and forth to hub and other downstream nodes should be smooth
12.Under Problem log: Verify that admin can check all the problem logs plus its summary on this Problem log page

  • All the problem logs and its detail are expected to appear on this page
  • Verify that a wiki page opens up corresponding to the error on clicking the codec link
13.Verify that User is able to log out successfully by clicking the Logout button available on the top right corner of the application

  • Logout functionality should work properly and take user back to Login page



  • No labels