Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On JPMS Modules and Strong Encapsulation in JUnit #3355

Closed
jgarci40 opened this issue Jun 14, 2023 · 0 comments
Closed

On JPMS Modules and Strong Encapsulation in JUnit #3355

jgarci40 opened this issue Jun 14, 2023 · 0 comments

Comments

@jgarci40
Copy link

Hi JUnit5 team. I know this is an unusual place to ask this question, but it seems to be about as good as any other place I can find. My name is Joshua (Josh) Garcia (https://jgarcia.ics.uci.edu/), and I am an assistant professor in software engineering at the University of California, Irvine. My students and I have spent a significant amount of time studying JUnit5 lately and JEPs related to Java strong encapsulation, JPMS modules, FFMI, and Java integrity by default. Our research goal is to study the design, decay, and repair/prevention of software decay in JPMS modules. As a result, we've been producing preliminary results, and coming up with ideas regarding our research goal based on JUnit, especially JUnit5. To help JUnit and the Java community with the aforementioned Java platform issues, we're looking to see if anyone on the JUnit5 team may be willing to discuss collaboration on those issues, with a particular focus on JUnit. It seems @sormuras has a particular interest in JPMS modules, but my research team and I would be excited to discuss with anyone else on the team to help guide our research so that it helps the JUnit and Java communities. We are further working hard to seek funding opportunities to support our research, and we think it would be great to have JUnit developers as collaborators. Thank you very much for your time and consideration!

@junit-team junit-team locked and limited conversation to collaborators Jun 15, 2023
@sormuras sormuras converted this issue into discussion #3356 Jun 15, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

2 participants