GUI acceptance tests using environment deployed from packages.
Build: #1922 failed
Job: Chrome metadata test was successful
Stages & jobs
-
Acceptance Test
- Chrome metadata test
- Chrome onepanel ceph spaces
- Chrome onepanel deployment ceph
- Chrome oneprovider ACL directories
- Chrome oneprovider ACL files multi
- Chrome oneprovider hardlinks and symlinks
- Chrome onezone automations tests
- Chrome onezone providers sync test
- Chrome transfers multi browser tests
- Chrome transfers tests
- Metadata
- Multiprovider basic
- Multiprovider multiuser
- Multiprovider QoS
- Onepanel basic
- Onepanel deployment basic
- Onepanel login
- Onepanel members
- Onepanel two hosts deployment
- Oneprovider ACL basic
- Oneprovider ACL files
- Oneprovider ACL subdirectories
- Oneprovider data tab
- Oneprovider datasets
- Oneprovider upload
- Onezone automations
- Onezone basic
- Onezone data discovery
- Onezone groups basic
- Onezone groups multiuser
- Onezone harvesters basic
- Onezone providers basic
- Onezone spaces basic
- Onezone spaces multiuser
- Onezone tokens
- POSIX multiuser
- Public shares
- Shares basic
- Storage sync
add valid metadata in json format[1oz 1op deployed-file metadata-file1]: Test case result
The below summarizes the result of the test " add valid metadata in json format[1oz 1op deployed-file metadata-file1]" in build 1,922 of Onedata Products - gui acceptance pkg - Chrome metadata test.
- Description
- add valid metadata in json format[1oz 1op deployed-file metadata-file1]
- Test class
- gui.scenarios.test_metadata
- Method
- test_add_valid_metadata_in_json_format[1oz_1op_deployed-File metadata-file1]
- Duration
- 36 secs
- Status
- Successful