Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
E
edx-platform-release
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
1
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Hsin-Yu Chien
edx-platform-release
Commits
421a9cc0
Commit
421a9cc0
authored
9 years ago
by
Andy Armstrong
Browse files
Options
Downloads
Patches
Plain Diff
Add details about debugging Jasmine tests
parent
6b7f1bce
Loading
Loading
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/en_us/internal/testing.rst
+12
-1
12 additions, 1 deletion
docs/en_us/internal/testing.rst
with
12 additions
and
1 deletion
docs/en_us/internal/testing.rst
+
12
−
1
View file @
421a9cc0
...
...
@@ -281,7 +281,7 @@ console::
paver test_js_run -s common
paver test_js_run -s common-requirejs
To run JavaScript tests in
your default
browser:
:
To run JavaScript tests in
a
browser:
paver test_js_dev -s lms
paver test_js_dev -s lms-coffee
...
...
@@ -290,6 +290,17 @@ To run JavaScript tests in your default browser::
paver test_js_dev -s xmodule
paver test_js_dev -s common
paver test_js_dev -s common-requirejs
To debug these tests on devstack in a local browser:
* first run the appropriate test_js_dev command from above which will open a browser using XQuartz
* open the same URL in your browser but change the IP address to 192.168.33.10, e.g.
http://192.168.33.10:TEST_PORT/suite/cms
* this will run all the tests and show you the results including details of any failures
* you can click on an individually failing test and/or suite to re-run it by itself
* you can now use the browser's developer tools to debug as you would any other JavaScript code
Note: the port is also output to the console that you ran the tests from if you find that easier.
These paver commands call through to a custom test runner. For more
info, see `js-test-tool <https://github.com/edx/js-test-tool>`__.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment