[
https://issues.apache.org/jira/browse/FINERACT-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17102979#comment-17102979
]
James Dailey commented on FINERACT-949:
---------------------------------------
I'm not going to be much use on this, but just reading the
([https://github.com/skyscreamer/JSONassert] suggests it has a good approach
and makes tests less brittle, which seams to be a main issue for fineract.
Down the paths you outlined, I also found
[https://springframework.guru/processing-json-jackson/] (and the debate of
Jackson vs GSON). It seems that the criteria for this effort is: less
brittle, more readable, easy to write. I hope someone with some experience in
this can chime in.
> 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)
