Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content
This repository was archived by the owner on Oct 4, 2020. It is now read-only.

Commit 86aa582

Browse files
author
nipa
committed
Create a meaningful README
1 parent 0bfad92 commit 86aa582

File tree

1 file changed

+53
-2
lines changed

1 file changed

+53
-2
lines changed

README.md

+53-2
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,53 @@
1-
# lab-junitlambda
2-
Toying around with the JUnit Lambda Prototype
1+
# Lab: JUnit-Lambda
2+
3+
_Toying around with the JUnit Lambda Prototype_
4+
5+
---
6+
7+
On November 18th _[JUnit Lambda](http://junit.org/junit-lambda.html)_ presented their first [prototype](https://github.com/junit-team/junit-lambda/wiki/Prototype).
8+
I'm using this project to get to know the features and to demonstrate them.
9+
10+
## Compiling & Running
11+
12+
The prototype is only available in [Sonatype's snapshots repository](https://oss.sonatype.org/content/repositories/snapshots/org/junit/prototype/) and by default Maven will not access it.
13+
Adding the following [profile](http://maven.apache.org/guides/introduction/introduction-to-profiles.html) to your `settings.xml` will allow you to instruct Maven to do just that:
14+
15+
```xml
16+
<profile>
17+
<id>snapshots</id>
18+
<activation>
19+
<activeByDefault>false</activeByDefault>
20+
</activation>
21+
<repositories>
22+
<repository>
23+
<id>snapshots-repo</id>
24+
<url>https://oss.sonatype.org/content/repositories/snapshots</url>
25+
<releases>
26+
<enabled>false</enabled>
27+
</releases>
28+
<snapshots>
29+
<enabled>true</enabled>
30+
</snapshots>
31+
</repository>
32+
</repositories>
33+
</profile>
34+
```
35+
36+
This project should then compile with `mvn -P snapshots compile`.
37+
38+
The prototype [must be executed](https://github.com/junit-team/junit-lambda/wiki/Prototype-Running-Tests) with a bare-bones console runner and it is straight-forward to have Maven do that.
39+
This way the surefire plugin is not used but that's no problem. The runner will print a lot of colorful messages to the console.
40+
41+
The tests can simply be run with `mvn test`.
42+
43+
## Further Reading
44+
45+
A list of things you could read if you're interested in the topic:
46+
47+
* first and foremost, there is of course [the official documentation](https://github.com/junit-team/junit-lambda/wiki/Prototype)
48+
* there will be a [JUnit tag on my blog](http://blog.codefx.org/tag/junit/) collecting my posts about this
49+
50+
## Caveat Lector
51+
52+
Note that _JUnit Lambda_ is actively developed and very much a moving target.
53+
Anything presented here must be carefully reexamined before basing any opinions or even decisions on it.

0 commit comments

Comments
 (0)