-
Notifications
You must be signed in to change notification settings - Fork 1
chore: Seperate test processor logic into its own service #524
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
base: staging
Are you sure you want to change the base?
Conversation
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferencesCodacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more |
0354676
to
4d9adfa
Compare
🚨 OpenAPI Validation Failed 🚨 The OpenAPI specs in cd ./server
./gradlew :application-server:generateOpenApiDocs Commit and push the updated file. |
There hasn't been any activity on this pull request recently. Therefore, this pull request has been automatically marked as stale and will be closed if no further activity occurs within seven days. Thank you for your contributions. |
There hasn't been any activity on this pull request recently. Therefore, this pull request has been automatically marked as stale and will be closed if no further activity occurs within seven days. Thank you for your contributions. |
I'll put it back into "Ready for review" once the conflicts are resolved. |
There hasn't been any activity on this pull request recently. Therefore, this pull request has been automatically marked as stale and will be closed if no further activity occurs within seven days. Thank you for your contributions. |
Motivation
Right now the test processor is part of the application server code. However, with increasing complexity of the processor that could lead to some maintainability issues in the future.
Description
This PR seperates the downloading of test artifacts, extraction of zip files and parsing of test files into its own microservice called
test-processor
. I'm making use of our existing NATS service for communication. Additionally, the test processor provides the actual results with a REST API as the data is too large for sending it via nats.Testing Instructions
Displaying test results: Try to generate some test results (see test instructions of #341) on your branch/PR. You'll need to run the test processor as well (run
./gradlew :test-processor:bootRunDev
within server directory). Also make sure that your.env
file is moved to theserver
directory.Checklist
General