fabiobrz
commented
4 years ago At the moment, to easy up the process and reduce risk, the decision is to follow an iterative approach, starting with a very basic PR to introduce an application stub and minimal coverage for integration tests by merging what needed for https://github.com/jboss-eap-qe/eap-microprofile-test-suite/issues/11.
This was also discussed with the team and members reported that no common approach is required and each EAP MP spec test suite contributor can do what fits best. So this is meant to have lightweight process for quick iteration.
RATIONALE: first contribution to new TS with strict deadlines so risk ratio must be definitely very low. Tiny PR to introduce (almost) empty application for RHOAR QE TS migrated tests is a perfect candidate.
Evaluate architecture/implementation strategy for final solution with two potential approaches:
1 app, to serve as a back-end to simulate customer scenarios and to let the tests for all sections of TP to be run against
n mini apps to serve things as integration tests but 1 app for complex scenarios