As per discussion at team day, this splits our ui-components tests to follow the Vue.js conventions of:
Unit tests - a subset of a component - aware of the implementation details - uses mocking, stubbing, etc
Component tests - unaware of implementation details - does not touch private state - only interaction is via "user"
The component tests should be happy path coverage of the component, while the unit tests should be covering any edge cases. Long term, all the UI components should have their own component tests, but only some will need unit tests.
As per discussion at team day, this splits our ui-components tests to follow the Vue.js conventions of:
The component tests should be happy path coverage of the component, while the unit tests should be covering any edge cases. Long term, all the UI components should have their own component tests, but only some will need unit tests.