-
Notifications
You must be signed in to change notification settings - Fork 98
/
Copy pathREADME.html
89 lines (74 loc) · 3.93 KB
/
README.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
<h1>Oracle Code One Lambda Programming Laboratory</h1>
<h2>Introduction</h2>
<p>Welcome to the Lambda Programming Laboratory! The goal of this
lab is for you to learn about the lambda expressions, default methods,
and APIs (particularly the Streams library) introduced in Java 8, plus
a few API additions in Java 9 and 10.</p>
<p>The lab is structured as a set of exercises in the form of JUnit
tests. To complete each exercise, write some code that uses a
lambda or new API that enables the test to pass.</p>
<h2>Lab Instructions</h2>
<ol>
<li><p>Open the NetBeans development build (or your favorite IDE).</p></li>
<li><p>Open the LambdaLab project. If you don't have it, it can be cloned
from github:</p>
<p>git clone https://github.com/stuart-marks/LambdaHOLv2</p></li>
<li><p>Inside the LambdaLab project, open the Test Packages folder.</p></li>
<li><p>Open up one of the following exercise files:</p>
<pre><code>A_Lambdas.java
B_Comparators.java
C_DefaultMethods.java
D_SimpleStreams.java
E_IntermediateStreams.java
F_AdvancedStreams.java
G_MatcherScanner.java
H_Challenges.java
</code></pre></li>
<li><p>Each exercise is in the form of a single JUnit test method. Each
test is marked with an @Ignore annotation so that JUnit will skip that
test initially.</p></li>
<li><p>To work on a test, delete the @Ignore annotation, fill in code at
the // TODO marker, trying to avoid modifying any setup code above the
TODO marker and assertion code below the TODO marker.</p></li>
<li><p>Press Control-F6 to run the tests in this file.</p></li>
<li><p>Make all the tests pass and get a 100% green bar!</p></li>
</ol>
<h2>Detailed Test Description</h2>
<p>At the top of each exercise is a comment that describes the goal of
the exercise. Within the test method, there is a // TODO comment that
marks the location where you need fill in some implementation
code. There may be some setup code above the // TODO comment, and
there will be some assertion-checking code below. You shouldn't have
to modify any of the setup code at the top of the test method or the
assertions at the bottom of the test method.</p>
<p>There is sometimes a hint or two after a test method. If you're having
trouble with an exercise, look for hints. The hint text is inside
a editor fold that is closed by default, so click on the plus-sign
in the left margin to read it.</p>
<p>The intent of the exercises is to solve them using the Java 8 lambda
expressions feature, the Java 8 default methods feature, the Java 8
Streams API, and other APIs added in Java 8 or Java 9. Of course, it
is possible to use conventional Java code, such as for-loops, but all
of the exercises are amenable to being solved using new features in
just a handful of lines. Most exercises will take less than half a
dozen lines. Some of the more difficult exercises may take up to eight
lines, depending upon how aggressive you are about breaking
lines. None of the exercises involve writing large amounts of
code. Most of the streams-based exercises involve writing a single
stream pipeline.</p>
<p>Several of the exercises read data from a text file. The field named
"reader" is a BufferedReader which will be opened for you on the text
file. In any exercise that refers to reading from the text file, you
can simply use the "reader" variable without worry about opening or
closing it. This is set up by JUnit using the @Before and @After
methods at the bottom of the file. The text file is "SonnetI.txt"
(Shakespeare's first sonnet) which is located at the root of this
NetBeans project.</p>
<p>If you're really stuck, the solutions to the exercises are in the package</p>
<pre><code> Test Packages > solutions
</code></pre>
<p>There is one solutions file corresponding to each exercise file. Many
exercises can be solved in several different ways. In some cases, the
solutions file will have several alternatives. Even if you've solved
an exercise, it can be useful to look at the solutions to compare your
solutions with those of the lab authors.</p>