Story #15334
closed[Workbench2] Unit testing
0%
Description
Review https://dev.arvados.org/projects/arvados/wiki/Hacking_Workbench2 to get a better understanding of how WB2 is structured.
Reducers
Reducers are responsible for transitioning between states. These are straight forward to test. Start with an initial state, call the reducer with an action, and evaluate the resulting state.
Action creators and services
These are the components that invoke actions to change state and interact with outside resources (Axios, localstorage, etc). Need more research to figure out how to test these properly. Do we use the actual store, or mock it? Do we have to mock the entire service repository?
React UI Components
React components only rely on their connected props/state, which make them relatively easy to test using something like Enzyme. Consider snapshot testing for components that don't change often.
Resources: https://redux.js.org/recipes/writing-tests, https://willowtreeapps.com/ideas/best-practices-for-unit-testing-with-a-react-redux-approach
Updated by Eric Biagiotti over 5 years ago
- Related to Story #15333: Workbench2 feature parity with Workbench added
Updated by Eric Biagiotti over 5 years ago
- Subject changed from Workbench 2 unit testing to [Workbench2] Unit testing
Updated by Tom Morris over 5 years ago
- Target version changed from To Be Groomed to Arvados Future Sprints
- Story points set to 2.0
Updated by Tom Morris over 5 years ago
- Blocks Story #15581: [Workbench2] Improve error handling and reporting added
Updated by Peter Amstutz almost 5 years ago
- Target version deleted (
Arvados Future Sprints) - Release set to 20