-
While we do have tests to verify that the generate code looks as expected and compiles without errors, we don't have tests to verify that the code we generate runs as expected. We achieve that using m…
-
jofme updated
1 month ago
-
Similar to [this](https://github.com/open-telemetry/opentelemetry-python-contrib/issues/2444).
-
Add performance tracking for nanoGPT (regression testing in L1). Need to add infra for tracking a) build time b) performance across time and share this infra for all performance tests/samples.
-
I see several issues with our infrastructure:
1. Lint is very slow. This mostly happens because we install every single package to create a virtual environment for linting.
2. We are using `tox.in…
-
conjure-oxide needs an exhaustive testing infrastructure. This is mainly for correctness and performance testing in comparison to conjure. Tests should be run through Github actions, can make use of h…
-
We have, so far, written a minimal amount of tests in order to focus on rapid prototyping without major concern for breakage, in the absence of actual users. As the scope of the project grows, the per…
-
Currently our testing only accounts for regressions against an existing saved svg. This is very primitive and subject to churn when we change the svg output e.g. to add transforms as in #40. We could …
-
I suggest using [`testthat`](https://testthat.r-lib.org/) to refresh the testing infrastructure. This can replace the original test infrastructure in the `tests` folder.
Advantages:
- easier to ma…
-
The current testing infrastructure is lacking. We have many similar functions: `dotenv`, `from_filename`, `from_path`, `from_read` and their `override` and `iter` variants; but only the `dotenv` funct…