Versions Compared

Old Version 5

changes.mady.by.user Sam Tsoi

Saved on

compared with

New Version Current

changes.mady.by.user Sam Tsoi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Application - Admin Dashboard

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

Image Modified

  • 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

Image Modified

  • 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

Image Modified

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

Image Modified

  • Errors are not expected
5.

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

Image Modified

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

Image Modified

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

Image Modified

  • 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

Image Modified

  • 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

Image Modified

  • 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

Image Modified

  • 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

Image Modified

  • 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

Image Modified

  • 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

Image Modified

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