-
Notifications
You must be signed in to change notification settings - Fork 18
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
Added the test cases for the context menu features and message access request in to-do list. #158
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
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 | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
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. |
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." | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
status: Active | ||||||
priority: Normal | ||||||
folder: Context-menu-feature | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
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. | ||||||
Comment on lines
+46
to
+49
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please arrange the format to follow steps/expected as commented here - #161 (review) |
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 | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
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. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
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>`. |
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.