From 4cabd6418ed47409ca394f63853df7ea9bbb6273 Mon Sep 17 00:00:00 2001 From: Godmar Back Date: Fri, 29 Aug 2008 14:00:35 +0000 Subject: [PATCH] added test case table --- sigcse2009/Makefile | 2 +- sigcse2009/assignments.tex | 7 +++++-- sigcse2009/figures.tex | 14 ++++++++++++++ sigcse2009/principles.tex | 2 +- 4 files changed, 21 insertions(+), 4 deletions(-) diff --git a/sigcse2009/Makefile b/sigcse2009/Makefile index 86b09e2..6f0e48c 100644 --- a/sigcse2009/Makefile +++ b/sigcse2009/Makefile @@ -9,4 +9,4 @@ $(BASE).pdf: $(BASE).tex introduction.tex abstract.tex $(BASE).bib principles.te -bibtex $(BASE) pdflatex $(BASE).tex pdflatex $(BASE).tex - + test -d /home/gback/public_html && /bin/cp -f $(BASE).pdf /home/gback/public_html diff --git a/sigcse2009/assignments.tex b/sigcse2009/assignments.tex index 5fd3b88..dd4d48b 100644 --- a/sigcse2009/assignments.tex +++ b/sigcse2009/assignments.tex @@ -1,6 +1,8 @@ \section{Assignments} \label{sec:assignments} +\pintostestcounttable{} + % % Not sure if we need that. % @@ -53,8 +55,9 @@ priority scheduler. This scheduler adjusts threads' priority based on a samplin 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 diff --git a/sigcse2009/figures.tex b/sigcse2009/figures.tex index 761b797..5510a75 100644 --- a/sigcse2009/figures.tex +++ b/sigcse2009/figures.tex @@ -20,3 +20,17 @@ \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} +} diff --git a/sigcse2009/principles.tex b/sigcse2009/principles.tex index 359ee88..059ba71 100644 --- a/sigcse2009/principles.tex +++ b/sigcse2009/principles.tex @@ -29,7 +29,7 @@ own data structures and associated algorithms as much as possible. %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} -- 2.30.2