In this document, I would like to summarize my quality-related findings on domain-service teams. I have categorized my findings in several areas, such as frontend and backend quality and stability, and test coverage.

# PMD
At the moment there is no clear way to understand the pmd-backend since no proper API documentation is available, unlike the OpenAPI documentation that we have for our core platform services.

In the frontend application, I found some deviation from the designs provided by the DeepBlue, but I got the answer that the designs are merely suggestions and the details are up to the team and the PO to decide:

Also the new react components that they implement are not shared with the core via the read-component and the style guide documentation, adding an additional overhead for the core frontend team to reimplement them whenever there is a need.
When it comes to test coverage, pmd-backend as a good unit tests coverage, but there is no end-to-end test for neither the API nor the frontend application.

# DaaS

Deployment works, only production:
https://frontend.daas.olt-dev.io/
To run the application locally: the best would be to sit with someone and do it
Database is mocked: being used for the integration tests
**Unit test:** are being executed in the commit level.
**Integration/API test:** Supertests. All the needed endpoints are mocked. Execution: commit level
**UI tests:** there are a few tests written. Not added to the CI pipeline yet. The plan is to run them against the production: execution: Pull request level
**Deployment of the cypress tests:** issue with the limitation of the Qlik environments

Homework for Mo: How to test the graphs and diagrams: 1- jest snapshot 2- screenshot comparison
Meeting with @Bjorn about running tests locally

# Building Central
The deployment is done and ready
Good unit test coverage
Good e2e tests for the UI, but in an executable state and not in CI
No test coverage for the REST/GraphQL API endpoints