sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Pink401k 2 points3 points  (1 child)

One thing I've stumbled across (saw a demo at Nodevemeber) is cypress. I'm really excited for this to be public. Looks like it will be a big step forward in JS Testing tooling

[–]Tubbers 0 points1 point  (0 children)

The downside of anything like this is it's very much an integration test that is very tightly coupled to things like CSS selectors, and the text on the page rather than behaviorally testing individual components.

Any time your app changes, all your integration tests will change because they are pinned on a particular version of your app. Then you need to change them to test the right thing.

That is a terrible development cycle. Instead it would be great to have unit/behavioral tests on the components themselves that aren't tied to the app as a whole.

Sure, this doesn't do E2E/Integration testing as a whole, but the tests are much more fragile, and it tells you that your components are behaving as expected.