You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to use the TestTrack Chrome extension, you will need to set up the `BROWSER_EXTENSION_SHARED_SECRET` environment variable. [Details.](https://github.com/Betterment/test_track_chrome_extension#building-the-extension)
69
69
70
+
#### Running specs
71
+
72
+
To run all specs:
73
+
```bash
74
+
bundle exec rspec
75
+
```
76
+
77
+
If you are interested in hitting a `binding.pry` somewhere while playing around with your development environment, you can use `binding.pry_remote` in your code. When reloading the page you expect to have the breakpoint, the browser should freeze and you should be able to connect to your console via running in your terminal `pry-remote`. Pry away as normal!
78
+
79
+
If you are curious to see your integration tests running in a non-headless manner, run your test this way:
80
+
81
+
```
82
+
$ CAPYBARA_DEBUG=1 bundle exec rspec <path to file>/<file>s
83
+
```
84
+
70
85
## Managing your installation
71
86
There are a few things that you will need to do in the TestTrack application:
72
87
* Create `App`s -- client applications that will manage splits on your TestTrack server
0 commit comments