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
@@ -65,6 +69,11 @@ You can also run a single test with the following command: `tox -e py36 -- -s -v
65
69
* Note that the coverage test will fail if you only run a single test, so make sure to surround the command with `export IGNORE_COVERAGE=-` and `unset IGNORE_COVERAGE`
You can also run the unit tests with the following options:
74
+
* Right click on a test file in the Project tree and select `Run/Debug 'pytest' for ...`
75
+
* Right click on the test definition and select `Run/Debug 'pytest' for ...`
76
+
* Click on the green arrow next to test definition
68
77
69
78
### Running the Integration Tests
70
79
@@ -168,6 +177,33 @@ Please remember to:
168
177
Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels ((enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/aws/aws-step-functions-data-science-sdk-python/labels/help%20wanted) issues is a great place to start.
169
178
170
179
180
+
## Setting Up Your Development Environment
181
+
182
+
### Setting Up Your Environment for Debugging
183
+
184
+
Setting up your IDE for debugging tests locally will save you a lot of time.
185
+
You might be able to `Run` and `Debug` the tests directly in your IDE with your default settings, but if it's not the case,
186
+
follow the steps described in this section.
187
+
188
+
#### PyCharm
189
+
1. Set your Default test runner to `pytest`in _Preferences → Tools → Python Integrated Tools_
190
+
1. If you are using `PyCharm Professional Edition`, go to _Preferences → Build, Execution, Deployment → Python Debugger_ and set the options with following values:
0 commit comments