Test results for WholeTale v0.6.0rc1

[bodom0015]

Test Plan

Note: For all tests, repeat for supported browser/OS combinations.

Preconditions:

• Clear browsing history or open incognito/private session

Authentication

• Basic login flow

1. Goto https://dashboard.wholetale.org
2. Select "Access Whole Tale" button. You should be prompted to login via Globus Auth.
3. Select your organization and login
4. You should be taken to the Browse page
5. Your Gravatar and user name should display

• Basic logout flow

1. Select the "Logout" button. You should be taken to the login page.
2. Select "Access Whole Tale" button.
3. Note that you are not prompted to login.
   1. Note PR #331 for issues with logout
   2. Note issue #384 for logout for Globus
4. Restart your incognito session
5. Select "Access Whole Tale" button. You should be prompted to login via Globus Auth.

• Return-route for non-logged in users (#300)

1. Logout from Whole Tale
2. Attempt to access https://dashboard.dev.wholetale.org/run
3. You should be redirected to https://dashboard.dev.wholetale.org/login?rd=%252Frun
4. Select "Access Whole Tale".
5. You should be redirected to the Run page.

Navigation

• General navigation

1. Select "Browse" button. Browse page should display
2. Select "Run" button. Run page should display
3. Select "Manage" button. Manage page should display
4. Select "Compose" button. Compose page should display
5. Select "i" button should open User Guide in new tab
6. Select "Logout" button should logout from WT
7. Select "Report a problem" button should open https://github.com/whole-tale/whole-tale/issues in new tab

Browse

Preconditions:

• Assumes production Tales present (e.g., LIGO, materials, etc).

• No running instances

• General

1. Select "Browse" button. Confirm browse page displays
2. Confirm "i" button opens https://wholetale.readthedocs.io/en/stable/users_guide/browse.html
3. Confirm "fullscreen" button opens Browse panel in fullscreen
4. Confirm no tales in "Launched Tales" panel

• Search

1. Enter "Ligo" as search term. Confirm only LIGO tale displays
2. Clear search term. Confirm all tales display

• Filter

1. Confirm filter dropdown is disabled
2. Select "Filter" icon. Confirm that filter dropdown is enabled
3. Select "All". Confirm that all tales are displayed
4. Select "Mine". Confirm that only your tales are displayed
5. Select "Published". Confirm that only published tales are displayed (no tales)
6. Select "Recent". (What is supposed to happen here?)
7. Select Run then Browse. Note that selection is not retained.

• List and card views

1. Select "Switch to list view". Confirm list view displays
2. Select "Switch to card view". Confirm card view displays
3. Select Run then Browse. Note that selection is not retained.

• View tale

1. Select "View" button on LIGO Tale
2. Confirm View page displays
3. Confirm that you cannot delete or edit Tale properties
4. Select Back button. Confirm that you are taken back to Browse page
5. Select "View" button on Tale you own
   1. Confirm Delete button is present
   2. Confirm that you can edit Tale properties
   3. Select "Delete". Confirm that you are prompted to delete.
   4. Select "No" -- tale is not deleted
   5. Select "Yes" -- tale is deleted and you are retured to Browse view

• Launch instance

1. Select "Launch" button on "Ligo" tale
   1. Confirm that tale appears in "Launched Tales" panel
   2. Confirm spinner displays until Tale is ready
   3. Confirm "Tale Launched" notification displays on Tale card
   4. Confirm that then the instance is started and can be selected in the Launched Tales panel
2. Select "X" to delete the instance
   1. Confirmation dialog displays.
   2. Select "No" -- instance is not deleted
   3. Select "Yes" -- instance is deleted
3. Select "Launch" button on Tale you own
   1. After the instance is launched, try to delete the Tale (not instance)
   2. Confirm cannot Delete Tale message displays
   3. After instance has started, select the instance in the Launched Tales panel
   4. Confirm that you are taken to the Run > Interact page for the instance
4. Select "Launch" on the already-launched instance
   1. Confirm "The Tale...has been Launched!" message displays"
   2. Select "Go to Tale". Confirm that you are taken to the Run > Interact page.

Manage

Preconditions

• Empty home directory

• No registered data

• Register General

1. Select Manage > Data > "+" to open register panel
2. Confirm list of providers matches list of supported providers (Globus, DataONE, Dataverse)

• Register DataONE data

1. Select Manage > Data tab
2. Select "+". Confirm "Search for Data Sources" modal displays
3. Search for DOI 10.5065/D6862DM8
4. Confirm "Humans and Hydrology" dataset is found on DataONE.
5. Select Register
6. Confirm dataset appears in Manage Data list
7. Confirm additional URL formats:
   1. https://search.dataone.org/view/doi:10.5063/F1Z60M87
   2. https://search.dataone.org/view/https://pasta.lternet.edu/package/metadata/eml/knb-lter-nwt/115/1
   3. https://search.dataone.org/view/doi:10.18739/A2CN6XZ7H
   4. https://raw.githubusercontent.com/whole-tale/dashboard/master/.travis.yml

• Dataverse

1. Register dataset doi:10.7910/DVN/SZ9YXZ
2. Confirm "Replication Data for: Direct Democracy and Women's Political Engagement" from Dataverse

• Globus/MDF

1. Confirm DOI resolution for http://dx.doi.org/doi:10.5072/FK2KW5FG4W results in https://publish.globus.org/jspui/handle/ITEM/607
2. Register dataset https://publish.globus.org/jspui/handle/ITEM/607

Compose

• Compose RStudio Tale

1. Select Compose. Confirm Compose page displayed with Launch New Tale button disabled.
2. Enter title "Test Tale"
3. Select compute environment RStudio
4. Select "Launch New Tale"
5. Launching new Tale spinner displays
6. After instance is started, you are redirected to Run page for instance

• Compose Jupyter Tale

• Compose OpenRefine Tale

• Too many instances

Run

Preconditions:

• No running Tale instances

• General

1. Go to the Run page
2. Confirm "Choose from Launched Tales panel" displays
3. Confirm no Tales in Launched Tales panel
4. Launch the Ligo Tale and wait for instance to start
5. Select the "Run" Menu.
   1. Confirm LIGO Tale instance is displayed in Run and Launched Tale panels
   2. Confirm Run panel displays Tale icon, title, and author
6. Confirm Run page displays Interact, Files, Metadata tabs
7. Select "..." menu.
   1. Read the docs displays https://wholetale.readthedocs.io/en/stable/users_guide/run.html
   2. Confirm fullscreen displays Run panel in full screen

• Interact tab

1. Select the "Interact" tab
2. Confirm Jupyter environment is displayed in iframe
3. Select "popout" icon. Confirm Jupyter is opened in new Tab

• Files tab

1. Select "Files" tab
2. You should see a vertical navigation menu with three tabs: "Home", "External Data", and "Tale Workspace".

• Metadata tab

1. Select "Metadata" tab
2. Confirm that metadata displays for current tale
3. If you do not own or cannot edit the Tale, the form should be read-only
4. If you own the Tale Date Created, Last Updated, and Authors should be read-only
5. Valid environments should be listed in the form dropdown for Environment
6. Change the name of the Tale, Category, Description, Illustration and Public
7. Refresh the page. Your changes should be preserved between page refreshes, confirming that they are being properly persisted.
8. Select Save. Confirm changes are saved.

• Home

1. Select Files > Home. Confirm that your home directory displays
2. Create a folder and upload a file to the folder
3. Confirm file operations:
   1. Copy, rename, remove, download

• External data

1. Precondition: Register one or more Datasets (e.g. doi:10.18739/A29G5GD0V) on Manage > Data (see Manage > Register test cases above)
   • NOTE: You may need to wait for registration to complete
2. Confirm "External Data" list is initially empty
3. Confirm (+) button ("Select Data modal") behavior
   1. Confirm that "WholeTale Catalog" shows all registered datasets
   2. Confirm that "My Data" filters to only show your registered datasets
   3. "Add" data to associate it with a Tale
   4. "Remove" data to dissociate it with a Tale
   5. "Submit" saves your changes back to the server
   6. "Cancel" aborts the operation without saving and reverts your changes
4. Confirm "External Data" list matches what was saved

• Workspaces

1. Confirm create folder
2. Confirm rename folder/file
3. Confirm upload file
4. Confirm copy file/folder from/to Home
5. Confirm move file/folder from/to Home
6. Confirm remove file/folder
7. Select "+" button has options "New folder", "Upload file", "Select Data"
8. Folder operations
   1. Confirm context menu Move To, Rename, Copy to Home, Download, Remove
   2. Move To...
      1. Issue -- should this be enabled
   3. Confirm rename folder
   4. Copy to Home confirm folder copied to home
   5. Confirm download -- zip file
   6. Confirm remove
9. File operations
   1. Upload a file
   2. Confirm context menu Move To, Rename, Copy to Home, Download, Remove
   3. Move To... Home?
      1. Issue -- doesn't work
   4. Confirm rename folder
   5. Copy to Home confirm folder copied to home
   6. Confirm download
   7. Confirm remove
10. Select "Select Data..."
    1. Note vertical navigation with Home and Tale Workspaces
    2. Copy to Workspace from Home
    3. Move to Workspace from Home
    4. Copy to Workspace from another workspace
    5. Move to workspace from another workspace

Analyze in Whole Tale

Regression tests

• Internal-state problems (#326)

1. Open a non-incognito browser tab, log into the UI and navigate to the /manage view
2. Create a folder (e.g. test123) and click down into it
3. Open an incognito browser tab, login to the UI again, and navigate to the /manage view
4. In the incognito tab, delete the test123 folder and close the incognito tab
5. Refresh your non-incognito browser tab
6. You should not be stuck on a blue screen
7. You should not need to manually refresh the page
8. You should be taken to the /manage view of your Home folder
9. NOTE: Your last refresh may take a couple of seconds longer than usual

• Invalid instance ID (#333)

1. Manually change the path suffix in the address bar to /run/ThisIsObviouslyNotARealID
2. You should be brought to /browse page instead

[bodom0015]

Software issues (Chrome/OSX):

• Run > Interact for OpenRefine only shows a 404 for me.. am I doing something wrong here?
  • @Xarthisius says see Openrefine start server take too much time on Openstack Instance OpenRefine/OpenRefine#1274
• UI should disable Tale Workspaces features for users with insufficient Tale access dashboard#391 / Workspaces that I can't access are returned from GET /workspace girder_wholetale#239
  • Run > Files > Tale Workspaces > New Folder / Upload File are somehow adding the new items to "Home" and not the Workspace (listed items become desynced from selection as well)
  • Run > Files > Tale Workspaces > Import Tale Data throws a 403 and fails when attempting to view the contents of a Tale Workspace which I don't own (and could also shown the "Back" button on such a failure)
  • ERROR: CANNOT FINISH WORKSPACES TESTS - since I cannot create workspace folders or read the Workspaces of others', I am unable to run many of the tests written above for Tale Workspaces
• Browse filter state mismatch when deleting a Tale dashboard#390
  • Browse: edge case found when deleting a Tale while filtered to "Mine"

Other issues:

• Metadata tab: Test case does not mention that I will need write access to the launched Tale, previous cases used LIGO which is read-only
• Home test case is missing file operation for "Move To..."
• Globus/MDF registration test case has an invalid fake DOI - use http://dx.doi.org/doi:10.18126/M2301J instead

[ThomasThelen]

For the second issue,

• Run > Files > Tale Workspaces > New Folder / Upload File are somehow adding the new items to "Home" and not the Workspace (listed items become desynced from selection as well)

If you go to girder can you look at your folders to make sure you have a workspace folder?

[bodom0015]

I did have a workspace folder (although mine was lower case.. is this expected?), but I see now that I was running the LIGO Tale as per the Test Plan.

Since I didn't have write access, I can't import to the Workspace of this Tale. Since I also don't have read access to these folders, my currentFolder in the UI is never updated, so the Files are actually being added to whatever my previous currentFolder was (in this case, "Home").

Running a "Test Tale" RStudio (per the Compose RStudio Instance test case), I am able to import to the Tale's workspace.

This is related to my note above:

• Metadata tab: Test case does not mention that I will need write access to the launched Tale, previous cases used LIGO which is read-only

The UI should probably disable the "Import Tale Data" button if you don't have write access to the Tale.

Filed these issues separately as whole-tale/girder_wholetale#239 and whole-tale/dashboard#391

[ThomasThelen]

Can confirm issues with registering MDF datasets.

[ThomasThelen]

Under Run > General, I noticed that if I launch the LIGO Tale and navigate to run once it's done spinning up, it isn't automatically selected (I think this test case implies that it is)

[ThomasThelen]

Under run > Files tab

The folder names are slightly different than the ones outlined in the test case.
External Data is shown as data
Tale Workspace is shown as workspace

[ThomasThelen]

I went through the workspace tests and all but the last of the test cases went well; I'm not sure where the Select Data... piece is.

I did note that the Import Tale Data modal failed to load any registered data (I got permission denied 403 from the item and folder endpoints). This can be related to whole-tale/dashboard#391

When I browsed Tales that I did own, the dialog functioned as expected.

[bodom0015]

Can confirm issues with registering MDF datasets.

@ThomasThelen apparently the link provided had a fake DOI.. can use http://dx.doi.org/doi:10.18126/M2301J instead

[bodom0015]

Under Run > General, I noticed that if I launch the LIGO Tale and navigate to run once it's done spinning up, it isn't automatically selected (I think this test case implies that it is)

You are right, there seems to be a step missing from the test case to select the LIGO Tale - we have the tester verify that it is in the Launched Tales, but never explicitly say to select it

[bodom0015]

Under run > Files tab

The folder names are slightly different than the ones outlined in the test case.
External Data is shown as data
Tale Workspace is shown as workspace

The test case here is poorly worded, and the reapeated "Files" tab in the UI does not do much to remedy the confusion. In the test case, we are referring to the upper "Files" tab that is rendered by Ember (e.g. directly between "Interact" and "Metadata"). The "data", "home", "workspace" folders appear in the Jupyter iframe's "Files" tab that is below the Ember one.

Although, it is confusing that these folders no longer match even though they are related 1-1

I went through the workspace tests and all but the last of the test cases went well; I'm not sure where the Select Data... piece is.

I did note that the Import Tale Data modal failed to load any registered data (I got permission denied 403 from the item and folder endpoints). This can be related to whole-tale/dashboard#391

When I browsed Tales that I did own, the dialog functioned as expected.

More test plan confusion, as the Run > Files > Tale Workspaces > Select Data option was renamed to "Import Tale Data..."

Regarding the permissions errors, you are correct that this is the same as whole-tale/dashboard#391. And you should still be able to browse down and view data for Tales that you own or have sufficient access to read