* Updated privacy policy link * Removed broken link from fa language * Updated terms of use link * Updated pricing links * Updated self hosted billing links * Updated terms-of-use links * Updated privacy-policy links across the project * Updated pricing links in e2e tests * Updated cloud billing docs * Fixed upgrading mattermost server links * Updated ssl client certificate links * Updated configure session lenghts links * Updated configure site url links * Updated elasticsearch links * Update data retention policy links * Updated ldap links * advanced-permissions * Updated anchor ServiceSettings.ListenAddress * Updated anchor #SystemSettings.Forward80To443 * Updated link desktop managed resources * Updated elasticsearch links * Updated file content extraction links * Updated HA Cluster inks * Updated setup image proxy link * Updated push notification links * Update performance monitoring links * Help links * Updated about mattermost links * updated report a problem links * Updated download apps links * Updated mobile apps links * Update share messages links * Updated format messages links * Updated in product notices links * Updated multi factor auth links * Updated LDAP links * Updated setup saml links * Updated saml/ldap configuration links * Updated plugins URL * Updated plugin signing links * Updated webhook links * Updated slash commands links * Updated oauth2 links * Updated webhook links * Update enable oauth2 links * Updated personal access tokens list * Updated experimental links * Updated snap files * check-style * privacy/terms links in about modal
Testing Text Processing
The text processing tests located in the doc/developer/tests folder are designed for use with the /test url command. This command posts the raw contents of a specified .md file in the doc/developer/test folder into Mattermost.
Turning on /test
Access the System Console from the Main Menu. Under Service Settings make sure that Enable Testing is set to true, then click Save. You may also change this setting from config.json by setting ”EnableTesting”: true. Changing this setting requires a server restart to take effect.
Running the Tests
In the text input box in Mattermost, type: /test url [file-name-in-testing-folder].md. Some examples:
/test url test-emoticons.md
/test url test-links.md
Notes:
- If a test has prerequisites, make sure your Mattermost setup meets the requirements described at the top of the test file.
- Some tests are over 4000 characters in length and will render across multiple posts.
Manual Testing
It is possible to manually test specific sections of any test, instead of using the /test command. Do this by clicking Raw in the header for the file when it’s open in GitHub, then copy and paste any section into Mattermost to post it. Manual testing only supports sections of 4000 characters or less per post.
Test plugins
There are two test plugins: testplugin.tar.gz and testplugin2.tar.gz. These are use in some integration tests in the api4 package. Any changes to the plugin bundles require updating the corresponding signatures.
First, import the public and private development key:
gpg --import ./development-public-key.gpg
gpg --import ./development-private-key.asc
This has to be done only once.
Then update the signatures:
gpg -u F3FACE45E0DE642C8BD6A8E64C7C6562C192CC1F --verbose --personal-digest-preferences SHA256 --detach-sign testplugin.tar.gz
gpg -u F3FACE45E0DE642C8BD6A8E64C7C6562C192CC1F --verbose --personal-digest-preferences SHA256 --detach-sign --armor testplugin.tar.gz
gpg -u F3FACE45E0DE642C8BD6A8E64C7C6562C192CC1F --verbose --personal-digest-preferences SHA256 --detach-sign testplugin2.tar.gz
gpg -u F3FACE45E0DE642C8BD6A8E64C7C6562C192CC1F --verbose --personal-digest-preferences SHA256 --detach-sign --armor testplugin2.tar.gz
Finally, include the updates bundles and signatures in your commit.