UPLOADER: Windows testing
Closed this issue · 4 comments
MattReimer commented
@KellyMWhitehead and @jtgilbert here are the sorts of things I've been testing as a reference of the kinds of cases we need to think about
Form load and Authentication
- Pre-authed used opens form
- Unauthed users opens form
- Authentication fails
- Authentication times-out (1 minute)
- When multiple projects open in viewer dialog shows the correct one.
- When multiple projects open in viewer cancelling and re-opening another shows the right one
- Authed user resets auth with "reset" button
New Project Upload
- SUCCESS: New Project (No Warehouse tag) is uploaded to ORG as PUBLIC
- SUCCESS: Uploaded project can be viewed in Data exchange
- SUCCESS: Exisiting project (with Warehouse tag) is uploaded as new
- SUCCESS: New Project is uploaded to USER
- SUCCESS: New Project is uploaded PRIVATE
- SUCCESS: New Project is uploaded SECRET
- SUCCESS: New Project is uploaded with TAGS
- SUCCESS: Uploading files > 50Mb
- SHOULD_FAIL: Project fails validation
- Broken XML, Malformed XML
- Missing files
- Permissions issues
Modify Project
- Existing project can be visited in Data Exchange
- SHOULD_FAIL: Project has been deleted remotely #116
- SHOULD_FAIL: Project has been modified remotely since this change
- SUCESS: Existing ORG project is modified
- SUCCESS: Existing USER project is modified
- SUCCESS: Uploading files > 50Mb
- SUCCESS: Unchanged Files < 50Mb are detected as existing and skipped
- SUCCESS: Unchanged Files > 50Mb are detected as existing and skipped
- SUCCESS: Tags are changed during upload
Misc and Edge cases:
- SHOULD_FAIL: Unknown project type should load but cannot be uploaded
- SUCCESS: View log button works
- SUCCESS: New project is canceled mid-upload
- SUCCESS: Cancelled project can be restarted successfully
- SHOULD_FAIL: Refuse to upload project from different api
- SHOULD_FAIL: Refuse to upload project with bad project id
- Form can be closed and opened again without losing functionality
jtgilbert commented
I'm getting this error @MattReimer
MattReimer commented
The issue was .graphql files weren't included in the packaging script. should be fixed in the latest zip I sent.
MattReimer commented
Ok. I'm calling this good. We're good for release