Open bodom0015 opened 4 years ago
After rerunning "Zenodo Tale via AiWT" with @craig-willis' new DOI (https://sandbox.zenodo.org/record/490450#.XjnHHRNKh25):
BUG - modal never shows, AiWT never happens, and I am just redirected to Craig's existing Tale: https://dashboard.stage.wholetale.org/run/5e39d26e8bec16c2663dda16?token=wZrmafFvLyvyeGyKeP8ymzAVcoquvOObLqwwMLjfC6A7SonsvfomfbOE44KqAk2Q
@bodom0015 it's not Craig's Tale, it's your copy. There's no modal, cause there's nothing for you to choose. You just described a feature not a bug :)
Ah... you are correct! Well, that is genuinely confusing. :D
Unfortunately, the test case still fails because there is no citation or external data attached to the resulting Water Tale.
Proposed improvements: https://github.com/whole-tale/wt-design-docs/pull/126
404.html
appeared under "External Data", and no data ever appeared in the Tale Workspace_ver_2
suffix, not _ver_1
(not sure if this counts as a failure)zenodo.org
?Publish
target... this was confusing even to me
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:
Authentication
NOTE: User's name/gravatar no longer displays in the navbar Filed https://github.com/whole-tale/dashboard/issues/590 since gravatar icon no longer displays in the navbar
[x] Basic logout flow
[x] Return-route for non-logged in users (#300)
Navigation
Browse
Preconditions:
Assumes production Tales present (e.g., LIGO, materials, etc).
No running instances
[x] General
[x] Search
[x] Filter
[x] View tale
[x] Launch instance
Manage
Preconditions
Empty home directory
No registered data
[x] Register General
NOTE: Zenodo missing from test confirmation
10.5065/D6862DM8
BUG: Registering "Humans and Hydrology" required a refresh afterward.. display was missing one or more datasets before refresh.
[x] Dataverse
[x] Globus/MDF
NOTE: Punctuation is stripped - could this potentially result in a collision?
Run
Preconditions:
No running Tale instances
[x] General
[x] Interact tab
[x] Files tab
[x] Metadata tab - Read Only Tale
NOTE: Duplicate test case (see "View Tale" above)
[x] Metadata tab - Owned Tale
Environment
dropdown menuLicense
dropdownCreated by <your_name>
underAuthors
Published Location
readsThis Tale has not been published
[x] Home
NOTE: "Move To..." is also here (and works), apparently
doi:10.18739/A29G5GD0V
) on Manage > Data (see Manage > Register test cases above)NOTE: "External Data" does not start empty for LIGO Tale
BUG: Copying a folder, then immediately removing it does not update the UI (hint: copy, navigate, navigate back, then remove does work properly)
bag-info.txt
bagit.txt
data/
fetch.txt
manifest-md5.txt
manifest-sha256.txt
metadata/
README.md
run-local.sh
tagmanifest-md5.txt
tagmanifest-sha256.txt
metadata
foldermanifest.json
andenvironment.json
fileLICENSE
fileSettings
[x] Default State
[ ] Connect to DataONE
BUG: Hard-coded
dashboard.local
(see https://github.com/whole-tale/dashboard/pull/589)BUG: "Connect Account" not disabled after all servers registered
BUG: "Connect Account" not disabled after all servers registered
girder-shell
, confirm tokens are still presentNOTE: I can't run this case, since I don't have SSH access to the staging VM, and therefore cannot use Docker exec.
Tale Creation
[x] Create RStudio Tale
[x] Compose Jupyter Tale
NOTE: Which Jupyter? Each?
[x] Compose OpenRefine Tale
[x] Too many instances
NOTE: Error does not explicitly say that we have hit the max limit
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.
Testing Steps:
Replication Data for: "Agricultural Fires and Health at Birth"
Input data
section matches the uri withData Source
appendedCreate New Tale and Launch
button is disabledCreate New Tale and Launch
science
BUG: No "External Data" appeared, even after Tale was running. Dataset also did not appear under "Manage" after Tale was running
Task 2: Importing a Dataset from DataONE
These test cases cover different scenarios that may happen when importing datasets from DataONE.
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:
Fire influences on forest recovery and associated climate feedbacks in Siberian Larch Forests, Russia
Selected data
section matches the uri withData Source
appendedRstudio
is selected in the Environments widgetCreate New Tale and Launch
button is enabledCreate New Tale and Launch
science
NOTE - Regarding this step:
I'm not sure what this actually means... confirm that the "DataSource"l isted matches the
uri
in the query string?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:
Create New Tale and Launch
NOTE: Accidental(?)
dashboard.local
above - should bedashboard.stage
BUG(?): First dataset is just calledproveit
... is this correct? BUG(?): Second dataset is just calledD6N014NC
... is this correct?Task 4: Shared Behavior
NOTE: There is no
Task 3
in this listThese 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.
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:
https://dataverse.harvard.edu/api/access/datafile/3323458
Selected data
section matches the uri withData Source
appendedCreate New Tale and Launch
button is disabledCreate New Tale and Launch
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:
Selected data
section matches the uri withData Source
appendedCreate New Tale and Launch
button is disabledREAD/WRITE
Create New Tale and Launch
NOTE: is the Tale/Dataset title supposed to be
proveit
? Can't we just include that in the test case from now on? BUG:404.html
appeared under "External Data" BUG: No data ever appeared in the Tale WorkspaceTale metadata tests
The purpose of these tests are to confirm that the metadata files (manifest.json, environment.json, LICENSE) we generate are correct.
[x] manifest.json
manifest.json
file undermetadata/
schema:author
createdBy
aggregates
aggregates
Datasets
[x] environment.json
metadata/environment.json
config
section from girder matches theconfig
section inenvironment.json
[x] LICENSE
LICENSE
fileLICENSE
file matches the selected license on the metadata pageLICENSE
changed appropriatelyPublishing tests
[x] Case 1: No Accounts Configured
Publish tale...
Go to Settings
[x] Case 2: Publishing to a Third Party
Publish tale...
Publish
metadata.xml
LICENSE
README.md
manifest.json
environment.json
Repeat for each third party provider
a. After publishing to each provider, use girder to query the Tale
b. Ensure that the 'pid' field in the 'publishInfo' object has an identifier in a doi format
NOTE: Which options are / are not dev servers? NOTE: Neither
demo.dataverse.org
nordev2.dataverse.org
appeared in the publishers list after connecting an API tokenPublished Location
in Run > metadataPublished Location
has changed to the correct package landing pageZenodo integration tests
doi:10.5281/zenodo.16384
ver_1
https://zenodo.org/record/1172960#.XidIvlNKh24
ver_2
doi:10.5281/zenodo.1172960
ver_2
doi:10.5281/zenodo.608984
ver_2
The register tests the following cases.
BUG: First register had
_ver_2
suffix, not_ver_1
NOTE: For confirming contents, you can't browse into the Dataset from a Tale... easier to do this from the "Manage" pageThe register tests the following cases.
NOTE:
Jupyter%20Lab
in querystring above should beJupyterLab
publishInfo
field on the tale object contains pid, repository, repository_id, uriBUG - First step fails with a stack trace:
After rerunning with https://sandbox.zenodo.org/record/490450#.XjnHHRNKh25:
https://girder.stage.wholetale.org/api/v1/integration/zenodo?doi=10.5072%2Fzenodo.490450&resource_server=sandbox.zenodo.org BUG - modal never shows, AiWT never happens, and I am just redirected to Craig's existing Tale: https://dashboard.stage.wholetale.org/run/5e39d26e8bec16c2663dda16?token=wZrmafFvLyvyeGyKeP8ymzAVcoquvOObLqwwMLjfC6A7SonsvfomfbOE44KqAk2Q
[ ] Publish/import to/from Zenodo Sandbox
NOTE: Is there a specific way to "Import a Zenodo Tale"? Tried
https://girder.stage.wholetale.org/api/v1/integration/zenodo?doi=10.5072%2Fzenodo.490330&resource_server=sandbox.zenodo.org
, but will this actually resolve the DOI? This just redirected me to Browse... NOTE: What does "Download and run local" entail - is there a set of commands for this already?Regression tests
[x] Internal-state problems (#326)
/manage
viewtest123
) and click down into it/manage
viewtest123
folder and close the incognito tab/manage
view of your Home folder[x] Invalid instance ID (#333)
/run/ThisIsObviouslyNotARealID
/browse
page instead[x] Files don't overflow Manage page (#410)
[x] Handle read only Tales (#406)
NOTE: This could be merged with "View Tale" test case (see above) NOTE: Step 2 should be removed, as it does not make sense NOTE: Step 3 should say "View" instead of "Launch" - launching requires write access