super() would call Object() instead of ValidationMessage(). This way, debugging can track instantiations of ValidationMessage from one place
Co-authored-by: dotasek <david.otasek@smilecdr.com>
* WIP add initial test running code
* Importing test modules fix breaking tests 1
* Clean up pom dependencies, move execution before context load
* Re-org and document cli pom
* Set more dependencies to compile. Print entries in classpath
* Try running via internal Executors
* Clearer class names + provide clear output
* Clean up test summarys and output + update class regex to junit default
* Refactor to avoid having to extend class
* Trim down dependency additions in pom + javadoc
* Add the rest of the modules to TestExecutor
* Parse additional params for classname filter and module
* Add experimental JUnit 4 runner in case JUnit 5 hates us.
* Include JUnit4 tests via adapters. Need to refactor for better naming.
* Update LoadIgTests to JUnit 5
* Gentle refactor, print execution time
* Remove unnecessary interface, organize packages
* Remove cached resources (need to fix this)
* Allow setting of txCache globally for tests + fix r5 tests
* Mild refactor of TestExecutor + Reorder test execution
* Add fhirTestCasesDirectory to testConfig + get r4 tests working
* Add dstu2016may and dstu3 tests
* Add dstu2 tests
* Add convertors tests
* Refactor resourceNameForFile + don't copy existing files
* Get all txCache directories centrally and allow all to live in same dir
* Start extracting txCache resources
* Finish extracting txCache resources
* Fix failing GraphQLEngineTest
* Try an mvn install for the pull pipeline
* Clean and refactor
* Test coverage
* Fix GraphQLEngineTests for local jar run
* More refactoring, more tests
* Add bare test for TxCacheResourceExtractor
Co-authored-by: dotasek <david.otasek@smilecdr.com>
