[Epic]: Improve Quality Assurance

[eliobischof]

This Issue gives a view over all issues that should improve quality assurance.
It also includes issues from other repos.
The issues are ordered by priority.

• https://github.com/zitadel/website/issues/771
• https://github.com/zitadel/website/issues/772
• ZITADEL New Login UI: Standardize the way of writing and running acceptance tests. typescript#7
• ZITADEL New Login UI: Integration tests are complete typescript#8
• ZITADEL New Login UI: Acceptance tests are complete typescript#9
• ZITADEL API: Rename integration tests to acceptance tests #5831
• ZITADEL Actions: Standardize the way of writing and running unit and integration tests. #5840
• ZITADEL Actions: Standardize the way of writing and running acceptance tests. #5841
• ZITADEL Console: Standardize the way of writing and running unit and integration tests. #5854
• ZITADEL Schema: Standardize the way of writing and running unit and integration tests. schema#3
• Go Tests: Improve measuring of go test coverage #5858
• https://github.com/zitadel/website/issues/770
• ZITADEL API: Integration tests are complete #5833
• ZITADEL Actions: Integration tests are complete #5842
• ZITADEL Notifications: Integration tests are complete #5846
• ZITADEL Console: Integration tests are complete #5855
• ZITADEL Schema: Integration tests are complete schema#4
• https://github.com/zitadel/website/issues/773
• ZITADEL API: Acceptance tests are complete #5834
• ZITADEL Actions: Acceptance tests are complete #5843
• ZITADEL Notifications: Acceptance tests are complete #5847
• End-to-end tests: Standardize the way of writing and running end-to-end tests. #5857
• https://github.com/zitadel/website/issues/774
• ZITADEL Quotas and Log Stores: End-to-end tests are complete #5853
• ZITADEL New Login UI: End-to-end tests are complete typescript#10
• ZITADEL Notifications: End-to-end tests are complete #5848
• ZITADEL Actions Examples: List ready for review checks in PR template actions#17
• Terraform Provider: Generate schemas from protos terraform-provider-zitadel#93
• ZITADEL Login and Registration Server Side Golang UI: Standardize the way of writing and running unit and integration tests. #5835
• ZITADEL Login and Registration Server Side Golang UI: Standardize the way of writing and running acceptance tests. #5836
• ZITADEL Login and Registration Server Side Golang UI: Integration tests are complete #5837
• ZITADEL Login and Registration Server Side Golang UI: Acceptance tests are complete #5838
• ZITADEL Login and Registration Server Side Golang UI: End-to-end tests are complete #5839
• Coding Principles: Add DRY to all PR templates #5859
• Helm Charts: List ready for review checks in PR template zitadel-charts#85
• Terraform Provider: Run tests on PR terraform-provider-zitadel#92
• ZITADEL New Login UI: Standardize the way of writing and running unit and integration tests. typescript#6
• ZITADEL API: Standardize the way of writing and running acceptance tests. #5832
• ZITADEL Notifications: Standardize the way of writing and running unit and integration tests. #5844
• Terraform Provider: List ready for review checks in PR template terraform-provider-zitadel#90
• Terraform Provider: Roll out lifecycle tests to all resources terraform-provider-zitadel#91
• ZITADEL Notifications: Standardize the way of writing and running acceptance tests. #5845
• ZITADEL Quotas and Log Stores: Standardize the way of writing and running unit and integration tests. #5849
• ZITADEL Quotas and Log Stores: Standardize the way of writing and running acceptance tests. #5850
• ZITADEL Quotas and Log Stores: Integration tests are complete #5851
• ZITADEL Quotas and Log Stores: Acceptance tests are complete #5852

[hifabienne]

@eliobischof Which of these issues should we have a look next?
Are all still relevant or can we close some?
I would assume that we only have a look at the new apis for now, and leave the old ones out, at the momenet.

[eliobischof]

@hifabienne the ZITADEL API prefixed issues in this list don't differentiate between new and old API. Would you rather create separate issues? As they are not really different in their nature, I'd keep them together for consistency.

• I increased the priority of the portal tests, as the portal becomes more and more important.
• I decreased the priority for testing the old login UI. I wouldn't close them as long as the feature is not EOL.
• I Increased the priority of completing any unit/integration tests over any acceptance tests, as this enables us to increase the coverage faster