-
```
The junit guys have removed "junit-dep"; if I want hamcrest I need to specify
it myself (this is good).
The hamcrest guys have created a "hamcrest-integration" jar which brings in a
tree of dep…
-
```
The junit guys have removed "junit-dep"; if I want hamcrest I need to specify
it myself (this is good).
The hamcrest guys have created a "hamcrest-integration" jar which brings in a
tree of dep…
-
I'm trying to write a test similar to
```jsl
uttest("some case", "localhere",
Expr(
LocalHere(
::utassertthat(Expr(1+2), ::utgreaterthan(2), "Simple")
)
)
);
```
And g…
-
Given that this plugin will already detect testing frameworks like JUnit and add the appropriate --add-reads and --add-opens, can we do the same thing for Hamcrest and other common testing libraries?
-
```
There seems to be a regression in Hamcrest 1.3.RC2 (might date from earlier
versions) when compared to Hamcrest 1.1, to do with nested matchers. The
following test case works in Hamcrest 1.1:
…
-
```
The junit guys have removed "junit-dep"; if I want hamcrest I need to specify
it myself (this is good).
The hamcrest guys have created a "hamcrest-integration" jar which brings in a
tree of dep…
-
```
The junit guys have removed "junit-dep"; if I want hamcrest I need to specify
it myself (this is good).
The hamcrest guys have created a "hamcrest-integration" jar which brings in a
tree of dep…
-
```
The junit guys have removed "junit-dep"; if I want hamcrest I need to specify
it myself (this is good).
The hamcrest guys have created a "hamcrest-integration" jar which brings in a
tree of dep…
-
```
There seems to be a regression in Hamcrest 1.3.RC2 (might date from earlier
versions) when compared to Hamcrest 1.1, to do with nested matchers. The
following test case works in Hamcrest 1.1:
…
-
```
The junit guys have removed "junit-dep"; if I want hamcrest I need to specify
it myself (this is good).
The hamcrest guys have created a "hamcrest-integration" jar which brings in a
tree of dep…