6.2 KiB
Mattermost component upgrade test plan
Test plan
Build tests
- Built on all supported platforms
- Ran
Trigger:ee-package
and thenqa-subset-test
as well as manualqa-remaining-test-manual
CI jobs ongitlab.com
.
Fresh installation tests
Installed a Linux package created in the build system on a fresh OS installation and ran the following actions, checks, and tests:
-
Installed Linux package with the new Mattermost version:
- Verified that package installation logs/output shows no errors.
- Verified Mattermost version by running
/opt/gitlab/embedded/bin/mattermost version
.
-
Edited
/etc/gitlab/gitlab.rb
and set:external_url
mattermost_external_url
Both URLs should point to the same system so that GitLab and Mattermost are co-located. Example:
external_url 'gitlab.example.com' mattermost_external_url 'mattermost.example.com'
-
Ran
gitlab-ctl reconfigure
. -
Connected to
gitlab.example.com
. -
Navigated to
Admin>Settings>Network>Outbound requests
and addedmattermost.example.com
toLocal IP addresses and domain names that hooks and services can accesss
and clickedSave changes
. -
Navigated to
mattermost.example.com
. -
Verified that single-sign on using GitLab credentials was working:
- Clicked on
or create and account with
GitLab. - When presented with the
Authorize GitLab Mattermost to use your account?
page, clicked onAuthorize
. You should have landed on theSelect teams
page.
- Clicked on
-
Verified that when creating a group in GitLab, checking the box for Create a Mattermost team for this group also created a team in Mattermost and the GitLab user is a member of that team.
-
Created a test project within the group created in the previous step and initialize with a
README
. -
Verified Mattermost slash command operation:
- Enabled slash commands using GitLab documentation.
- Tested slash commands by creating a new issue from the Mattermost instance. After following the prompt to re-authorize, the issue should have been successfully created in GitLab.
-
Verified GitLab issue notification.
- Configured incoming web hooks in Mattermost using the GitLab Documentation. Note that you have to configure both Mattermost and GitLab.
- Using the created web hook, followed the documentation for adding notification support.
- Created an issue in the test project. Verified that the notification for the issue appeared in Mattermost for the GitLab user.
Upgrade installation tests
Install a Linux package from the previous, latest minor number release on a fresh OS installation. Run the following actions, checks, and tests:
-
Installed Linux package from the previous, latest minor number release:
- Verified that package installation logs/output showed no errors.
- Verified Mattermost version by running
/opt/gitlab/embedded/bin/mattermost version
.
-
Edited
/etc/gitlab/gitlab.rb
and set:external_url
mattermost_external_url
Both URLs should point to the same system so that GitLab and Mattermost are co-located. Example:
external_url 'gitlab.example.com' mattermost_external_url 'mattermost.example.com'
-
Ran
gitlab-ctl reconfigure
. -
Connected to
gitlab.example.com
. -
Navigated to
Admin>Settings>Network>Outbound requests
and addedmattermost.example.com
toLocal IP addresses and domain names that hooks and services can accesss
and clickedSave changes
. -
Navigated to
mattermost.example.com
. -
Verified that single-sign on using GitLab credentials is working:
- Clicked on
or create and account with
GitLab. - When presented with the
Authorize GitLab Mattermost to use your account?
page, clicked onAuthorize
. - You should have landed on the
Select teams
page.
- Clicked on
-
Verified that when creating a group in GitLab, checking the box for Create a Mattermost team for this group also created a team in Mattermost and the GitLab user is a member of that team.
-
Created a test project within the group created in the previous step and initialized with a
README
. -
Verified Mattermost slash command operation:
- Enabled slash commands using GitLab documentation.
- Tested slash commands by creating a new issue from the Mattermost instance. After following the prompt to re-authorize, the issue should have been successfully created in GitLab.
-
Verified GitLab issue notification.
- Configured incoming web hooks in Mattermost using the GitLab Documentation. Note that you have to configure both Mattermost and GitLab.
- Using the created web hook, followed the documentation for adding notification support.
- Created an issue in the test project. Verified that the notification for the issue appears in Mattermost for the GitLab user.
Upgrade GitLab with a Linux package created with the new Mattermost version. Run the following actions, checks, and tests:
-
Upgraded to package with new Mattermost version:
- Verified that package installation logs/output shows no errors.
- Verified Mattermost version by running
/opt/gitlab/embedded/bin/mattermost version
.
-
Verified Mattermost slash command operation:
- Tested slash commands by creating a new issue from the Mattermost instance. After following the prompt to re-authorize, the issue should have been successfully created in GitLab.
-
Verified GitLab issue notification.
- Created an issue in the test project. Verified that the notification for the issue appeared in Mattermost for the GitLab user.