Of course, I know in the long run, that will lead to even more bugs but I don't have an effective workflow around that.
Of course, I know in the long run, that will lead to even more bugs but I don't have an effective workflow around that.
1) use a prefix (t-) for test selectors and do not attach any styles to them (put them on the elements you need to target directly so the tests do not have to know about the DOM structure)
2) use data- attributes for test selectors (again directly on the target elements so DOM changes won't break the tests)
The second I got from this article, which is a bit Ember specific, but makes a lot of good recommendations:
https://dockyard.com/blog/2015/09/25/ember-best-practices-ac...
Thanks for the suggestion on how to work with test classes anyway. Very useful.
[1]: https://github.com/BBC-News/wraith
[2]: https://percy.io/