mirror of
https://github.com/gitlabhq/gitlabhq.git
synced 2025-08-15 23:30:46 +00:00
Add latest changes from gitlab-org/gitlab@master
This commit is contained in:
@ -315,7 +315,7 @@ export, one is be generated by the babel plugin). The second parameter is the
|
||||
name of the import you wish to change. The result of the function is a Spy
|
||||
object which can be treated like any other Jasmine spy object.
|
||||
|
||||
Further documentation on the babel rewire pluign API can be found on
|
||||
Further documentation on the babel rewire plugin API can be found on
|
||||
[its repository Readme doc](https://github.com/speedskater/babel-plugin-rewire#babel-plugin-rewire).
|
||||
|
||||
#### Waiting in tests
|
||||
@ -532,7 +532,7 @@ In order to ensure that a clean wrapper object and DOM are being used in each te
|
||||
});
|
||||
```
|
||||
|
||||
See also the [Vue Test Utils documention on `destroy`](https://vue-test-utils.vuejs.org/api/wrapper/#destroy).
|
||||
See also the [Vue Test Utils documentation on `destroy`](https://vue-test-utils.vuejs.org/api/wrapper/#destroy).
|
||||
|
||||
#### Migrating flaky Karma tests to Jest
|
||||
|
||||
@ -649,7 +649,7 @@ it('uses some HTML element', () => {
|
||||
HTML and JSON fixtures are generated from backend views and controllers using RSpec (see `spec/frontend/fixtures/*.rb`).
|
||||
|
||||
For each fixture, the content of the `response` variable is stored in the output file.
|
||||
This variable gets automagically set if the test is marked as `type: :request` or `type: :controller`.
|
||||
This variable gets automatically set if the test is marked as `type: :request` or `type: :controller`.
|
||||
Fixtures are regenerated using the `bin/rake frontend:fixtures` command but you can also generate them individually,
|
||||
for example `bin/rspec spec/frontend/fixtures/merge_requests.rb`.
|
||||
When creating a new fixture, it often makes sense to take a look at the corresponding tests for the endpoint in `(ee/)spec/controllers/` or `(ee/)spec/requests/`.
|
||||
|
Reference in New Issue
Block a user