You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Michael Vorburger (Jira)" <ji...@apache.org> on 2020/05/08 17:42:00 UTC
[jira] [Updated] (FINERACT-949) Improve Java API style used for
writing integration tests in Fineract
[ https://issues.apache.org/jira/browse/FINERACT-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Vorburger updated FINERACT-949:
---------------------------------------
Summary: Improve Java API style used for writing integration tests in Fineract (was: Improve Java API style used for writting integration tests in Fineract)
> Improve Java API style used for writing integration tests in Fineract
> ---------------------------------------------------------------------
>
> Key: FINERACT-949
> URL: https://issues.apache.org/jira/browse/FINERACT-949
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Michael Vorburger
> Priority: Major
> Labels: integration-test, technical, testing
>
> The current (Java) "style" that integration tests are written in in Fineract is... really ugly!
> They are from a bygone era when Java had no generic. All those weird {{java.util.HashSet}}, with a lot of {{java.lang.Object}} etc. in tests are... so not 21st century style.
> I don't really have the answer here, yet - but perhaps others have ideas - how does one write Java (test) code in 2020 which deals with JSON in a nicer way?
> Does REST Assured (http://rest-assured.io) meanwhile offer a better way to do this kind of thing?
> Could https://github.com/skyscreamer/JSONassert be of use and interest for this purpose?
> BTW if using REST Assured better than we are is part of the answer here, then let's first do FINERACT-884.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)