393ba00221
* Attempt number 1 * Fix rack_attack specs * Fix users_searches_users spec * Fix display_users_search_spec * Fix comment typo * Remove search:destroy task from cypress * Remove port 9300 from gitpod * Stub response in attack_spec
29 lines
763 B
Markdown
29 lines
763 B
Markdown
---
|
|
title: Test Flags
|
|
---
|
|
|
|
# Test Flags
|
|
|
|
When creating tests using Rspec we have the ability to add flags to those tests
|
|
that will signal to Rspec to run certain commands before, after, or around the
|
|
test example.
|
|
|
|
Some flags that we use are:
|
|
|
|
- `js: true`
|
|
- `throttle: true`
|
|
- `type: <test type>`
|
|
|
|
### `js: true` Flag
|
|
|
|
`js: true` indicates that we want the JavaScript on the page to be executed when
|
|
the page is rendered, and a headless chrome instance will be initialized to do
|
|
so (instead of the default
|
|
[rack_test](https://github.com/teamcapybara/capybara#racktest) driver).
|
|
|
|
If you are debugging a `js: true` spec and want to see the browser, you can set
|
|
`HEADLESS=false` before running a spec:
|
|
|
|
```shell
|
|
HEADLESS=false bundle exec rspec spec/app/system
|
|
```
|