[JShellAPI][Testing] Setting up First Integration Test - Simple code snippet evaluation scenario

[firasrg]

Pull-request

• [ ] I have read the contributing guidelines.
• [x] I have read the code guidelines.
• [ ] I have created a relating issue.

Changes

• [x] Some changes in gradle files to
• [x] New integration test

Description

This PR is about setting up a first working integration test for JShellAPI only, it contains the following :

• New global property in root project'd gradle.build file to share JShellWrapper's image name across subprojects gradle.build files and Java files as well.
• [JShellAPI] New custom tasks in gradle.build file for docker image : build + remove;
• [JShellAPI] New Integration tests class with a 1st working test on WS POST/jshel/eval .

Note: this PR is about setting the roadmap for testing strategy for JShellAPI only. It doesn't close the relevant issue.

[Alathreon]

I don't have time to do a review, so I'll just write here. There are two problems :

• Your test is too complicated to test something too simple, you need to simplify it, create methods or classes for this so your test can be as simple as for example assertEquals(sendEval("2+2"), new JShellResult(...))
• Also include a test to test state. For example, you can send an eval "var list = List.of(1, 2, 3)" and then send a separate eval like "println(list)"

[firasrg]

Hello @Alathreon !

Your test is too complicated to test something too simple

I think that my test code is pretty simple, it uses WebTestClient API to establish test in a smooth way (ig it's a good practice as mentioned in spring docs) :

create methods or classes for this so your test can be as simple as for example assertEquals(sendEval("2+2"), new JShellResult(...))

I'm not certain i understand this sorry, can u elaborate ?