-
We will need unittests done for all methods, classes and functions found in this file.
### PR Acceptance Criteria
1. When complete this file must show **100%** coverage when merged into the code…
-
We will need unittests done for all methods, classes and functions found in this file.
### PR Acceptance Criteria
1. When complete this file must show **100%** coverage when merged into the code…
-
We will need unittests done for all methods, classes and functions found in this file.
### PR Acceptance Criteria
1. When complete this file must show **100%** coverage when merged into the code…
-
We will need unittests done for all methods, classes and functions found in this file.
### PR Acceptance Criteria
1. When complete this file must show **100%** coverage when merged into the code…
-
**The problem**
We'd like to know which steps/scenarios are not implemented yet(There is only feature file without code execution)
rather than below error,
`Missing steps found. Use snippets belo…
-
Need to be able to automatically test new changes to ensure functionality isn't degrading as we move forward.
Set up tests and automatic test runs as part of CI
-
### New issue checklist
- [X] I searched for [existing GitHub issues](https://github.com/microsoft/azure-pipelines-tasks/issues)
- [X] I read [pipeline troubleshooting guide](https://docs.microsoft.c…
-
This tool already has `--exclude-from-report`, does it make sense to add black/white lists for toggling instrumentation on and off?
Like `--enable-coverage-for crate1 --enable-coverage-for crate2` or…
-
### What Happened
There appears to be some inconsistencies when using `--parallel`:
- the `--colors=never` option is being disregarded
- the `--coverage-text` is disregarded
- Note: without…
-
We have a nice test suite, we should have a coverage report. This should help: https://docs.cypress.io/guides/tooling/code-coverage
TODO:
- [ ] Setup coverage with cypress
- [ ] have a coverage …