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 revoking the application on gitlab and proper message is displayed for member access request in todo. #156

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

Conversation

arush-vashishtha
Copy link
Contributor

Summary

The following PR consists the test cases for the following scenarios,

  • Revoking the application on Gitlab.
  • Display proper message for member access request in todo in RHS of Gitlab on MM.

…and proper message is displayed for member access request in todo. (#27)

* [MM-54]: Added the test cases for revoking the application on gitlab.

* [MM-54]: added the file for PR 407.

* [MM-54]: fixed the comments by Aayush.

* [MM-54]: fixed the comments by Aayush'

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

* [MM-54]: replaced private with public for projects/groups on gitlab.
@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 DHaussermann self-requested a review May 3, 2024 17:00
@DHaussermann
Copy link
Contributor

This looks good @arush-vashishtha . It's nice to see coverage this deep on the functionality.

The script is fine. I will approve for merge once I confirm if we need any further validation of the Zephyr test data.

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 except for few suggestions.

@@ -0,0 +1,50 @@
---
# (Required) Ensure all values are filled up
name: "Merge request message is rendered properly in the RHS of gitlab on MM"
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: "Merge request message is rendered properly in the RHS of gitlab on MM"
name: "Merge request message is rendered properly in the RHS"

Comment on lines +35 to +50
**Step 1**

1. Generate a access request to your desired public project/group from another user on Gitlab.
2. Navigate to MM and click on the `To-do list` icon in the LHS menu on MM.
3. Check the desired member access request in the RHS of `To-do list` on MM.

**Step 2**

1. Accept or reject any desired member access request on Gitlab.
2. Navigate to MM and click on the `To-do list` icon in the LHS menu on MM.
3. Check the desired member access request in the RHS of `To-do list` on MM.

**Expected**

The member access request to the desired public project/group should be shown with proper description of the request and in proper UI in the RHS of Gitlab on MM.
After step 2, the desired member access request should be removed from the `To-do list` in RHS of Gitlab on MM.
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)

@@ -0,0 +1,57 @@
---
# (Required) Ensure all values are filled up
name: "Refresh the sidebar after revoking the application from the gitlab."
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: "Refresh the sidebar after revoking the application from the gitlab."
name: "Refresh the sidebar after revoking the application from GitLab"


**Step 1**

1. Revoke the OAuth token for your app from the connected gitlab account.
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. Revoke the OAuth token for your app from the connected gitlab account.
1. Revoke the OAuth token for your app from the connected GitLab account.

**Step 1**

1. Revoke the OAuth token for your app from the connected gitlab account.
2. Navigate to MM and click on the refresh button in the LHS of gitlab.
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
2. Navigate to MM and click on the refresh button in the LHS of gitlab.
2. Navigate to MM and click on the refresh button in the LHS of GitLab.

**Step 3**

1. Revoke the OAuth token for your app from the connected gitlab account.
2. Navigate to MM and enter any slash command that fetches the data from the gitlab.
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
2. Navigate to MM and enter any slash command that fetches the data from the gitlab.
2. Navigate to MM and enter any slash command that fetches the data from GitLab.


1. Revoke the OAuth token for your app from the connected gitlab account.
2. Navigate to MM and enter any slash command that fetches the data from the gitlab.
3. Open the DM from Gitlab bot.
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
3. Open the DM from Gitlab bot.
3. Open the DM from GitLab bot.


**Expected**

All the Gitlab icons in the LHS should be removed and the user should get a message in the DM from Gitlab bot that their account has been disconnected on MM.
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
All the Gitlab icons in the LHS should be removed and the user should get a message in the DM from Gitlab bot that their account has been disconnected on MM.
All the GitLab icons in the LHS should be removed and the user should get a message in the DM from GitLab bot that their account has been disconnected on MM.

**Expected**

All the Gitlab icons in the LHS should be removed and the user should get a message in the DM from Gitlab bot that their account has been disconnected on MM.
After step 2, all the Gitlab icons in the LHS should be removed and the user should get a message in the DM from Gitlab bot that their account has been disconnected on MM.
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
After step 2, all the Gitlab icons in the LHS should be removed and the user should get a message in the DM from Gitlab bot that their account has been disconnected on MM.
After step 2, all the GitLab icons in the LHS should be removed and the user should get a message in the DM from GitLab bot that their account has been disconnected on MM.


All the Gitlab icons in the LHS should be removed and the user should get a message in the DM from Gitlab bot that their account has been disconnected on MM.
After step 2, all the Gitlab icons in the LHS should be removed and the user should get a message in the DM from Gitlab bot that their account has been disconnected on MM.
After step 3, all the Gitlab icons in the LHS should be removed and the user should get a message in the DM from Gitlab bot that their account has been disconnected on MM.
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
After step 3, all the Gitlab icons in the LHS should be removed and the user should get a message in the DM from Gitlab bot that their account has been disconnected on MM.
After step 3, all the GitLab icons in the LHS should be removed and the user should get a message in the DM from GitLab bot that their account has been disconnected on MM.

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)

@DHaussermann
Copy link
Contributor

/update-branch

@DHaussermann
Copy link
Contributor

@arush-vashishtha can you also try bringing your branch current to see if GitHub shows a pipeline running?

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