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
As part of the effort to improve our unit tests, we've decided to move unit tests to the same directory as the source file of the system under testing.
Primarily, this provides the benefit of making it easier to find the associated test file for each component and to identify which source files is missing associated tests.
Note that naming of the unit tests should:
start with the same file name as the source file, until the file extension
One open question is where should the test utilities (e.g. mocks, helpers) be located? If it is placed in the same directory as the source and unit test files, it becomes a little more difficult to differentiate between source files and test utilities. We need to test this out to ensure the coverage tool recognizes test utilities correctly.
Update: we decided to keep test utilities in the top level test directory.
As part of the effort to improve our unit tests, we've decided to move unit tests to the same directory as the source file of the system under testing.
For example:
Primarily, this provides the benefit of making it easier to find the associated test file for each component and to identify which source files is missing associated tests.
Note that naming of the unit tests should:
.unit.spec.js
as specified here.We'll likely do this in smaller steps, note that some of these tests will have been removed as part of the remove obsolete components work.
Definition of Done
The text was updated successfully, but these errors were encountered: