Hey Let me share how I do it (console is mostly just simple copy from how github workflow is doing):
We need a running instance of Fineract for both of them! Integration tests - IntelliJ: To execute every integration tests Right click on src/test/java directory in integration-tests module and select Run Tests in java option Alternatively: Go to Run > Edit Configurations. Click the + button and select JUnit. In the configuration settings: Set the JDK: Java 17 (example) Choose the fineract.integration-tests.test module VM options: -ea Select All in package as type of search Working directory: $MODULE_WORKING_DIR$ For more details and configuration: https://fineract-academy.com/how-to-run-fineract-integration-test-with-intellij-idea.html <https://fineract-academy.com/how-to-run-fineract-integration-test-with-intellij-idea.html> - Console: ./gradlew -PcargoDisabled=true --no-daemon --console=plain :integration-tests:test E2E - IntelliJ: To execute every E2E tests Above configuration but Feature or folder path: <fully qualified path to fineract directory>/fineract-e2e-tests-runner/src/test/resources/features/ Alternatively: Go to Run > Edit Configurations. Click the + button and select Gradle. In the configuration settings: Run: cucumber Gradle project: <fully qualified path to fineract directory>/fineract-e2e-tests-runner For more details and configuration: https://fineract-academy.com/how-to-run-fineract-e2e-test-with-intellij-idea.html - Console: ./gradlew --no-daemon --console=plain fineract-e2e-tests-runner:cucumber --tags 'not @Skip’ Regards, Adam > On 21 Dec 2024, at 22:56, James Dailey <jdai...@apache.org> wrote: > > Devs > > Adam brought up a topic (off thread) so highlighting it here. > > TL;DR : don’t we need e2e tests to run locally that are not brittle? > Especially for release “smoke test” > > ( long-term / separate threads follow... ) > > I found it challenging to get integration/e2e tests running locally. I can > now run one at a time in IntelliJ but the setup is complex and brittle. > Running tests on a dev machine from the command line is somewhere I can offer > some useful contributions, if/as desired. I'd like to first understand if > it's my inexperience with this project or if there are fundamental issues > with how the tests are set up. > > It would be useful to have an agreed-upon pre-release smoke test for these > release votes. Surely GitHub actions/workflow are/will be useful for this, > but personally I always hope to be able to locally run the same things that > run in the cloud. Services like GitHub are handy but they can become just > another capricious dependency. > > > >
