# OpenElis Future with Junit 4

**URL:** <https://talk.openelis-global.org/t/openelis-future-with-junit-4/1689>\
**Category:** Development\
**Created:** [November 3, 2025, 2:40pm UTC](https://talk.openelis-global.org/t/openelis-future-with-junit-4/1689 "2025-11-03T14:40:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Agaba\_Derrick\_Junior](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/agaba_derrick_junior/32/503_2.png) [@Agaba\_Derrick\_Junior](https://talk.openelis-global.org/u/Agaba_Derrick_Junior)\
**Post date:** [November 3, 2025, 2:40pm UTC](https://talk.openelis-global.org/t/openelis-future-with-junit-4/1689/1 "2025-11-03T14:40:33Z")

</div>

JUnit 4 has reached the end of active development and is only receiving minimal maintenance updates. Since OpenELIS now uses **Java 21** and **Jakarta EE (`jakarta.*`)**, staying on JUnit 4 could limit compatibility with newer testing tools and libraries.

JUnit 5 offers modern features, active support, and full Jakarta compatibility — making it a natural step forward.

**Question:**  
Should we start thinking about gradual migration from JUnit 4 to JUnit 5 to align with current Java and Jakarta standards

---

<div class="post-metadata">

**Author:** ![Moses\_Mutesasira](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/moses_mutesasira/32/72_2.png) [@Moses\_Mutesasira](https://talk.openelis-global.org/u/Moses_Mutesasira)\
**Post date:** [November 3, 2025, 2:54pm UTC](https://talk.openelis-global.org/t/openelis-future-with-junit-4/1689/2 "2025-11-03T14:54:10Z")

</div>

Thanks @Agaba_Derrick_Junior for Starting up this thread.  
I agree with the idea.

> [@Agaba\_Derrick\_Junior](#):
>
> Should we start thinking about gradual migration from JUnit 4 to JUnit 5 to align with current Java and Jakarta standards

Yeah we can start trying out the [Migration](https://www.baeldung.com/junit-5-migration)

---

<div class="post-metadata">

**Author:** ![Vishal\_Sharma](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/vishal_sharma/32/739_2.png) [@Vishal\_Sharma](https://talk.openelis-global.org/u/Vishal_Sharma)\
**Post date:** [November 10, 2025, 4:54pm UTC](https://talk.openelis-global.org/t/openelis-future-with-junit-4/1689/3 "2025-11-10T16:54:03Z")

</div>

That’s a valid point @Agaba_Derrick_Junior thanks for bringing this up

---

<div class="post-metadata">

**Author:** ![Agaba\_Derrick\_Junior](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/agaba_derrick_junior/32/503_2.png) [@Agaba\_Derrick\_Junior](https://talk.openelis-global.org/u/Agaba_Derrick_Junior)\
**Post date:** [November 10, 2025, 7:17pm UTC](https://talk.openelis-global.org/t/openelis-future-with-junit-4/1689/4 "2025-11-10T19:17:55Z")

</div>

@Vishal_Sharma We have had some work done on this Migration i.e

> [Add a vintage engine that supports smooth transition by Agaba-derrick · Pull Request #2295 · DIGI-UW/OpenELIS-Global-2 · GitHub](https://github.com/DIGI-UW/OpenELIS-Global-2/pull/2295)

and

> <https://github.com/DIGI-UW/OpenELIS-Global-2/pull/2297>
>
> \# Pull Requests Requirements
> 
> \- \[\] The PR title includes a brief description …of the work done, including the
> Issue number if applicable.
> \- \[\] The PR includes a video showing the changes for the work done.
> \- \[\] The PR title follows conventional commit label standards.
> \- \[\] The changes confirm to the OpenElis Global x3
> \[Styleguide and Design\](https://uwdigi.atlassian.net/wiki/spaces/OG/pages/621346838/OpenELIS+Global+Style+Guide)
> documentation.
> \- \[\] The changes include tests or are validated by existing tests.
> \- \[\] I have read and agree to the Contributing
> \[Guidelines\](https://openelis-global.org/community/get-involved/) of this
> project.
> 
> \## Summary
> 
> Add a seperate Ci workflow for the junit5 coverege
> \## Screenshots
> 
> 
> 
> \## Related Issue
> 
> Closes \[#2296\](https://github.com/DIGI-UW/OpenELIS-Global-2/issues/2296)
> 
> \## Other

which is under review, once approved we can have some documentation on how to proceed with the the rest of the testing.