junit4

junit4 copied to clipboard

# Security Vulnerability Fix This pull request fixes either 1.) Temporary Directory Hijacking Vulnerability, or 2.) Temporary Directory Information Disclosure Vulnerability, which existed in this project. ## Preamble The system...

JLLeitschuh

Update to hamcrest 2.2

16

Can we have a version of junit4 with a recent version of hamcrest? Thanks

juliocbcotta

Resolves #1739.

marcphilipp

This code fails to compile on JDK 18 and newer: https://github.com/junit-team/junit4/blob/cc7c500584fcb85eaf98c568b7441ceac6dd335c/src/main/java/org/junit/runner/Result.java#L190-L198 ```java src/main/java/org/junit/runner/Result.java:192: error: unreported exception ClassNotFoundException; must be caught or declared to be thrown fCount = (AtomicInteger) fields.get("fCount", null);...

cushon

If subclassing the Suite class one can implement a constructor which can invoke a custom static method to specify test suite classes. This is currently not possible with subclasses ob...

dbratusa

Another attempt to solve #1720 The only my motivation - if this would help with improving testcontainers support of junit5 :-)

panchenko

@Rule execution order looks to have been guaranteed since 4.12 but is not documented as such

1

My understanding is that https://github.com/junit-team/junit4/commit/c75dcc28810aeb1c918ee7430981b31f41742ea7#diff-f35409420f2540415a9878beaf5a537248f301b6c683bb87a11016be3c9dc8b8R55 caused JUnit to begin processing `@Rule` fields in a defined order. The `@Rule` Javadoc, however, still [states](https://github.com/junit-team/junit4/blob/7167b23b3ba7dd79410f6e9db350d16cbe30617b/src/main/java/org/junit/Rule.java#L20-L22) that the order is defined by the JVM's...

cpovirk

Validate actual rule object instead of Field#type for @Rule

22

Currently, JUnit validates field's type, and it wants the declaration to implement `TestRule`. Is there a reason for that? What if JUnit4 validated the actual value rather than field type?...

vlsi

fixes #1720

vlsi

kluever