Skip to content

Commit 9688cdf

Browse files
authored
Update CONTRIBUTING.md
1 parent 4bcb8a2 commit 9688cdf

File tree

1 file changed

+2
-37
lines changed

1 file changed

+2
-37
lines changed

CONTRIBUTING.md

Lines changed: 2 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ For pull request with notable file changes or a big feature developmennt, we hig
3030

3131
#### Git Desktop
3232

33-
Git command veterans might argue that a simple terminal and cherry switch powered keyboard is the most elegant solution. But in general, a desktop tool makes the task easier.
33+
Git command veterans might argue that a simple terminal and a cherry switch keyboard is the most elegant solution. But in general, a desktop tool makes the task easier.
3434

3535
1. https://www.gitkraken.com/git-client
3636
2. https://desktop.github.com/
@@ -59,19 +59,6 @@ Emojis make the commit messages :cherry_blossom:. If you have no idea about what
5959
- :space_invader: `:space_invader:` - Too much space or too little.
6060
- :spaghetti: `:spaghetti:` - copy-pasta, used to signal code that was copy-pasted without being updated
6161

62-
## Testing before your first push
63-
64-
You can use [circleci local cli](https://circleci.com/docs/2.0/local-cli/) to **locally** test your branch before pushing it to origin `plotly/dash`, doing so leaves no chance of making an embarrasing public exposé.
65-
66-
```bash
67-
# install the cli (first time only)
68-
$ curl -fLSs https://circle.ci/cli | bash && circleci version
69-
70-
# trigger a local circleci container session
71-
# you should run at least one python version locally
72-
# note: the current config requires all tests pass on python 2.7, 3.6 and 3.7.
73-
$ circleci local execute --job python-3.6
74-
```
7562
### Coding Style
7663

7764
We use both `flake8` and `pylint` for basic linting check, please refer to the relevant steps in `.circleci/config.yml`.
@@ -88,31 +75,9 @@ Note: *You might find out that we have more integration tests than unit tests in
8875

8976
### Integration Tests
9077

91-
We create various miminal dash apps to cover feature scenario. A server is launched in mutli-thread or multi-process flavor and the test steps are executed in browsers driving by selenium webdrivers.
92-
93-
Any reasonable test scenario is encouraged to be added along with the same PR.
94-
95-
### Visual regression with Percy
96-
97-
Testing graph-intensive-application is a challenging job. We use [percy](https://percy.io/) to mitigate the pain, please pay attention if percy reports visual differences. If you are not sure whether the change is expected, leave a comment, and don't blind-approve it.
78+
We introduced the `dash.testing` feature in Dash 1.0. It makes writing an Dash integration test much easier. Please read the [tutorial](http://dash.plot.ly/testing) and contribute your feature code along with a decent integration test if applicable.
9879

9980

100-
## Test variable tips
101-
You can configure the test server with the following variables:
102-
103-
### DASH_TEST_CHROMEPATH
104-
If you run a special chrome, set the path to your chrome binary with this environment variable.
105-
106-
### DASH_TEST_PROCESSES
107-
If you encounter errors about Multi-server + Multi-processing when running under Python 3, try running the tests with the number of server processes set to 1.
108-
109-
### Example: single test run with configuration
110-
111-
```bash
112-
DASH_TEST_CHROMEPATH=/bin/google-chrome-beta DASH_TEST_PROCESSES=1
113-
pytest -k test_no_callback_context
114-
```
115-
11681
## Financial Contributions
11782

11883
Dash, and many of Plotly's open source products, have been funded through direct sponsorship by companies. [Get in touch] about funding feature additions, consulting, or custom app development.

0 commit comments

Comments
 (0)