-
At the moment, each test case consists of an assembly listing file and a "known good" machine code file. I think most of the machine code was either assembled by hand (suspect) or obtained online from…
-
## Issue
Low Coverage in some tests.
### Description
We are not checking all the fields that are being sent from our API and thus the test coverage is low for some tests. Please have a look into …
-
### Bug Report or Feature Request (mark with an `x`)
```
- [ ] bug report -> please search issues before submitting
- [x] feature request
```
### Area
```
- [x] devkit
- [ ] schematics
```
…
-
Test coverage needs to be at least 65%
![image](https://user-images.githubusercontent.com/35634011/163472106-e1cdf2d7-4704-40b0-a991-fde191777f41.png)
> Thresholds:
> 60-65% = 10pts
> 55-59.9…
-
https://docs.google.com/document/d/1yo5d-HsDEv6sSmYKvp1FIIHj5rTlN6iFwnQ0AT3RnlI/edit#
-
Especially for the public API.
-
-
I am building a Go provider for [Pruner][1] (a CLI that runs only the tests that ran through the lines you changed, saving you time).
For that, I need to be able to see per-test coverage. Not just …
-
Quoting @lukaseder [from Twitter](https://twitter.com/lukaseder/status/1334076327708778497):
> Is there a simple JUnit based tool to check for code coverage by a test class X for a given tested cla…
-
This is a catch all issue, feel free to split this up into separate issues.
Currently only tests are setup around, fuzzy matching.
Core areas that need tests:
* Image hashing (hash comparison, …