Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix coverage with new decoupled backend #483

Open
1 of 4 tasks
vkotronis opened this issue Dec 11, 2020 · 1 comment
Open
1 of 4 tasks

Fix coverage with new decoupled backend #483

vkotronis opened this issue Dec 11, 2020 · 1 comment

Comments

@vkotronis
Copy link
Member

Describe the bug
current convert_coverage.sh script:

#!/bin/sh
docker cp backend:/root/core/.coverage .coverage
sed -i "s;/root/core/;${PWD}/backend/core/;g" .coverage
coverage xml --rcfile testing/.coveragerc

We need to account for the new modules, which are under
backend-services

Structure is as follows:

backend-services/
├── service
│   ├── AUTHORS.md
│   ├── core
│   │   ├── service.py
│   │   └── __init__.py
│   ├── Dockerfile
│   ├── entrypoint
│   ├── LICENSE
│   ├── Makefile
│   ├── requirements.txt
│   └── wait-for
..........

where service = [autoignore, autostarter, configuration, database, detection, fileobserver, mitigation, notifier, prefixtree]

Affected Component(s)

  • Back-End (Database, Microservices, Containers, etc)
  • Front-End (Flask, API, etc)
  • Docs
  • Build System

Expected behavior
Backend services need to be properly covered.

@vkotronis vkotronis added this to the release-2.0.0 milestone Dec 11, 2020
@vkotronis vkotronis added the p/medium Medium priority label Dec 18, 2020
@vkotronis
Copy link
Member Author

@slowr should I move this to another release?

@vkotronis vkotronis removed this from the release-2.1.0 milestone Apr 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant