-
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
2 weeks ago
-
Refactor headless ghidra testing infrastructure:
```[tasklist]
### Tasks
- [ ] Refactor headless ghidra tests:
- [ ] Move `script/ghidra/test` to `test/ghidra`
- [ ] Instead of custom bash scri…
-
**As a Pillarbox developer** I would like to have a QoS / QoE test infrastructure to which I can send events collected by the platform player I am working on.
# Acceptance criteria
- Event dispatche…
-
## Detailed Description
Nice to have test that actually hit API and see what happens.
Good to keep these seperate from unit tests
-
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…
-
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…
-
It should be feasible to easily run VMs on the op-program (with valid inputs) without instantiating the op-challenger and dispute games.
-
Spring Data JDBC & R2DBC currently use different ways to implement integration tests.
JDBC
* creates an `ApplicationContext` and uses Spring profiles to create the right kind of database.
* SQL …
-
Currently, we are only performing continous integration tests for the full pipeline. We recognized that some code snippets should be tested to avoid errors.
Once example is the `split_cells()` func…