Problem
See #1748 as example.
12 tests failed:
(fail) harness list > prints the listed harnesses as JSON [10.84ms]
(fail) harness get > prints the harness detail as JSON for a given id [3.28ms]
(fail) harness endpoint list > prints the harness's endpoints as JSON for a given id [3.84ms]
(fail) harness endpoint get > prints the endpoint detail as JSON for a given id and qualifier [3.64ms]
(fail) harness version list > prints the harness's versions as JSON for a given id [3.59ms]
(fail) harness version get > prints the harness detail as JSON for a given id and version [3.54ms]
(fail) harness write flow > `harness create` provisions a default execution role and creates the harness [6.22ms]
(fail) harness write flow > `harness update` updates the prompt and creates version 2 [2.64ms]
(fail) harness write flow > `harness endpoint create` points a named endpoint at version 1 [3.16ms]
(fail) harness write flow > `harness endpoint update` repoints the endpoint at version 2 [10.36ms]
(fail) harness write flow > `harness endpoint delete` deletes the endpoint [2.01ms]
(fail) harness write flow > `harness delete` deletes the harness [1.73ms]
Note: the issue appears to be related to reading the expected data from the fs on windows machines, not functionality related.
Definition of Done
- unit tests pass on windows.
Problem
See #1748 as example.
Note: the issue appears to be related to reading the expected data from the fs on windows machines, not functionality related.
Definition of Done