5e59b5f70c
* MM-23935 extend session expiry on user activity - if user types anything before a session expires the session will be extended to now + session length - ensures new session expiries are not written to DB too frequently - new session store func for updating session ExpiresAt - session length defaults for mobile and web/ldap changed from 180 days to 30 days |
||
---|---|---|
.. | ||
channel-role-has-permission.csv | ||
development-private-key.asc | ||
development-public-key.asc | ||
development-public-key.gpg | ||
Fake_Team_Import.zip | ||
orientation_test_1_expected_preview.jpeg | ||
orientation_test_1_expected_thumb.jpeg | ||
orientation_test_1.jpeg | ||
orientation_test_2_expected_preview.jpeg | ||
orientation_test_2_expected_thumb.jpeg | ||
orientation_test_2.jpeg | ||
orientation_test_3_expected_preview.jpeg | ||
orientation_test_3_expected_thumb.jpeg | ||
orientation_test_3.jpeg | ||
orientation_test_4_expected_preview.jpeg | ||
orientation_test_4_expected_thumb.jpeg | ||
orientation_test_4.jpeg | ||
orientation_test_5_expected_preview.jpeg | ||
orientation_test_5_expected_thumb.jpeg | ||
orientation_test_5.jpeg | ||
orientation_test_6_expected_preview.jpeg | ||
orientation_test_6_expected_thumb.jpeg | ||
orientation_test_6.jpeg | ||
orientation_test_7_expected_preview.jpeg | ||
orientation_test_7_expected_thumb.jpeg | ||
orientation_test_7.jpeg | ||
orientation_test_8_expected_preview.jpeg | ||
orientation_test_8_expected_thumb.jpeg | ||
orientation_test_8.jpeg | ||
orientation_test.jpeg | ||
qa-data-graph.png | ||
qa-data.ldif | ||
README.md | ||
slack-import-test-channels.json | ||
slack-import-test-direct-messages.json | ||
slack-import-test-group-direct-messages.json | ||
slack-import-test-posts.json | ||
slack-import-test-private-channels.json | ||
slack-import-test-users.json | ||
test_expected_tiff_preview.jpeg | ||
test_expected_tiff_thumb.jpeg | ||
test-attachments.md | ||
test-config.json | ||
test-data-graph.png | ||
test-data.ldif | ||
test-emoticons1.md | ||
test-emoticons2.md | ||
test-emoticons3.md | ||
test-emoticons4.md | ||
test-emoticons5.md | ||
test-emoticons6.md | ||
test-hashtags.md | ||
test-link-preview.md | ||
test-links.md | ||
test-markdown-basics.md | ||
test-markdown-lists.md | ||
test-mentions.md | ||
test-public-key.plugin.gpg | ||
test-search.md | ||
test-slack-attachments.json | ||
test-syntax-highlighting.md | ||
test-tables.md | ||
test.png | ||
test.svg | ||
test.tiff | ||
testgif.gif | ||
testjpg.jpg | ||
testplugin.tar.gz | ||
testplugin.tar.gz.asc | ||
testplugin.tar.gz.sig | ||
testplugin2.tar.gz | ||
testplugin2.tar.gz.asc | ||
testplugin2.tar.gz.sig | ||
tls_test_cert.pem | ||
tls_test_key.pem |
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 coresponding signatures.
First, import the public and privat development key:
$ gpg --import ./development-public-key.gpg
$ gpg --import ./development-private-key.asc
This has to be done only once.
Then update the sigantures:
$ 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.