[
https://issues.apache.org/jira/browse/FINERACT-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046382#comment-18046382
]
Adam Monsen commented on FINERACT-2329:
---------------------------------------
For running Fineract locally in dev/test, yes, {{devRun}} is great!
All the different ways/filters for testing do seem to work, it's just hard to
keep track of all the options. My intent was to give ourselves some reasonable,
simple default test run. For example, to quickly run a subset of checks/tests:
{code:java}
./gradlew test{code}
But perhaps this isn't realistic, since what I want to test depends on what I
am doing (quick check after saving a file, check as much as I can before
pushing code or releasing, integration tests only, e2e tests, oauth, twofactor,
all of the above, etc)...
Really I was bemoning the
[current|https://github.com/apache/fineract/blob/develop/CONTRIBUTING.md#unit-tests]
default "unit test" incantation of
{code:java}
./gradlew test -x :twofactor-tests:test -x :oauth2-tests:test -x
:integration-tests:test{code}
and that it's hard to know exactly what to do locally and when.
Also see the description in FINERACT-2328. I'm concerned about reliance on
github and reproducibility in general.
I'm fine resolving this for now because I'm not hearing much desire to change
the build in the way I originally imagined. Maybe it's just a matter of
improving documentation.
> simplify local build+test on dev computers
> ------------------------------------------
>
> Key: FINERACT-2329
> URL: https://issues.apache.org/jira/browse/FINERACT-2329
> Project: Apache Fineract
> Issue Type: Task
> Reporter: Adam Monsen
> Priority: Minor
>
> Make it easier for devs to run tests locally.
> Remove the need for any/all "-x :slow-stuff" or "-x :broken-stuff" exclusions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
