GUI acceptance tests using environment deployed from packages.
Build: #1965 failed
Job: Oneprovider hardlinks was successful
Stages & jobs
-
Acceptance Test
- Chrome metadata test
- Chrome onepanel ceph spaces
- Chrome onepanel deployment ceph
- Chrome onezone automations tests
- Chrome transfers multi browser tests
- Metadata
- Multiprovider basic
- Multiprovider multiuser
- Multiprovider QoS
- Multiprovider QoS storage
- Onepanel basic
- Onepanel deployment basic
- Onepanel login
- Onepanel members
- Onepanel two hosts deployment
- Oneprovider ACL basic
- Oneprovider ACL directories privileges
- Oneprovider ACL directories privileges create
- Oneprovider ACL directories privileges metadata
- Oneprovider ACL directories privileges remove
- Oneprovider ACL files
- Oneprovider ACL files metadata
- Oneprovider ACL remove file
- Oneprovider ACL subdirectories
- Oneprovider ACL subdirectories remove
- Oneprovider ACL subfiles
- Oneprovider ACL subjects
- Oneprovider archives incremental and nested
- Oneprovider data tab
- Oneprovider datasets
- Oneprovider datasets privileges
- Oneprovider hardlinks
- Oneprovider symlinks
- Oneprovider upload
- Onezone automations
- Onezone basic
- Onezone data discovery
- Onezone data discovery helpers
- Onezone data discovery querying
- Onezone groups basic
- Onezone groups multiuser
- Onezone groups multiuser single group
- Onezone harvesters basic
- Onezone harvesters effective privileges
- Onezone harvesters index
- Onezone harvesters index metadata
- Onezone harvesters memberships privileges
- Onezone harvesters privileges add and remove
- Onezone invite tokens
- Onezone invite tokens with caveats
- Onezone invite tokens with consumer caveats
- Onezone providers basic
- Onezone spaces basic
- Onezone spaces memberships privileges
- Onezone spaces memberships privileges data
- Onezone spaces multiuser
- Onezone tokens
- Onezone tokens delete
- POSIX multiuser
- Public shares
- QoS basic
- QoS storage
- Shares basic
- Storage sync
- Storage sync charts
- Transfers directories
- Transfers files
new metadata and qos are inherited by all hardlinks after file browser refresh[1oz 1op deployed]: Test case result
The below summarizes the result of the test " new metadata and qos are inherited by all hardlinks after file browser refresh[1oz 1op deployed]" in build 1,965 of Onedata Products - gui acceptance pkg - Chrome oneprovider hardlinks.
- Description
- new metadata and qos are inherited by all hardlinks after file browser refresh[1oz 1op deployed]
- Test class
- gui.scenarios.test_oneprovider_hardlinks
- Method
- test_new_metadata_and_qos_are_inherited_by_all_hardlinks_after_file_browser_refresh[1oz_1op_deployed]
- Jira Issue
-
- Duration
- 2 mins
- Status
- Successful