Feature: Document junit/testng mode switching in a blog post
MohabMohie opened this issue · comments
<@U047WGNEGQJ> the new alpha will detect and self-configure to run in testng or junit mode.
This requires some changes to the pom.xml as the configuration depends on automatically triggered maven profiles, and automatically generated service loader files.
Please check out the changes made to this pom.xml and upgrade yours accordingly
https://github.com/MohabMohie/using_SHAFT_Engine/blob/alpha_engine_upgrade/GUI_Web/pom.xml|https://github.com/MohabMohie/using_SHAFT_Engine/blob/alpha_engine_upgrade/GUI_Web/pom.xml
The engine is in alpha mode now because I want to make sure that introducing the junit integration is not breaking anything... Also I'm improving the overall user experience and trying to find a way that doesn't require existing users to change their pom.xml files....
I would really appreciate that you help me test this alpha version with junit.
Just upgrade your pom.xml, make sure to map to the one I linked, and just run any junit test class. The engine should pick that up automatically and tell you that it detected a junit run, it's self-healing, and it's triggering a minimalistic first run.
It won't be able to generate the reports on that first run, but it'll output everything to the console.
On your second+ runs the engine will have full functionality and will open the summary report automatically.
Also you can perform your second+ runs from CLI and the engine will work as expected.