Evaluation of our current QA Pipeline

[dkayiwa (Daniel Kayiwa)]

@jayasanka, this is a very useful evaluation!

@jayasanka

E2E tests provide more accurate feedback than unit and integration tests because they run in a full real-life environment rather than a mock environment.

FWIW, with openmrs-core 2.6.0, we have introduced Testcontainers such that one is able to run all existing tests on MySQL with: mvn test -DuseInMemoryDatabase=false -Ddatabase=mysql or on PostgreSQL with: mvn test -DuseInMemoryDatabase=false -Ddatabase=postgres

@jayasanka

Best practices, and our expectations around testing, are not clearly documented.

As part of the next steps, do you also plan to improve the documentation?

@jayasanka

What Gherkin syntax is really good for is if we have a less technical team to implement tests. You can have a team of developers create a library of steps and then have less technical users write the scenarios, which is not how we work. Everything we’re getting with Cucumber can be done with a good naming convention for tests and having tests properly organised into suites. Making sure that non-technical users can read a report of tests and understand what parts failed; is a crucial component of effective test design.

This is one of the best paragraphs that you have ever written for my consumption!!! Ever since we started using cucumber, i have never seen its practical benefit for our community. And i already emphasised this from the very beginning of our cucumber integration:

Up next for QA, do you think we need cucumber?

I read a blog of some developer who put it this way: I’ve done several projects that were using cucumber, yet never have I seen it used beneficially. The business people have never asked me about my step definitions in cucumber or anything like that. The only question that business people ask is: “Are you ready for production?”. Then another blog put it as below: Keep in mind, however, that in some cases the business side of the organization may not have input or opinions as to how the appli…

@jayasanka

One possible solution would be to have tests in each micro frontend repository itself. So that developers can easily update tests along with their PRs.

I like this. But in order to start simple, i would deal with it after all the others are done.