You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some basic guidelines for what types of tests to write when working in this space
Proposed strategies
Common Components / Layouts
Should have component specific testing within common-components/layout project
vitests where any setup (not including api requests) needs to be mocked
ELSE/AND cypress tests over example.vue (common) or default.vue (Layout) -- this should not duplicate tests needed in btr-main-app)
Should have tests inside btr-main-app to secure it is showing / the expected variation is present
basic vitest added at the page / component level that the common component is added into (not necessary if the cypress test written already secures this)
cypress test securing page(s) that the component is present on
Main App
cypress tests preferred
vitests where mocking needed goes outside of intercepting api requests
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Description
Some basic guidelines for what types of tests to write when working in this space
Proposed strategies
Beta Was this translation helpful? Give feedback.
All reactions