GUI acceptance tests using environment deployed from packages.
Build: #1952 failed
Job: Chrome oneprovider hardlinks and symlinks was successful
Stages & jobs
-
Acceptance Test
- Chrome metadata test
- Chrome onepanel ceph spaces
- Chrome onepanel deployment ceph
- Chrome oneprovider ACL directories
- Chrome oneprovider ACL directories privileges remove or create directory
- Chrome oneprovider ACL files multi
- Chrome oneprovider ACL files multi metadata
- 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 directories privileges
- Oneprovider ACL files
- Oneprovider ACL files metadata
- Oneprovider ACL subdirectories
- Oneprovider ACL subdirectories remove
- Oneprovider ACL subfiles
- Oneprovider ACL subjects
- Oneprovider archives incremental and nested
- 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
hardlink info is no longer visible after hardlink removal[1oz 1op deployed]: Test case result
The below summarizes the result of the test " hardlink info is no longer visible after hardlink removal[1oz 1op deployed]" in build 1,952 of Onedata Products - gui acceptance pkg - Chrome oneprovider hardlinks and symlinks.
- Description
- hardlink info is no longer visible after hardlink removal[1oz 1op deployed]
- Test class
- gui.scenarios.test_oneprovider_hardlinks_and_symlinks
- Method
- test_hardlink_info_is_no_longer_visible_after_hardlink_removal[1oz_1op_deployed]
- Jira Issue
-
- Duration
- 46 secs
- Status
- Successful