forked from mattermost/mattermost-test-management
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[MM-70]: added the test cases for the context menu features and messa…
…ge access request in to-do list. (#32) * [MM-70]:Added the test cases for PR 404. * added the test cases for create gitlab issue * [MM-70]: added the test cases for the message attach to gitlab issue. * Fixed the comments by Aayush. * Review fixes by Raghav Co-authored-by: Raghav Aggarwal <[email protected]> * Review fixes by Raghav Co-authored-by: Raghav Aggarwal <[email protected]> --------- Co-authored-by: Raghav Aggarwal <[email protected]>
- Loading branch information
1 parent
27eb35c
commit 84a548c
Showing
3 changed files
with
134 additions
and
0 deletions.
There are no files selected for viewing
43 changes: 43 additions & 0 deletions
43
data/test-cases/plugins/gitlab/context-menu-feature/Attach_message_gitlab_issue.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
--- | ||
# (Required) Ensure all values are filled up | ||
name: "Add comment to a gitlab issue from the `Attach to GitLab Issue` option in the context menu on MM." | ||
status: Active | ||
priority: Normal | ||
folder: Context-menu-feature | ||
authors: "@arush-vashishtha" | ||
team_ownership: [] | ||
priority_p1_to_p4: P2 - Core Functions (Do core functions work?) | ||
|
||
# (Optional) | ||
location: null | ||
component: null | ||
tags: [] | ||
labels: [] | ||
tested_by_contributor: null | ||
|
||
# (Optional) Test type and tools | ||
cypress: null | ||
detox: null | ||
mmctl: null | ||
playwright: null | ||
rainforest: [] | ||
manual_test_environments: [] | ||
|
||
# Do not change | ||
id: null | ||
key: null | ||
created_on: null | ||
last_updated: null | ||
case_hashed: null | ||
steps_hashed: null | ||
--- | ||
|
||
**Step 1** | ||
|
||
1. Hover cursor over a user message and click on the `message-actions` then select `Attach to GitLab Issue` on MM. | ||
2. In the `Attach Message to GitLab Issue` modal, select the desired Gitlab issue to attach the message and click on `Attach` button on MM. | ||
3. Navigate to the desired issue on the Gitlab. | ||
|
||
**Expected** | ||
|
||
The message should get added as a comment on the desired issue on Gitlab. |
49 changes: 49 additions & 0 deletions
49
data/test-cases/plugins/gitlab/context-menu-feature/Create_gitlab_issue.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
--- | ||
# (Required) Ensure all values are filled up | ||
name: "Create a Gitlab issue from the `Create Gitlab Issue` in the context menu on MM." | ||
status: Active | ||
priority: Normal | ||
folder: Context-menu-feature | ||
authors: "@arush-vashishtha" | ||
team_ownership: [] | ||
priority_p1_to_p4: P2 - Core Functions (Do core functions work?) | ||
|
||
# (Optional) | ||
location: null | ||
component: null | ||
tags: [] | ||
labels: [] | ||
tested_by_contributor: null | ||
|
||
# (Optional) Test type and tools | ||
cypress: null | ||
detox: null | ||
mmctl: null | ||
playwright: null | ||
rainforest: [] | ||
manual_test_environments: [] | ||
|
||
# Do not change | ||
id: null | ||
key: null | ||
created_on: null | ||
last_updated: null | ||
case_hashed: null | ||
steps_hashed: null | ||
--- | ||
|
||
**Step 1** | ||
|
||
1. Hover cursor over a user message and click on the `message-actions` then select `Create Gitlab Issue` on MM. | ||
2. In the `Create Gitlab Issue` modal, select and enter the details as per the requiement for the issue and click on `Submit` button on MM. | ||
3. Navigate to the issues in the selected project on Gitlab. | ||
|
||
**Step 2** | ||
|
||
1. Hover cursor over a user message and click on the `message-actions` then select `Create Gitlab Issue` on MM. | ||
2. In the `Create Gitlab Issue` modal, select and enter the details as per the requiement for the issue and then remove the selected project in the modal on MM. | ||
|
||
**Expected** | ||
|
||
The issue should be created for the selected project on Gitlab. | ||
After step 2, the dropdown menu for additional options should get hidden upon removing the project. |
42 changes: 42 additions & 0 deletions
42
...ugins/gitlab/subscriptions-and-notifications/Todo_list_member_access_request.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
--- | ||
# (Required) Ensure all values are filled up | ||
name: "Member access request in the todo list after entering the `/gitlab todo` slash command." | ||
status: Active | ||
priority: Normal | ||
folder: Subscriptions-and-notifications | ||
authors: "@arush-vashishtha" | ||
team_ownership: [] | ||
priority_p1_to_p4: P2 - Core Functions (Do core functions work?) | ||
|
||
# (Optional) | ||
location: null | ||
component: null | ||
tags: [] | ||
labels: [] | ||
tested_by_contributor: null | ||
|
||
# (Optional) Test type and tools | ||
cypress: null | ||
detox: null | ||
mmctl: null | ||
playwright: null | ||
rainforest: [] | ||
manual_test_environments: [] | ||
|
||
# Do not change | ||
id: null | ||
key: null | ||
created_on: null | ||
last_updated: null | ||
case_hashed: null | ||
steps_hashed: null | ||
--- | ||
|
||
**Step 1** | ||
|
||
1. Create a `member access request` from a different user to any one of your desired public project/group on gitlab. | ||
2. Navigate to the desired channel or DM/GM on MM and enter the slash command `/gitlab todo`. | ||
|
||
**Expected** | ||
|
||
The user should get a list of todo in the desired channel or DM/GM on MM and the notification for member access request should follow the format, `member_access_requested : <user> has requested access to <owner/repo>`. |