From 06dcb0776eb2160ecff4910b9459f31ca6368507 Mon Sep 17 00:00:00 2001 From: Bryce Johnson Date: Thu, 3 Nov 2016 09:57:30 +0000 Subject: Add tip for using Chrome to run and debug teaspoon tests. --- doc/development/frontend.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/development/frontend.md b/doc/development/frontend.md index ece8f880542..1d7d9127a64 100644 --- a/doc/development/frontend.md +++ b/doc/development/frontend.md @@ -196,6 +196,12 @@ It consists of two subtasks: As long as the fixtures don't change, `rake teaspoon:tests` is sufficient (and saves you some time). +If you need to debug your tests and/or application code while they're +running, navigate to [localhost:3000/teaspoon](http://localhost:3000/teaspoon) +in your browser, open DevTools, and run tests for individual files by clicking +on them. This is also much faster than setting up and running tests from the +command line. + Please note: Not all of the frontend fixtures are generated. Some are still static files. These will not be touched by `rake teaspoon:fixtures`. -- cgit v1.2.1