To run vets-api and its redis and postgres dependencies run the following command from within the repo you cloned in the above steps.
foreman start -m all=1,clamd=0,freshclam=0
You should then be able to navigate to http://localhost:3000/v0/status in your browser and start interacting with the API. Changes to the source in your local directory will be reflected automatically via a docker volume mount, just as they would be when running rails directly.
bundle exec rake spec
- Run the entire test suite ( forrspec spec
). Test coverage statistics are incoverage/index.html
.make guard
- Run the guard test server that reruns your tests after files are saved. Useful for TDD!
- NOTE: Running specs in parallel requires that your development database exists, and is up to date. If necessary, you may need to run
bundle exec rake db:create
andbundle exec rake db:migrate
before the following steps. RAILS_ENV=test bundle exec rake parallel:setup
- This prepares all of the test databases. It will create a test database for each processor on your computer.RAILS_ENV=test NOCOVERAGE=true bundle exec rake parallel:spec
- This runs the entire test suite. Optionally, a folder path can be given as a parameter. Each file is assigned a processor, so it probably doesn't make sense to pass an individual file to run it in parallel. It is currently suggested to forgo the coverage testing by addingNOCOVERAGE=true
flag (currently the coverage check will fail, even if the test suite passes). If you would like to check coverage for the test run, remove that flag.
rake lint
- Run the full suite of linters on the codebase and autocorrect.rake security
- Run the suite of security scanners on the codebase.rake ci
- Run all build steps performed in CI.
rails console
- runs an IRB like REPL in which all of the API's classes and environmental variables have been loaded.