authorjapps
Question. Release candence of ZeroCode updating the currency of internal dependencies.
Hi, I work for Watson Health in IBM and we are reviewing ZeroCode for our requirements.
I have a question to your release cadence and your plans to keep the version of third party open source jars current. With critical issues often appearing in the third party supply chain, keeping current is important from a security stance and to allow ZeroCode to continue to work with other software, e.g. Spring Boot.
Do you plan to release new versions of ZeroCode moving to the most current version of dependent jars? If a request is made through this channel to update dependencies to the current version can you give an example of the timeline.
The status of the last releases here are not up-to-date https://github.com/authorjapps/zerocode/wiki/Zerocode-release-frequency-and-schedule
https://mvnrepository.com/artifact/org.jsmart/zerocode-tdd - 1 release in 2021.
Example of an issue I hit. I tried to get ZeroCode to work with the latest Spring Boot version, version 2.6.3 . There is a clashing jar file version, the higher version of the jackson library 2.13.1 in Spring Boot 2.6.3 is not compatible with ZeroCode, you get an exception saying 'Step cannot be created.'. I can continue as I have removed Spring Boot from my spike of ZeroCode.
Example of dependencies for ZeroCode.
- jackson-dataformat-yaml-2.9.8.jar - Dec, 2018
- jackson-databind-2.10.0.jar - Sep, 2019
Hi. We do plan to update dependencies. Im not sure about the release date though. You can always exclude whatever dependency is "problematic". Btw, please join our Slack if you need to discuss some other related issue to your project.
One related question on full Junit 5 integration.
Do you have plans to support Junit 5 for all test scenario types, just load testing is supported at present if I understand your docs correctly.
Hi @anthonyfarrelloylegate , JUnit5 is on the plan, it's a different engine and needs bit of time to implement it. This won't be immediately available as noone is working on it currently, as well as it will take much time to get it done quicker!
I'm curious to know and get some ideas about your usecases which could be blocking due to JUnit4 and JUnit5 can solve it. Happy to collaborate if you(and any other collaborators) are interested to contribute here for JUnit5, I will put some tickets for initial brainstorming... if that helps!
...just load testing is supported at present if I understand your docs correctly.
Yes, you are right. we implemented it quite long ago upon someone's request due to a blocking usecase in their project. As well as it made load testing more flexible due to JUnit5's engine architecture/design.
