More specifically, with regards to ATDD (sort of BDD flavored, or some could argue what was actually intended in the first place by TDD) should be there much UI testing?
As I have been testing my UI components on my flavor of the month client-side MCV framework I find that I haven't really been testing much in the components themselves, only the modules they use.
For example, on a book website with
Books if I am testing the
Book listing page for an Author, instead of testing that the elements are rendered in the component properly (e.g. the
li elements for each book, the parent
ul, etc.) I would move the logic into a module for fetching those
Books for a specific
To take the example further, if there was some logic for interacting with one of the
Book elements rendered in the
ul then instead of checking that a handler was triggered I would just make sure that the handler is being tested properly.
It feels like if I test the UI rendering of the
Author and his/her
Books on the client side it's too tied to the implementation, and similarly with the event handler it marries me to the event handler so I can't refactor.
Is this the way to think about client-side testing the UI? Perhaps I just need some acceptance tests (e.g. Selenium) in this case to fill in the gaps?