You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry I can't understand what you mean.
In my opinion the JVM and Java language are not the right place to standardise testing.
In Java with already have 'assert' but most probably we could have lived well without it.
Are you talking about adding tricks and hackable points to ease inspection and mutation of JVM state, objects....?
We are seeing that more and more the JVM is closing most of the doors that allow tweaking memory contents, but they have their reasons (mostly about security and having the ability to change the JVM without breaking code)
Unless I missed the intention of the project, if the intent of the project was to standardize on some interfaces and framework for testing on the JVM, then it seemed standardizing via a Java Community Process JSR would help.
This would be similar to how the Logging API JSR was developed in the context of Logging on the JVM and/or in Java.
This is a suggestion to establish a Test JSR to help in the process of standardizing test on JVM.
Can utilize opentest4j as reference implementation and/or TCK as applicable.
See http://jcp.org for more info.
The text was updated successfully, but these errors were encountered: