baarkerlounger
/
submit-social-housing-lettings-and-sales-data
mirror of https://github.com/communitiesuk/submit-social-housing-lettings-and-sales-data.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Submit social housing lettings and sales data (CORE)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2826 Commits
233 Branches
250 Tags
74 MiB
 
 
 
 
Tree: d1298ff10d
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'd1298ff10d'
${ noResults }
submit-social-housing-letti.../docs/testing.md

1.4 KiB
Raw Blame History

nav_order
4

Testing

  • We use RSpec and Capybara

  • Capybara is used for our feature tests. These use the Rack driver by default (faster) or the Gecko driver (installation required) when the js: true option is passed for a test.

  • Capybara is configured to run in headless mode but this can be toggled by commenting out app/spec/rails_helper.rb#L14

  • Capybara is configured to use Gecko driver for JavaScript tests as Chrome is more commonly used and so naturally more likely to be better tested but this can be switched to Chrome driver by changing app/spec/rails_helper.rb#L13

  • Feature specs are generally written sparingly as they’re also the slowest, where possible a request spec is preferred as this still tests a large surface area (route, controller, model, view) without the performance impact. They are not suitable for tests that need to run JavaScript or test that a specific set of interaction events that trigger a specific set of requests (with high confidence).

  • Test data is created with FactoryBot where ever possible

Parallel testing

  • The RSpec test suite can be ran in parallel in local development for quicker turnaround times

  • Setup with the following:

bundle exec rake parallel:setup
  • Run with:
RAILS_ENV=test bundle exec rake parallel:spec