You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/contributing.rst
+19-40Lines changed: 19 additions & 40 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,11 +31,11 @@ Notes on the Test Suite
31
31
32
32
To test all the API endpoints, the account that you use for testing must be an *admin* user for your Webex Teams Organization. Additionally, you should know that that the testing process creates some test people, rooms, messages, teams, and etc. as part of executing the test suite. We strongly recommend *NOT* running the test suite using your personal Webex Teams account (not that you can't; it's just that you probably don't want it cluttering your account with all these test artifacts).
33
33
34
-
If you cannot create a test account with *admin* privileges or configure your environment to run the test suite locally, you may always submit your code via a pull request. Our GitHub/Travis CI setup runs the test suite against all pull requests. All tests must pass before your pull request is accepted.
34
+
If you cannot create a test account with *admin* privileges or configure your environment to run the test suite locally, you may always submit your code via a pull request. We will test your code before merging and releasing the changes.
35
35
36
36
37
-
Contributing Code - Using the CI Automated Testing
1. Check for open `issues`_ or create a new *issue* for the item you want to work on and make sure to comment and let us know that you are working on it.
41
41
@@ -57,54 +57,33 @@ Contributing Code - Using the CI Automated Testing
57
57
58
58
7. Commit your changes.
59
59
60
-
8. Submit a `pull request`_. The GitHub/Travis CI system runs the test suite against your pull request code. If any tests fail, please review your changes. If everything looks good, we will gladly merge your request!
61
-
62
-
63
-
Contributing Code - Running the Test Suite Locally
1. Check for open `issues`_ or create a new 'issue' for the item you want to work on and make sure to comment and let us know that you are working on it.
67
-
68
-
2. Fork a copy of the `repository`_ and clone your forked repository to your development environment.
69
-
70
-
Run ``script/setup`` to install the development dependencies and setup your environment.
71
-
72
-
3. Configure the following environment variables in your development environment:
60
+
8. Submit a `pull request`_.
73
61
74
-
* ``WEBEX_TEAMS_ACCESS_TOKEN`` - Your test account's Webex Teams access token.
75
-
76
-
* ``WEBEX_TEAMS_TEST_DOMAIN`` - The test suite creates some users as part of the testing process. The test suite uses this domain name as the e-mail suffix of for the user's e-mail addresses.
77
-
78
-
* ``WEBEX_TEAMS_TEST_ID_START`` - The test suite uses this integer as the starting number for creating test user accounts (example: "test42@domain.com").
79
-
80
-
* ``WEBEX_TEAMS_TEST_FILE_URL`` - Configure this environment variable with a URL referencing a file that can be downloaded and posted to Webex Teams as part of the testing process.
81
62
82
-
*Example:*
63
+
Running the Test Suite Locally
64
+
------------------------------
83
65
84
-
.. code-block:: bash
66
+
Configure the following environment variables in your development environment:
* ``WEBEX_TEAMS_ACCESS_TOKEN`` - Your test account's Webex Teams access token.
91
69
70
+
* ``WEBEX_TEAMS_TEST_DOMAIN`` - The test suite creates some users as part of the testing process. The test suite uses this domain name as the e-mail suffix of for the user's e-mail addresses.
92
71
93
-
4. Add your code to your forked repository.
72
+
* ``WEBEX_TEAMS_TEST_ID_START`` - The test suite uses this integer as the starting number for creating test user accounts (example: "test42@domain.com").
94
73
95
-
If you are creating some new feature or functionality (excellent!), please also write a `test`_ to verify that your code works as expected.
96
-
97
-
5. We follow `PEP8`_ reasonably strictly for this project. Please make sure your code passes the linter.
98
-
99
-
Run ``script/test lint`` or simply run ``flake8`` from the project root.
74
+
* ``WEBEX_TEAMS_TEST_FILE_URL`` - Configure this environment variable with a URL referencing a file that can be downloaded and posted to Webex Teams as part of the testing process.
100
75
101
-
6. Commit your changes.
76
+
*Example:*
102
77
103
-
7. Ensure your code passes all of the default tests.
78
+
.. code-block:: bash
104
79
105
-
Run ``script/test`` and ensure all tests execute successfully.
0 commit comments