[jira] [Commented] (FINERACT-764) Run Integration Tests using Spring Boot IT support instead of on Tomcat started separately by gradle-tomcat-plugin

["Michael Vorburger (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FINERACT-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17098103#comment-17098103 ] 

Michael Vorburger commented on FINERACT-764:
--------------------------------------------

Motivated by [~ptuomola] interest in progressing FINERACT-730, I re-read my own old comment from above again today, just to better understand what really needs to be done here next. – As far as I can tell, that {{SpringBootLoginTest}} mentioned here is (only..) on my [https://github.com/apache/fineract/compare/develop...vorburger:FINERACT-764_spring-boot-run-integrationtest-rm-tomcat-gradle] .. I'll try to _rebase_ that (very old) branch and see how it looks like today.

> Run Integration Tests using Spring Boot IT support instead of on Tomcat started separately by gradle-tomcat-plugin
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: FINERACT-764
>                 URL: https://issues.apache.org/jira/browse/FINERACT-764
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Michael Vorburger
>            Priority: Major
>
> https://github.com/apache/fineract/pull/525 for FINERACT-700 struggles to get "./gradlew integrationTest" working under an up-to-date Gradle version, due to the gradle-tomcat-plugin failing to start Tomcat. The problem can also be seen (on that PR, as it stands right now) via {{./gradlew tomcatrunwar}}.
> https://github.com/bmuschko/gradle-tomcat-plugin mentions that its author "I don't have much time to contribute anymore. In practice this means far less activity, responsiveness on issues and new releases from my end."
> What we IMHO really should do instead is to ditch our use of gradle-tomcat-plugin and just use Spring Boot's very nice built-in support for Integration Test, see here:
> * https://docs.spring.io/spring-boot/docs/2.1.5.RELEASE/reference/htmlsingle/#boot-features-testing-spring-applications
> * https://www.baeldung.com/spring-boot-testing (see 7. Integration Testing with @SpringBootTest)
> * https://reflectoring.io/spring-boot-test/
> I wouldn't have time for this, but perhaps someone would like to pick this up?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)