kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

add documentation for karma testing with specific files/folders

Browse source
This commit is contained in:
Lukas Eipert 2018-04-10 12:03:46 +02:00
parent 267602fe84
commit 029180f016
No known key found for this signature in database
GPG key ID: 148BEA37CB35B2AC
1 changed files with 21 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
doc/development/testing_guide/frontend_testing.md
View file

@ -152,19 +152,33 @@ is sufficient (and saves you some time).
### Live testing and focused testing
While developing locally, it may be helpful to keep karma running so that you
can get instant feedback on as you write tests and modify code. To do this
you can start karma with `npm run karma-start`. It will compile the javascript
can get instant feedback on as you write tests and modify code. To do this
you can start karma with `yarn run karma-start`. It will compile the javascript
assets and run a server at `http://localhost:9876/` where it will automatically
run the tests on any browser which connects to it. You can enter that url on
run the tests on any browser which connects to it. You can enter that url on
multiple browsers at once to have it run the tests on each in parallel.
While karma is running, any changes you make will instantly trigger a recompile
and retest of the entire test suite, so you can see instantly if you've broken
a test with your changes. You can use [jasmine focused][jasmine-focus] or
a test with your changes. You can use [jasmine focused][jasmine-focus] or
excluded tests (with `fdescribe` or `xdescribe`) to get karma to run only the
tests you want while you're working on a specific feature, but make sure to
remove these directives when you commit your code.
It is also possible to only run karma on specific folders or files by simply
appending the file name to the karma command:
```bash
# Run all files
yarn karma-start
# Run specific spec files
yarn karma-start profile/account/components/update_username_spec.js
# Run specific spec folder
yarn karma-start profile/account/components/
# Run all specs in vue_shared and vue_mr_widget
yarn karma-start /vue_shared/ /vue_mr_widget/
```
## RSpec feature integration tests
Information on setting up and running RSpec integration tests with
@ -176,7 +190,7 @@ Information on setting up and running RSpec integration tests with
Similar errors will be thrown if you're using JavaScript features not yet
supported by the PhantomJS test runner which is used for both Karma and RSpec
tests. We polyfill some JavaScript objects for older browsers, but some
tests. We polyfill some JavaScript objects for older browsers, but some
features are still unavailable:
- Array.from
@ -188,7 +202,7 @@ features are still unavailable:
- Symbol/Symbol.iterator
- Spread
Until these are polyfilled appropriately, they should not be used. Please
Until these are polyfilled appropriately, they should not be used. Please
update this list with additional unsupported features.
### RSpec errors due to JavaScript
@ -223,7 +237,7 @@ end
### Spinach errors due to missing JavaScript
NOTE: **Note:** Since we are discouraging the use of Spinach when writing new
feature tests, you shouldn't ever need to use this. This information is kept
feature tests, you shouldn't ever need to use this. This information is kept
available for legacy purposes only.
In Spinach, the JavaScript driver is enabled differently. In the `*.feature`