Software testing is an investigation conducted to provide stakeholders with information about the quality of the software product or service under test.
Hello everyone,
I am André from MedVertical. We are exploring InterSystems-native ways to operationalize continuous FHIR conformance: repeatable regression runs, baseline/delta comparisons, and evidence-style reporting to detect drift after releases and IG changes.
In many FHIR implementations, validation is done “point-in-time” in pre-prod, but conformance degrades in production due to IG/profile updates, terminology changes, mapping evolution, upstream releases, and configuration drift.
Hi Developers!
Recently we discussed the naming convention on packages we deploy and even made some choices.
Here I want to have a conversation on the naming convention for unit tests.
Of course, we wish every good library has unit tests. Here is the documentation and some good articles(one, two, three) regarding it on the Developer Community.
Let's decide on the naming of UnitTests packages?
The suggestion is that unit test classes will all start with the UnitTest package name.
E.g. if your library's class name is:
johndoe.lib.class
The related unit test class will be:
UnitTest.johndoe.lib.class
What about folders?
The suggestion is that unit test classes will live separately from source classes, e.g. in /tests directory.
Here is the example of a repository with unit tests that are named and placed according to the proposal.
What do you think?