-
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 test cases for critical PRs of Jira release 4.0.0 #112
Open
AayushChaudhary0001
wants to merge
4
commits into
mattermost:main
Choose a base branch
from
Brightscout:jira-v4.0.0-critical
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+221
−0
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
ab15394
[MI-3516]: Added test cases for critical PRs of Jira release 4.0.0 (#2)
AayushChaudhary0001 68c2a80
Merge branch 'main' of https://github.com/mattermost/mattermost-test-…
AayushChaudhary0001 aa00b3d
Review fixes of Jira v4.0.0-critical
AayushChaudhary0001 b35193c
Review fixes Of Jira test cases
AayushChaudhary0001 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
43 changes: 43 additions & 0 deletions
43
data/test-cases/plugins/jira/jira-server/install-and-uninstall/OAuth_Setup.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: "OAuth setup for Jira plugin" | ||
status: Active | ||
priority: Normal | ||
folder: Install and Uninstall | ||
authors: "@AayushChaudhary0001" | ||
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. Run the `/jira connect` command. | ||
2. Run the `/jira instance install cloud-oauth <cloud_jira_URL>` | ||
3. Continue the steps provided in the direct message from Jira bot and complete the setup of cloud O-Auth 2.0. | ||
|
||
**Expected** | ||
|
||
The user should be able to complete and install the Jira cloud instance. |
42 changes: 42 additions & 0 deletions
42
data/test-cases/plugins/jira/jira-server/jira-connect/Disconnect_button.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: "Disconnect button for user" | ||
status: Active | ||
priority: Normal | ||
folder: Jira Connect | ||
authors: "@AayushChaudhary0001" | ||
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. Run the `/jira connect` command and connect the user. | ||
2. On the connection confirmation page, click on the disconnect button. | ||
|
||
**Expected** | ||
|
||
The user should be able to disconnect from the Jira instance. |
46 changes: 46 additions & 0 deletions
46
.../test-cases/plugins/jira/jira-server/jira-subscriptions/Comment_Notification.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,46 @@ | ||
--- | ||
# (Required) Ensure all values are filled up | ||
name: "Comment notification for the user" | ||
status: Active | ||
priority: Normal | ||
folder: Jira subscriptions | ||
authors: "@AayushChaudhary0001" | ||
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 subscription on MM for desired project in Jira. | ||
2. Go to the connected Jira instance. | ||
3. Open the subscribed Jira board. | ||
4. Perform any activity(for eg. add any comment) on the desired issue for which the subscription is already created. | ||
5. Go back to the channel in MM. | ||
|
||
**Expected** | ||
|
||
The user should get the comment notification in the channel through the Jira bot. | ||
|
45 changes: 45 additions & 0 deletions
45
...st-cases/plugins/jira/jira-server/jira-subscriptions/DM_Comment_notification.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,45 @@ | ||
--- | ||
# (Required) Ensure all values are filled up | ||
name: "Mention comment notification in DM" | ||
status: Active | ||
priority: Normal | ||
folder: Jira subscriptions | ||
authors: "@AayushChaudhary0001" | ||
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. Go to the connected Jira instance. | ||
2. Open the desired ticket on Jira board. | ||
3. Mention the desired user in the comments. | ||
4. Go back to the connected MM server. | ||
|
||
|
||
**Expected** | ||
|
||
The user should get the comment notification in the DM through the Jira bot. |
45 changes: 45 additions & 0 deletions
45
...-cases/plugins/jira/jira-server/jira-subscriptions/DM_Comment_notification_2.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,45 @@ | ||
--- | ||
# (Required) Ensure all values are filled up | ||
name: "Mention comment notification in DM if username contains @" | ||
status: Active | ||
priority: | ||
folder: Jira subscriptions | ||
authors: "@AayushChaudhary0001" | ||
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. Go to the connected Jira instance. | ||
2. Open the desired ticket on Jira board. | ||
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. Same as above ☝️ |
||
3. Mention the desired user whose username contains "@" in the comments. | ||
4. Go back to the connected MM server. | ||
|
||
**Expected** | ||
|
||
The user should get the comment notification in the DM through the Jira bot. | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
On this point, to prevent a false positive I would add a step that says "Ensure the test user desired user is not the assignee on the ticket"
Assignee get DMs for any comment so we should ensure the user is explicitly not seeing this DM.