0.9 RC3 Testing [Firefox] #131

ThomasThelen · 2020-03-23T21:45:20Z

Test Plan

https://github.com/whole-tale/wt-design-docs/issues/new?template=test_plan.md

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

Preconditions:

Clear browsing history or open incognito/private session
Disconnect all third party integrations

Authentication

Basic login flow

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

Basic logout flow

Select the "User" menu
Select the "Log out" menu item. You should be taken to the login page.
Select "Access Whole Tale" button.
Note that you are not prompted to login.
1. Note issue #384 for logout for Globus
Restart your incognito session
Select "Access Whole Tale" button. You should be prompted to login via Globus Auth.

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

Logout from Whole Tale
Attempt to access https://dashboard.stage.wholetale.org/manage
You should be redirected to https://dashboard.stage.wholetale.org/login?rd=%252Fmanage
Select "Access Whole Tale".
You should be redirected to the Manage page.

Navigation

General navigation

Select "Browse" button. Browse page should display
Click "Create New..." and choose "Create new Tale". Create Tale modal should display, then close the modal.
Select "Manage" button. Manage page should display
Select "i" button should open User Guide in new tab
Select "Notification" button should display the notification panel
Select "Report a problem" button should open https://github.com/whole-tale/whole-tale/issues in new tab
Select "View" on a Tale. The Run page should display
Click the "user" icon

You should see a dropdown expand
The dropdown should contain the user's first/last name and gravatar image
The dropdown should provide a link to the Settings page
The dropdown should provide an option to Logout
Select the "Settings" option should bring you to the Settings page

Browse

Preconditions:

Assumes production Tales present (e.g., LIGO, materials, etc).
No running instances
General

Select "Browse" button. Confirm browse page displays
Confirm that no Tales are running

Search

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

Filter

Navigate to the Browse page
Confirm that you can switch between "All Tales" and "My Tales"
Confirm that all public Tales are shown on "All Tales"
Confirm that your Tales are shown under "My Tales"
Select "My Tales"
View a Tale and then navigate back to Browse
Confirm the filter is reset

View tale

Select "View" button on LIGO Tale
Confirm that Run > Metadata page displays
Confirm that you cannot delete or edit Tale properties
Select Back button. Confirm that you are taken back to Browse page
Select "View" button on Tale you own
1. Confirm that the Run and Close buttons are present
2. Confirm that you can edit Tale properties
3. Select "Close"
4. Confirm that you are taken back to Browse

Launch instance

Select "Run Tale" button on "Ligo" tale
1. Confirm you are prompted to Copy and Run
2. Select Copy and Run
3. Confirm that you are redirected to the Tale's Run page
4. Confirm that the notification dialog appears
5. Confirm that the step progression is correct
6. Confirm that the "View Logs" button shows the build logs in a modal
7. Navigate to the Browse page
8. Confirm that the Tale is shown under "Currently Running"
9. Select "View" on the Tale card
Select "Stop" to end the Tale instance
1. Confirm that the Tale has stopped
2. Confirm that the button has changed to Run
Navigate to Browse
1. Confirm that there are no Tales under "Currently Running"
2. Select the "Run Tale" button on a Tale you own
3. After the instance is launched, navigate back to the Browse page
4. Try to delete the Tale (not instance)
5. Confirm you cannot select the delete button on the browse page
6. Confirm that the "Run Tale" button has been replaced with "Stop Tale"
7. Confirm that the Tale is shown at the top of the page under "Currently running"

Manage

Preconditions

Empty home directory
No registered data
Register General

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

Register DataONE data

Select Manage > Data tab
Select "+". Confirm "Search for Data Sources" modal displays
Search for DOI 10.5065/D6862DM8
Confirm "Humans and Hydrology" dataset is found on DataONE.
Select Register
Confirm dataset appears in Manage Data list
Confirm additional URL formats:

Dataverse

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

Globus/MDF

Confirm DOI resolution for http://dx.doi.org/doi:10.18126/M2301J results in https://petreldata.net/mdf/detail/pub_30_shahani_twinmediated_v1.2
Register dataset https://petreldata.net/mdf/detail/pub_30_shahani_twinmediated_v1.2

Run

Preconditions:

No running Tale instances
General

Launch (Copy and Run) the Ligo Tale and wait for instance to start
Confirm you are on the Run page
1. Confirm Run panel displays Tale icon, title, and author
2. Confirm Run page displays Interact, Files, Metadata tabs
Select "..." menu.
1. "Learn more" displays https://wholetale.readthedocs.io/en/stable/users_guide/run.html
2. Confirm fullscreen displays Run panel in full screen
3. Confirm that the option for exporting the Tale is present

Interact tab

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

Files tab

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

Metadata tab - Owned Tale

Launch a Tale that you own
Add multiple datasets that have DOIs to the Tale
Navigate to Run > metadata
Valid environments should be listed in the Environment dropdown menu
Valid licenses should be listed in the License dropdown
Confirm that you see Created by <your_name> under Authors
Confirm that your Tale has the CC4 license assigned to it
Confirm that the Tale's Published Location reads This Tale has not been published
Confirm that there are citations for the external datasets
Change the name of the Tale, Category, Description, Illustration, Public, License, and add multiple authors
Select Save. Confirm that you see a notification telling you that the Tale was saved.
Refresh the page. Your changes should be preserved between page refreshes, confirming that they are being properly persisted.
Confirm that the new Tale authors are displayed on the Tale card

Home

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

External data

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
Confirm "External Data" list is initially empty
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. "Select" saves your changes back to the server
6. "Cancel" aborts the operation without saving and reverts your changes
Confirm "External Data" list matches what was saved

Workspaces

Confirm create folder
Confirm upload file
Select "+" button has options "New folder", "Upload file", Import Tale Data..."
Folder operations
1. Confirm context menu Copy, Rename, Download, Remove
2. Confirm rename folder
3. Confirm download folder (this should result in a zip file)
4. Confirm remove folder
File operations
1. Upload a file
2. Confirm context menu Copy, Rename, Download, Remove
3. Confirm rename folder
4. Confirm download file
5. Confirm remove file
Select "Import Tale Data..."
1. Note vertical navigation with Tale Workspaces
2. Copy to Workspace from another workspace
3. Move to workspace from another workspace

Exporting - BagIt

View a Tale that you own
Navigate to Run
Click the three-dot-dropdown
Select 'Export as BagIt'
Confirm that a download starts for the ZIP archive
Open the archive
Confirm that the top level has
1. run-local.sh
2. tagmanifest-sha256.txt
3. tagmanifest-md5.txt
4. manifest-sha256.txt
5. manifest-md5.txt
6. bag-info.txt
7. README.md
8. bagit.txt
9. fetch.txt
10. data/
11. metadata/
Navigate into the metadata folder
Confirm that there is a manifest.json and environment.json file
Navigate to /data
Confirm that there is a LICENSE file

Settings

Default State

Navigate to the Settings page
Confirm there are empty settings for DataONE, Dataverse, and Zenodo

Connect to DataONE

Click "Connect Account" under the DataONE repository
Confirm that you're redirected to the DataONE login
Log in with ORCID
Confirm that you're redirected back to Whole Tale
Confirm that you see "Authorized" under the DataONE server
Confirm that the "Connect Account" Button is disabled
Disconnect your account
Confirm that you can re-connect it

Connect to Dataverse

Click "Connect Account" in the Dataverse section
Confirm that the connection modal opens
Enter your API key for one of the repositories
Click "Connect"
Confirm that you see "Authorized on "
Repeat for each Dataverse server

Connect to Zenodo

Click "Connect Account" in the Zenodo section
Confirm that the connection modal opens
Enter your API key for one of the repositories
Click "Connect"
Confirm that you see "Authorized on "
Repeat for each Zenodo server

Confirm tokens retained across logins
#370

Connect one or more accounts as outlined above
Logout and login again
Using Swagger UI, hit the /user/me endpoint to confirm tokens are still present

Tale Creation

Create RStudio Tale

Select the Create New... button on the Browse Page
Select the Create New Tale dropdown item
Enter title "Test Tale"
Select compute environment RStudio
Select "Create New Tale and Launch"
Confirm notification dialog opens
Confirm that the build/launch steps are correct
Confirm that you are redirected to the Run page
Navigate to the Browse page
Confirm the Tale is shown under "Currently running"

Compose Jupyter Tale
Compose OpenRefine Tale
Too many instances

Make sure you have two launched Tales
Attempt to create a Tale
Confirm that you receive an error that you have the max limit
Confirm that the Tale is created, but not the instance

Analyze in Whole Tale

Task 1: Importing a Dataset from Dataverse

These test cases cover potential situations that can occur when importing datasets from Dataverse.

Case 1: Ideal Scenario:

Testing Steps:

Remove all running Tale instances
Navigate to https://girder.stage.wholetale.org/api/v1/integration/dataverse?datasetPid=doi%3A10.7910%2FDVN%2F3MJ7IR&siteUrl=https%3A%2F%2Fdataverse.harvard.edu
Confirm that the Tale title reads as Replication Data for: "Agricultural Fires and Health at Birth"
Confirm that the only item in the Input data section matches the uri with Data Source appended
Confirm that no environment is selected
Confirm that the Create New Tale and Launch button is disabled
Select an environment
Confirm that READ/WRITE is selected
Click Create New Tale and Launch
Confirm that you are redirected to the run page
Confirm that the Tale name matches the Tale Name in the Create Tale Modal
Confirm that the data exists under Tale Workspace
Confirm that the Tale's category is science

Task 2: Importing a Dataset from DataONE

These test cases cover different scenarios that may happen when importing datasets from DataONE.

Case 1: Ideal Scenario:

This test covers the ideal case where dataset importing has all of the needed information
to properly run. This includes the dataset location, title, and selected environment.

Testing Steps:

Remove all running Tale instances
Navigate to https://girder.stage.wholetale.org/api/v1/integration/dataone?uri=https%3A%2F%2Fsearch.dataone.org%2Fview%2Fdoi%3A10.18739%2FA2VQ2S94D&title=Fire%20influences%20on%20forest%20recovery%20and%20associated%20climate%20feedbacks%20in%20Siberian%20Larch%20Forests%2C%20Russia&environment=RStudio
Confirm that the Tale title reads as Fire influences on forest recovery and associated climate feedbacks in Siberian Larch Forests, Russia
Confirm that the only item in the Selected data section matches the uri with Data Source appended
Confirm that Rstudio is selected in the Environments widget
Confirm that the Create New Tale and Launch button is enabled
Confirm READ ONLY is selected
Click Create New Tale and Launch
Confirm that you are redirected to the run page
Confirm that the Tale name matches the Tale Name in the Create Tale Modal
Confirm that the data exists in the Tale under External Data
Confirm that the Tale's category is science

Case 2: Testing Different DataONE Deployments
The Analyze in Whole Tale feature is deployed across a few DataONE test sites. This test ensures Whole Tale has the ability to import
data from each of them.

Links:

Testing Steps:

Remove all running Tale instances
Navigate to each of the two links above
Select an environment
Click Create New Tale and Launch
Confirm that the correct data exists in the Tale under External Data

Task 3: Shared Behavior

These cases show errors that are common between Dataverse and DataONE. Although they are tested using DataONE URIs, the errors should be the same when replacing it with a Dataverse URI.

Case 1: Missing Dataset Title Query Param:

This test covers the case where the name query parameter is missing. The expected behavior is
that the uri query parameter is used instead.

Testing Steps:

Remove all running Tale instances
Navigate to https://dashboard.stage.wholetale.org/browse?uri=https%3A%2F%2Fdataverse.harvard.edu%2Fapi%2Faccess%2Fdatafile%2F3323458
Confirm that the Tale title reads as https://dataverse.harvard.edu/api/access/datafile/3323458
Confirm that the only item in the Selected data section matches the uri with Data Source appended
Confirm that no Environment is selected
Confirm that the Create New Tale and Launch button is disabled
Select an environment
Click Create New Tale and Launch
Confirm that the notification bar appears & properly updates
Confirm that you are redirected to the run page
Confirm that the Tale name matches the Tale Name in the Create Tale Modal
Confirm that the data exists in the Tale under External Data

Case 2: Importing Data with Read/Write:

This test covers the case where a user imports data from an external source and selects READ/WRITE in the Create Tale Modal.

Testing Steps (Variant 1):

Remove all running Tale instances
Navigate to https://dashboard.stage.wholetale.org/browse?uri=https%3A%2F%2Fdataverse.harvard.edu%2Fapi%2Faccess%2Fdatafile%2F3323458
Confirm that the Tale title matches the URI above
Confirm that the only item in the Selected data section matches the uri with Data Source appended
Confirm that the Create New Tale and Launch button is disabled
Select an environment
Select READ/WRITE
Click Create New Tale and Launch
Confirm that the notification bar appears & properly updates
Confirm that you are redirected to the run page
Confirm that the Tale name matches the Tale Name in the Create Tale Modal
Confirm that the data exists in the Tale Workspace

Testing Steps (Variant 2):

Remove all running Tale instances
Navigate to https://dashboard.stage.wholetale.org/browse?api=https%3A%2F%2Fdev.nceas.ucsb.edu%2Fknb%2Fd1%2Fmn%2Fv2&environment=JupyterLab&name=proveit&uri=doi%3A10.5072%2FFK27P92Z55
Confirm that the Tale title matches the dataset
Confirm that the only item in the Selected data section matches the uri with Data Source appended
Confirm that the Create New Tale and Launch button is disabled
Select READ/WRITE
Click Create New Tale and Launch
Confirm that the notification bar appears & properly updates
Confirm that you are redirected to the run page
Confirm that the Tale name matches the Tale Name in the Create Tale Modal
Confirm that the data exists in the Tale Workspace

Tale metadata tests

The purpose of these tests are to confirm that the metadata files (manifest.json, environment.json, LICENSE) we generate are correct.

manifest.json

Launch a Tale that you own
Add a dataset to the Tale
Add at least one author
Add at least one file to the workspace
Export the Tale (as BagIt)
Open the manifest.json file under metadata/
Confirm that the author is listed under schema:author
Confirm that you are listed under createdBy
Confirm that the file(s) in the workspace are properly listed in aggregates
Confirm that the external dataset is referenced in aggregates
Confirm that the dataset is also listed under Datasets

environment.json

Open the archive from the manifest.json test
Navigate to metadata/environment.json
Open the girder web API
Locate and GET the Image that the Tale used
Confirm that the config section from girder matches the config section in environment.json

LICENSE

Open the archive from the manifest.json test
Open the LICENSE file
Navigate to Run > metadata
Confirm that the opened LICENSE file matches the selected license on the metadata page
Change the Tale's license
Export the Tale
Confirm that the LICENSE changed appropriately

Publishing tests

Case 1: No Accounts Configured
1. Disconnect all of your external accounts
2. Launch a Tale that you own
3. Click the ellipsis dropdown on the Run page
4. Click Publish tale...
5. Confirm that your are notified to link accounts on the settings page
6. Click Go to Settings
7. Confirm you are re-directed to settings
Case 2: Publishing to a Third Party
1. Connect to a third party provider (make sure it's a dev server)
2. Launch a Tale that you own
3. Add some data to it
4. Click Publish tale...
5. Confirm that the publishing modal opens
6. Confirm that the third party that you are connected to appears in the dropdown
7. Select the third party
8. Click Publish
9. Once complete, navigate to the metadata page
10. Confirm that the published location is present
11. Visit the published location
12. Confirm that you see the following files plus yours
  1. metadata.xml
  2. LICENSE
  3. README.md
  4. manifest.json
  5. environment.json
13. Repeat for each third party provider
  
  a. After publishing to DataONE, use girder to query the Tale
  
  b. Ensure that the 'pid' field in the 'publishInfo' object has an identifier in a doi format
Case 3: Re-published Tale

Launch a Tale that has been published before
Take note of the Published Location in Run > metadata
Re-publish the Tale to the third party
Confirm that the Published Location has changed to the correct package landing page

Zenodo integration tests

Register Zenodo data

Select Manage > Data tab
Select "+". Confirm "Search for Data Sources" modal displays
Search for Concept DOI doi:10.5281/zenodo.16384
Confirm "Belmont Forum..." dataset is found on Zenodo with suffix ver_1
Search for URL https://zenodo.org/record/1172960#.XidIvlNKh24
Confirm "Belmont Forum..." dataset is found on Zenodo with suffix ver_2
Search for DOI doi:10.5281/zenodo.1172960
Confirm "Belmont Forum..." dataset is found on Zenodo with suffix ver_2
Search for Concept DOI doi:10.5281/zenodo.608984
Confirm "Belmont Forum..." dataset is found on Zenodo with suffix ver_2
Select Register
Confirm dataset appears in Manage Data list
Add to tale and confirm contents match

The register tests the following cases.

Datasets with multiple files
Datasets with multiple versions
Concept DOI
Zenodo dataset via AiWT

Open https://dashboard.stage.wholetale.org/browse?uri=https%3A%2F%2Fdoi.org%2F10.5281%2Fzenodo.820575&name=Automotive%20Sensor%20Data
Confirm Source Data URL and Title match above URL and "READ ONLY" is selected
Select environment
Select 'Create and Launch Tale'
Confirm dataset is mounted read-only, citation is as expected, zipfile is not extracted

The register tests the following cases.

Dataset with single file (zipfile)
Zenodo Binder via AiWT

Open https://dashboard.stage.wholetale.org/browse?uri=https%3A%2F%2Fdoi.org%2F10.5281%2Fzenodo.3242073&environment=JupyterLab&name=Simple%20requirements.txt%20based%20example%20for%20repo2docker&asTale=true
COnfirm Source Data and Title match URL and "READ WRITE" is selected
Select 'Create and Launch Tale'
Confirm image builds and notebook can run

Zenodo Tale via AiWT

Open https://girder.stage.wholetale.org/api/v1/integration/zenodo?doi=10.5072%2Fzenodo.490450&resource_server=sandbox.zenodo.org
Confirm Water Tale is created.
Confirm citation on Metadata view
Confirm DOI matches above
Use the Swagger UI to confirm the publishInfo field on the tale object contains pid, repository, repository_id, uri
Run the tale and and notebook, confirm it works as expected (produces glorious map of Texas)

Publish/import to/from Zenodo Sandbox

Follow instructions above to configure your API key for Zenodo sandbox
Create your own Tale and publish to sandbox.zenodo.org
Confirm publishInfo contains Sandbox entry
Delete tale
Import tale from Zenodo
Confirm publishInfo
Modify the tale
Re-publish to sandbox.zenodo.org
Delete tale
Import tale from Zenodo
Confirm publishInfo
Download and extract the exported Tale
Execute the run-local.sh command to run the Tale locally

Regression tests

Internal-state problems (#326)

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

Invalid instance ID (#333)

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

Files don't overflow Manage page (#410)

Navigate to the manage page
Register enough/upload enough data to the point where you need to scroll through files on the right hand side
Make sure that the files don't overflow the container, also check in Firefox

Handle read only Tales (#406)

Login to the WholeTale Dashboard
View a Tale that allows you to read, but not write
Navigate to Run > Files > Tale Workspaces
- You should see the Tale's Workspace folders/files are listed here
- You should see that (+) has been greyed out, disallowing writes
Navigate to Run > Files > External Data
- You should see the Tale's External Datasets are listed here
- You should see that (+) has been greyed out, disallowing writes

The text was updated successfully, but these errors were encountered:

ThomasThelen · 2020-03-26T17:10:31Z

Authentication: Passed
Navigation: Passed
Browse: Passed
Tale Creation: Failed
Settings: Passed
Publishing tests: Passed
Regression tests: Passed
Run: Passed

ThomasThelen · 2020-03-26T19:27:12Z

Tale Creation

When creating a Jupyter with Spark! Tale I recieved the following trace. I created two new Tales with Jupyter Spark! they worked fine.

APIError: 500 Server Error: Internal Server Error ("mkdir /var/lib/docker/overlay2/6d9546c33aea02ae5321c0c1cb5a2af57400973dd02608b67f9afabd5499db12-init: no space left on device")
  File "/usr/local/lib/python3.5/dist-packages/celery/app/trace.py", line 382, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/girder_worker/task.py", line 148, in __call__
    results = super(Task, self).__call__(*_t_args, **_t_kwargs)
  File "/usr/local/lib/python3.5/dist-packages/celery/app/trace.py", line 641, in __protected_call__
    return self.run(*args, **kwargs)
  File "/gwvolman/gwvolman/tasks.py", line 437, in build_tale_image
    ret = _build_image(cli, tale_id, image, tag, temp_dir, REPO2DOCKER_VERSION)
  File "/gwvolman/gwvolman/utils.py", line 317, in _build_image
    'bind': '/host/tmp', 'mode': 'ro'
  File "/usr/local/lib/python3.5/dist-packages/docker/models/containers.py", line 803, in run
    detach=detach, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/docker/models/containers.py", line 861, in create
    resp = self.client.api.create_container(**create_kwargs)
  File "/usr/local/lib/python3.5/dist-packages/docker/api/container.py", line 430, in create_container
    return self.create_container_from_config(config, name)
  File "/usr/local/lib/python3.5/dist-packages/docker/api/container.py", line 441, in create_container_from_config
    return self._result(res, True)
  File "/usr/local/lib/python3.5/dist-packages/docker/api/client.py", line 267, in _result
    self._raise_for_status(response)
  File "/usr/local/lib/python3.5/dist-packages/docker/api/client.py", line 263, in _raise_for_status
    raise create_api_error_from_http_exception(e)
  File "/usr/local/lib/python3.5/dist-packages/docker/errors.py", line 31, in create_api_error_from_http_exception
    raise cls(e, response=response, explanation=explanation)

Xarthisius · 2020-03-26T20:36:28Z

APIError: 500 Server Error: Internal Server Error ("mkdir /var/lib/docker/overlay2/6d9546c33aea02ae5321c0c1cb5a2af57400973dd02608b67f9afabd5499db12-init: no space left on device")

Cleaned the node up. Should be good to go.

ThomasThelen · 2020-04-01T23:50:30Z

Aside from the noted regressions in the other issues, I don't see any newly injected bugs. Closing.

ThomasThelen self-assigned this Mar 23, 2020

ThomasThelen closed this as completed Apr 1, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

0.9 RC3 Testing [Firefox] #131

0.9 RC3 Testing [Firefox] #131

ThomasThelen commented Mar 23, 2020 •

edited

Loading

ThomasThelen commented Mar 26, 2020 •

edited

Loading

ThomasThelen commented Mar 26, 2020 •

edited

Loading

Xarthisius commented Mar 26, 2020

ThomasThelen commented Apr 1, 2020

0.9 RC3 Testing [Firefox] #131

0.9 RC3 Testing [Firefox] #131

Comments

ThomasThelen commented Mar 23, 2020 • edited Loading

Test Plan

Authentication

Navigation

Browse

Manage

Run

Settings

Tale Creation

Analyze in Whole Tale

Task 1: Importing a Dataset from Dataverse

Task 2: Importing a Dataset from DataONE

Task 3: Shared Behavior

Tale metadata tests

Publishing tests

Zenodo integration tests

Regression tests

ThomasThelen commented Mar 26, 2020 • edited Loading

ThomasThelen commented Mar 26, 2020 • edited Loading

Tale Creation

Xarthisius commented Mar 26, 2020

ThomasThelen commented Apr 1, 2020

ThomasThelen commented Mar 23, 2020 •

edited

Loading

ThomasThelen commented Mar 26, 2020 •

edited

Loading

ThomasThelen commented Mar 26, 2020 •

edited

Loading