-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gui testcases 3075 #3146
Gui testcases 3075 #3146
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, fix minor notes before the merge (see details in comments).
| 10 | Open the **Settings** page | | | ||
| 11 | Open the **SYSTEM MANAGEMENT** tab | | | ||
| 12 | Select the **LOGS** tab | | | ||
| 13 | Click ***Show advanced*** button | | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest to add an action like "Clear the field From" - as by default logs are shown from the moment of the opening Logs form.
| 7 | Open the **Settings** page | | | ||
| 8 | Open the **SYSTEM MANAGEMENT** page | | | ||
| 9 | Select the **LOGS** tab | | | ||
| 10 | Click ***Show advanced*** button | | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest to add an action like "Clear the field From" - as by default logs are shown from the moment of the opening Logs form.
3. Open the **SYSTEM MANAGEMENT** page | ||
4. Select the **LOGS** tab | ||
5. Click ***Show advanced*** button | ||
6. Click **Type** field and select `audit` value from drop-down |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest to add an action like "Clear the field From" - as by default logs are shown from the moment of the opening Logs form.
| 10 | Logout and _Check audit log_ (see below) | Record <br> `WRITE cp://storage1/file3` <br> is shown in the top of logs records | | ||
| 11 | Repeat steps 5-9 for `cp <destination_folder>/storage1/file1 <destination_folder>/storage2/file1` command | Records <br>`READ cp://storage1/file1` <br> `WRITE cp://storage2/file1` <br> are shown in the top of logs records | | ||
| 12 |Repeat steps 5-9 for `cat <destination_folder>/storage1/file2` command | Records <br>`READ cp://storage1/file1` <br> is shown in the top of logs records | | ||
| 13 | Repeat steps 5-9 for `mv <destination_folder>/storage1/file2 <destination_folder>/storage2` command | Record <br> `MOVE cp://storage1/file2 cp://storage2/file2` <br> is shown in the top of logs records | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it correct record MOVE
in the Logs?
| 9 | Enter and perform the `echo "test info" >> <destination_folder>/storage1/file3` command | | | ||
| 10 | Logout and _Check audit log_ (see below) | Record <br> `WRITE cp://storage1/file3` <br> is shown in the top of logs records | | ||
| 11 | Repeat steps 5-9 for `cp <destination_folder>/storage1/file1 <destination_folder>/storage2/file1` command | Records <br>`READ cp://storage1/file1` <br> `WRITE cp://storage2/file1` <br> are shown in the top of logs records | | ||
| 12 |Repeat steps 5-9 for `cat <destination_folder>/storage1/file2` command | Records <br>`READ cp://storage1/file1` <br> is shown in the top of logs records | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose, record READ cp://storage1/file2
shall be in Logs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
| 9 | Logout | | | ||
| 10 | Open link stored at the step 5 of the Preparations. Login as the non-admin user from the prerequisites | The page with the header ***storage1-share-1*** appears that contains only `file1` and `folder1` created at step 3 of the Preparations | | ||
| 11 | Click **Download** button near the `file1` name | | | ||
| 12 | Logout and _Check audit log_ (see below) | Record <br> `READ storage1/file1` <br> is shown in the top of logs records | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add the section After in which the storage created at the Preparations shall be removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
| 9 | Logout | | | ||
| 10 | Open link stored at the step 5 of the Preparations. Login as the non-admin user from the prerequisites | The page with the header ***storage1-share-1*** appears that contains only `file1` and `folder1` created at step 3 of the Preparations | | ||
| 11 | Click **Download** button near the `file1` name | | | ||
| 12 | Logout and _Check audit log_ (see below) | Record <br> `READ storage1/file1` <br> is shown in the top of logs records | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add Check audit log section - similar to the one in tests 3059_3-3059_5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
| 13 | Repeat steps 1-12 for `pipe storage -r mv storage1/folder2 storage2/folder2` command | For each files from folder2 (*inner_file3* and *inner_file4*) records <br> `READ storage1/folder2/<file>` <br> `WRITE storage2/folder2/<file>` <br> `DELETE storage1/folder2/<file>` <br> are shown in the top of logs records | | ||
| 14 | Repeat steps 1-12 for `pipe storage rm -r storage1/folder1 -y` command | For each files from folder1 (*inner_file1* and *inner_file2*) record <br> `DELETE storage1/folder1/<file>` <br> is shown in the top of logs records | | ||
|
||
**After:** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest to remove the section After, as this run is still need in the case 3075
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
| 8 | Open the **SYSTEM MANAGEMENT** page | | | ||
| 9 | Select the **LOGS** tab | | | ||
| 10 | Click ***Show advanced*** button | | | ||
| 11 | Click **Type** field and select `audit` value from drop-down | Record <br> `WRITE storage2/file3` <br> is shown in the top of logs records | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest to add an action like "Clear the field From" - as by default logs are shown from the moment of the opening Logs form.
| 15 | Repeat steps 1-12 for `rm -f cloud-data/storage2/file2` command | Record <br> `DELETE storage2/file2` <br> is shown in the top of logs records | | ||
|
||
**After:** | ||
- Stop run launched at step 4 of [3059_2](3059_2.md) case |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add the item:
"- Delete storages created at step 2 in the Preparations of 3059_1 case"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
This PR adds testcases for Audit pipe mount operations #3075 and Data access audit #3059