\section{Assignments}
\label{sec:assignments}
+\pintostestcounttable{}
+
%
% Not sure if we need that.
%
much CPU time a thread has received recently.
\paragraph{Testing and Grading}
-Project 1 is accompanied by about $XX$ tests, which are run using the Bochs simulator by
-a grading script. Most tests are designed to test a single aspect, but some tests
+Project 1 is accompanied by 27 tests as shown in Table~\ref{table:tests}, which are
+run using the Bochs simulator by a grading script.
+Most tests are designed to test a single aspect, but some tests
test more involved scenarios. Most of the tests are designed to produce a deterministic
output; the grading script will point out differences between the expected and the actual output.
Usually, a test failure leads students to study the documented source code of the test
\label{fig:pintosdetail}
\end{figure*}
}
+
+\newcommand{\pintostestcounttable}{
+\begin{table}
+ \begin{tabular}{lccc}
+ Project & Functionality & Robustness & Regression \\
+ 1 & 27 & - & - \\
+ 2 & 41 & 35 & - \\
+ 3 & 20 & 14 & 75 \\
+ 4 & 39 & 7 & 75 \\
+ \end{tabular}
+ \caption{Pintos test cases by project.}
+ \label{table:tests}
+\end{table}
+}
%Test-driven development~\cite{Edwards}
Each project includes a large number of test cases that is accessible
to students.
-They must implement the API that is exercised by these test cases.
+They must implement the API that is exercised by these test cases. An overview is provided in Table~\ref{table:tests}.
Students are encouraged to add their own test cases.
\paragraph{Work in a Team}