Skip to content
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
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

AayushChaudhary0001
Copy link
Contributor

@AayushChaudhary0001 AayushChaudhary0001 commented Sep 18, 2023

Summary
This consist of the test cases of critical PR's of Jira release 4.0.0

Test coverage for:-
mattermost/mattermost-plugin-jira#951
mattermost/mattermost-plugin-jira#949
mattermost/mattermost-plugin-jira#953
mattermost/mattermost-plugin-jira#946
mattermost/mattermost-plugin-jira#961

Is the feature in stable branch or under review?
Feature in stable branch (master, main)?

* [MI-3516]: Added the extra test cases in this PR

* [MI-3516]: Added an extra test cases in this PR

* [MI-3516]: Added an extra test cases in this PR

* [MI-3516]:Fixed review comments

* [MI-3516]:Fixed a review comments

* [MI-3516] Review fix

Co-authored-by: kshitij katiyar <[email protected]>

---------

Co-authored-by: kshitij katiyar <[email protected]>
@AayushChaudhary0001 AayushChaudhary0001 changed the title [MI-3516]: Added test cases for critical PRs of Jira release 4.0.0 Added test cases for critical PRs of Jira release 4.0.0 Sep 18, 2023
@saturninoabril saturninoabril added the 2: QA Review Requires review by a QA tester label Sep 20, 2023
@saturninoabril
Copy link
Member

/update-branch

Copy link
Member

@saturninoabril saturninoabril left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @AayushChaudhary0001! Looks good to me except few comments. Also, please update your branch to latest. You may validate your change locally by deno task validate and fix error before pushing. Let me know if you need help.

Copy link
Member

@saturninoabril saturninoabril left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating. See comments.

Copy link
Member

@saturninoabril saturninoabril left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @AayushChaudhary0001, LGTM!

**Step 1**

1. Go to the connected Jira instance.
2. Open the desired ticket on Jira board.
Copy link
Contributor

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.

**Step 1**

1. Go to the connected Jira instance.
2. Open the desired ticket on Jira board.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above ☝️

@DHaussermann
Copy link
Contributor

This is great @AayushChaudhary0001!
Just 2 small steps I would add to the script here.

@saturninoabril
Copy link
Member

@DHaussermann Just following up on next step here. Thanks!

@DHaussermann
Copy link
Contributor

@AayushChaudhary0001 just to circle back to this. There was 1 check suggested on 2 of the tests.

@DHaussermann DHaussermann added the Awaiting Submitter Action Blocked on the author label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2: QA Review Requires review by a QA tester Awaiting Submitter Action Blocked on the author
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants