Lines Matching full:testing

1 # Unit Testing
9 > writing too many. I call this the unit testing Goldilocks rule—not too many,
13 > -- Ed Yerburgh, Testing Vue Applications (New York: Manning
68 - Avoid coupling test code to source code when testing functionality
75 - There is no return on investment for testing presentational HTML
79   when testing a plugin like Vuex
98 1. Static components do not need unit tests, use snapshot testing
103 1. Create smaller functions with a specific purpose to make testing easier
107    visual testing
109 ### Snapshot Testing
116 This type of testing is good for testing that static content output has not
123 There are two testing strategies for testing a Vuex store, which include testing
124 store parts separately or testing a running store instance. Each strategy has
129 ### Testing Store Parts Separately
131 Testing the parts separately is easy since each of the parts is a JavaScript
142 functions that may not require testing unless there is getter logic. Any logic
148 functions that may not require testing unless there is mutation logic. Any logic
158 - Requires extreme mocking when testing actions
162 ### Testing Store Instance
179 - Our current structure does not warrant testing the vue router
182 - When testing a vue router, it is important to use localVue
184 [Vuex Testing](https://vuex.vuejs.org/guide/testing.html)
189 - [Knowing What To Test — Vue Component Unit Testing](https://vuejsdevelopers.com/2019/08/26/vue-wh…