Move nightwatch tests into the same directory as the code they test

Bug #2036831 reported by Jane Sandberg
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Wishlist
Unassigned

Bug Description

Discussed in today's new dev working group.

Nightwatch tests are great, but they are in a different directory from the code that they describe. This has a few drawbacks:
* adds to the maintenance burden (if you change a selector in a template, you'd need to remember to change it in the nightwatch test too, for example)
* it's harder to know if a nightwatch test exists for the screen you're currently working with

We should:
* redistribute the nightwatch tests into the eg2/src directory, each with its own extension (for example .nightwatch.ts or .e2e.ts)
* update nightwatch.conf.js to use "src" as the "src_folder" and something matching the new extension as the "filter".

Tags: angular
Revision history for this message
Terran McCanna (tmccanna) wrote :

+1 to moving them into the same directory as the code they are testing.

+1 to the idea of using .nightwatch.ts to make them particularly easy to spot.

Changed in evergreen:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Stephanie Leary (stephanieleary) wrote :

+1 to both! I like using .nightwatch.ts (or maybe .nw.ts?) to make it easy to decommission these files if we end up having to change syntax again when Nightwatch is inevitably replaced by the next great thing.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.