diff options
| author | Alfredo Sumaran <alfredo@gitlab.com> | 2016-11-04 05:34:10 +0000 |
|---|---|---|
| committer | Alfredo Sumaran <alfredo@gitlab.com> | 2016-11-04 05:34:10 +0000 |
| commit | a04a451fca4c077709bb60bbe05b04b306fae167 (patch) | |
| tree | 18ecf44896ed32a34bdb4bcce6005b94dd5fb5fc | |
| parent | b0f89867a80fe6edefe0ee5fa47502f166296e37 (diff) | |
| parent | 06dcb0776eb2160ecff4910b9459f31ca6368507 (diff) | |
| download | gitlab-ce-a04a451fca4c077709bb60bbe05b04b306fae167.tar.gz | |
Merge branch 'patch-9' into 'master'
Add tip for using Chrome to run and debug teaspoon tests.
## What does this MR do?
Documents the approach I use when writing and debugging frontend tests, which is (IMHO) much better than running locally from the command line.
See merge request !7257
| -rw-r--r-- | doc/development/frontend.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/development/frontend.md b/doc/development/frontend.md index ece8f880542..1d7d9127a64 100644 --- a/doc/development/frontend.md +++ b/doc/development/frontend.md @@ -196,6 +196,12 @@ It consists of two subtasks: As long as the fixtures don't change, `rake teaspoon:tests` is sufficient (and saves you some time). +If you need to debug your tests and/or application code while they're +running, navigate to [localhost:3000/teaspoon](http://localhost:3000/teaspoon) +in your browser, open DevTools, and run tests for individual files by clicking +on them. This is also much faster than setting up and running tests from the +command line. + Please note: Not all of the frontend fixtures are generated. Some are still static files. These will not be touched by `rake teaspoon:fixtures`. |