Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Ruby Build a Todo List Application with Rails 4 Build a Todo List Application with Rails 4 Creating Methods in Tests

How does this test actually run?

I can read the test and understand how each section works but when I run the test from the command line what is actually happening?

I am seeing UI style tests but it's passing or failing in a short amount of time so that no browser UI tests appear to be being run. Basically I am unsure how these type of tests are being run without spinning up an actual browser or headless browser.

Thanks,

1 Answer

Maciej Czuchnowski
Maciej Czuchnowski
36,441 Points

The documentation describes this feature:

Switch the backend: your tests run against from fast headless mode to an actual browser with no changes to your tests.

So I assume that by default it's headless mode. You can even install another capybara gem that returns screenshots of situations where a test did not pass to show you how the browser looked like at that point.

Maciej Czuchnowski Perfect, thanks for looking into this. That definitely makes a lot more sense now as I had forgotten that we were working with Capybara as well :)