Commit aa3b4de
committed
tests: don't always test the mocks
The mock file is pretty big, and due to that has a lot of tests
The mocks should not need to be edited often, only when the dependency
they are mocking is updated. This is currently never, as it is unmaintained.
This means that we don't need to run the tests for the mocks all the time.
If an upgrade of our dependencies is taken, then the test file should be ran.
However, it does not need to run every time the test suite is ran.
This should lead to a faster total test suite when running the suite.1 parent 6f92e86 commit aa3b4de
1 file changed
+3
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
63 | 63 | | |
64 | 64 | | |
65 | 65 | | |
66 | | - | |
| 66 | + | |
67 | 67 | | |
68 | 68 | | |
69 | 69 | | |
70 | 70 | | |
71 | 71 | | |
72 | | - | |
| 72 | + | |
73 | 73 | | |
74 | 74 | | |
75 | 75 | | |
| |||
89 | 89 | | |
90 | 90 | | |
91 | 91 | | |
| 92 | + | |
0 commit comments