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
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
77 changes: 77 additions & 0 deletions data/test-cases/plugins/github/general/todo_list.md
Original file line number Diff line number Diff line change
@@ -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"

status: Active
priority: Normal
folder: General
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. 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.

2. Create a notification for any desired event e.g. discussion, issue, pulls, etc on GitHub.
3. Navigate to MM and run the `/github todo` command in any desired channel or DM/GM on MM.

**Step 2**

1. After step 1, close the created event on the connected account on github.
2. Run the `/github todo` command again in any desired channel or DM/GM on MM.

**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.

2. Run the `/github todo` command in any desired channel or DM/GM on MM.

**Step 4**

1. Read any desired unread message on the connected account on github.
2. Run the `/github todo` command in any desired channel or DM/GM on MM.

**Step 5**

1. Approve any desired pending requested review on the connected account on github.
2. Run the `/github todo` command in any desired channel or DM/GM on MM.

**Step 6**

1. After step 1, Click on the desired `owner` or `organisation` hyperlink part of the generated list on MM.

**Step 7**

1. After step 1, Click on the desired <description> hyperlink part of the generated list on MM.

**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.
Comment on lines +69 to +77
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)