-
## Issue Overview
Unit tests required for the indicated hooks to ease future refactoring and feature validations.
## Proposed Solutions or Ideas (more like tips and reminders)
- We use vitest…
-
## Issue Overview
Unit tests required for the indicated hooks to ease future refactoring and feature validations.
## Proposed Solutions or Ideas (more like tips and reminders)
- We use vitest…
-
## Issue Overview
Unit tests required for the indicated hooks to ease future refactoring and feature validations.
## Proposed Solutions or Ideas (more like tips and reminders)
- We use vitest…
-
## Issue Overview
Unit tests required for the indicated hooks to ease future refactoring and feature validations.
## Proposed Solutions or Ideas (more like tips and reminders)
- We use vitest…
-
See #1008 . I'm thinking this would look like adding a `--coverage-exe` flag. Or, some other name, TBH one of the reasons this doesn't exist is that there's no concise name for this flag that obviou…
-
Our private assertion helpers stopped working after the 1.1.1 upgrade, because they didn't track the new shape of the cached body.
If they were part of the shared library and part of its test cover…
-
## Value Statement
**_As a_** VA team member
**_I want to_** ensure that all VA applications are not dependent on a deprecated library (momentjs)
**_So that_** we can use a maintained library (da…
-
We have pretty limited test coverage at the moment, only covering the pricing api.
Would love to expand test coverage to the IV calcs and greeks. Some of this is difficult as we have some little…
-
In preparation for upstreaming `HeuristicResolver` to the clang libraries as discussed at https://github.com/clangd/clangd/discussions/1662, I'd like to add a unit test suite exercising the interface …
-
We want all the projects to use the same test library, [scalaz-zio](https://github.com/scalaz/scalaz-zio/blob/d9a136469212f0ab14c0d6cab221386b28254e78/build.sbt#L39) uses specs2.
The plugin already…