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 the test cases for the todo list generated message for Github plugin on MM. #155

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

arush-vashishtha
Copy link
Contributor

Summay

This PR consists the test cases for the updated format of the events in the generated message of Todo list of Github after running the /github todo slash command on MM.

)

* [MM-41]: added the test cases for todo list on github.

* [MM-41]: added the test cases for the todo list.

* [MM-41]: small changes.

* fixed comments by Aayush for some words changing.

* fixed comments by Aayush for some words changing.

* [MM-41]: Fixed the comments by Raghav.

* [MM-41]: Fixed the comment for notification.
@arush-vashishtha
Copy link
Contributor Author

@DHaussermann @saturninoabril Can you please have a look at this?

@lindalumitchell lindalumitchell added the 2: QA Review Requires review by a QA tester label Apr 30, 2024
@DHaussermann
Copy link
Contributor

Thanks @arush-vashishtha this all looks accurate to me.
The script is fine. I will approve for merge once I confirm if we need any further validation of the Zephyr test data.

@DHaussermann DHaussermann self-requested a review May 6, 2024 18:39
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 @arush-vashishtha, overall looks good to me except for few suggestions.


**Step 1**

1. Connect your MM account to Github account.
Copy link
Member

Choose a reason for hiding this comment

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

Please correct proper entity name for "GitHub".

Suggested change
1. Connect your MM account to Github account.
1. Connect your MM account to GitHub account.

@@ -0,0 +1,77 @@
---
# (Required) Ensure all values are filled up
name: "Todo list in the channel or DM/GM using the `/github todo` command."
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
name: "Todo list in the channel or DM/GM using the `/github todo` command."
name: "Todo list in the channel or DM/GM using the `/github todo` command"


**Step 3**

1. Merge any desiered open PR on the connected account on github.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
1. Merge any desiered open PR on the connected account on github.
1. Merge any desired open PR on the connected account on GitHub.

Comment on lines +69 to +77
**Expected**

The generated message should show the list for unread messages, review requests, open PRs and user's assignments with the formats, `owner or organisation/repo <event> : <description>` or `owner or organisation/repo : <description>` in the desired channel or DM/GM on MM.
After step 2, the generated message should not show the closed events in the desired channel or DM/GM on MM.
After step 3, the desired PR should not be visible in the generated message in the desired channel or DM/GM on MM.
After step 4, the desired message should not be visible in the generated message in the desired channel or DM/GM on MM.
After step 5, the desired pending request should not be visible in the generated in the desired channel or DM/GM on MM.
After step 6, the user should be redirected to the desired owner account or organisation on github respectively.
After step 7, the user should be redirected to the desired event on github.
Copy link
Member

Choose a reason for hiding this comment

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

Please organize the steps/expected format as commented here - #161 (review)

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants