[FINERACT-1209] Integration Tests using new Swagger Client API ("Fineract SDK")

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Component/s: SDK
• Assignee: Aleksandar Vidakovic
• Reporter: Michael Vorburger
• Created: 17/Oct/20 17:21
• Updated: 25/Feb/21 11:09
• Resolved: 13/Nov/20 00:19

Description

Thanks to the progress in FINERACT-1189, I think we're closer than we have ever been to do something I have dreamt of for a long time... basically what we were discussing back in the comments of FINERACT-838, copy/paste:

(...) include sample code in the repo building against the generated client libraries to test and illustrate their usage. (...) it's still not really "tested" at all, of course. We don't know if the generated code is a working client. (...) In an ideal world, we should have some sort of fineract-client-demo as a small separate project in the git root directory (of Apache Fineract core, not separately/outside!) which depends on fineract-client, and invokes at least some of the generated APIs. This IMHO should always be run, e.g. on Travis CI. We would of course need a "back-end server" - the easiest would probably be to run this against the local server we're anyway starting for integrationTest, in a separate new Gradle task with the appropriate dependencies?

Thinking about this again with 2 months distance since writing above, what we probably REALLY should do, I don't know if instead of or in addition to a separate small new fineract-client-demo, is have (all?) of our ITs (in integrationTest) use the Swagger Client, instead of all those weird hand hard-coded *Utils and *Helper classes with RestAssured - that would be so much nicer!

Aleksandar Vidakovic [~ChinmayKulkarni] Petri Tuomola Manthan Surkar

Issue Links

• Blocked: FINERACT-1305 Release Apache Fineract v1.5.0
• blocks: FINERACT-1247 ImageTest failures
• blocks: FINERACT-1218 Missing Integration Test coverage for Document Management functionality
• contains: FINERACT-1255 Staff Swagger declaration is wrong
• is blocked by: FINERACT-1221 Fineract Client Java SDK API has broken methods
• is blocked by: FINERACT-1222 SDK Swagger Client Java API DefaultApi should disappear and operations go to other Api interfaces
• is blocked by: FINERACT-1214 SDK Swagger Client Java API methods returning Rx Observable are not intuitive for Java developers
• is blocked by: FINERACT-1220 Client Java SDK must configure GSON to deserialize [yyyy,mm,dd] date format returned by Fineract API
• is blocked by: FINERACT-1230 SDK Swagger Client Java API mixes Long and Integer for IDs
• is blocked by: FINERACT-1212 SDK Swagger Client Java API method names are ugly
• is blocked by: FINERACT-1213 SDK Swagger Client Java API methods have (too) many parameters
• is blocked by: FINERACT-1216 docs/developers/swagger/client.md should explain how to authenticate and pass tenant to Fineract
• is blocked by: FINERACT-1219 Fineract Client Java SDK API must support "insecure" mode (optionally)
• is related to: FINERACT-1246 New :integration-tests module should have Checkstyle enabled
• relates to: FINERACT-733 Swagger Documentation for Fineract API's
• links to: GitHub Pull Request #1465
• links to: GitHub Pull Request #1490
• links to: GitHub Pull Request #1491
• links to: GitHub Pull Request #1494