10/24/16 & 0.2 & Add Unit Testing and Usability Survey \\
10/24/16 & 0.1 & Added Unit Testing and Usability Survey \\
10/24/16 & 0.3 & Add most of section 2 \\
10/24/16 & 0.2 & Added Most of Section 2 \\
\bottomrule
10/24/16 & 0.3 & Added Section 1 \\
\end{tabularx}
\bottomrule
\end{tabularx}
\end{table}
\end{table}
\newpage
\newpage
\pagenumbering{arabic}
% Report Content
This document ...
\pagenumbering{arabic}
\section{General Information}
\section{General Information}
\subsection{Purpose}
\subsection{Purpose}
The purpose of this document is to explore the verification process that will be applied to the Rogue Reborn project. After reviewing the document, the reader should understand the strategy, focus, and motivation behind the efforts of the Rogue++ testing team.
\subsection{Scope}
\subsection{Scope}
This report will encompass all technical aspects of the testing environment and implementation plan, as well as other elements in the domain of team coordination and project deadlines. The document will also strive to be comprehensive by providing context behind critical decisions, motivating the inclusion of particular features by referring to the existing \textit{Rogue} implementation, and offering a large variety of tests for various purposes and hierarchical units. Aside from the implementation, the report will also discuss a relevant component from the requirements elicitation process.
\subsection{Acronyms, Abbreviations, and Symbols}
\subsection{Acronyms, Abbreviations, and Symbols}
\begin{table}[hbp]
\begin{table}[H]
\caption{\textbf{Table of Abbreviations}}\label{Table}
\centering
\caption{\textbf{Table of Abbreviations and Acronyms}}
\begin{tabularx}{\textwidth}{p{3cm}X}
\label{TableAbbreviations}
\toprule
\bigskip
\textbf{Abbreviation}&\textbf{Definition}\\
\begin{tabularx}{\textwidth}{p{3cm}X}
\midrule
\toprule
Abbreviation1& Definition1\\
\textbf{Abbreviation}&\textbf{Definition}\\
Abbreviation2 & Definition2\\
\midrule
\bottomrule
PoC & Proof of Concept\\
\end{tabularx}
\bottomrule
\end{tabularx}
\end{table}
\end{table}
\begin{table}[!htbp]
\begin{table}[H]
\caption{\textbf{Table of Definitions}}\label{Table}
\centering
\caption{\textbf{Table of Definitions}}
\begin{tabularx}{\textwidth}{p{3cm}X}
\label{TableDefinitions}
\bigskip
\begin{tabularx}{\textwidth}{p{3cm}X}
\toprule
\toprule
\textbf{Term}&\textbf{Definition}\\
\textbf{Term}&\textbf{Definition}\\
\midrule
\midrule
Term1 & Definition1\\
\textbf{Boost}& C++ utility library that includes a comprehensive unit testing framework\\
Term2 & Definition2\\
\textbf{Libtcod}& Graphics library that specializes in emulating a roguelike experience\\
\textbf{Permadeath}& Feature of roguelike games whereby a character death will end the game\\
\textbf{Roguelike}& Genre of video games characterized by ASCII graphics, procedurally-generated levels, and permadeath\\
\bottomrule
\bottomrule
\end{tabularx}
\end{tabularx}
\end{table}
\end{table}
\subsection{Overview of Document}
\subsection{Overview of Document}
The early sections of the report will describe the testing environment and the logistic components of the Rogue Reborn testing effort, including the schedule and work allocation. Next, a suite of tests will be discussed with respect to the functional requirements, nonfunctional requirements, and proof of concept demonstration. Upon discussing the relevance of this project to the original \textit{Rogue}, a variety of unit tests will be given followed by a sample usability survey to guage the interest and opinion of the Rogue Reborn game. A breakdown of the sections is listed below:
\begin{itemize}
\item\S1 - Brief overview of the report contents
\item\S2 - Project logistics and the software testing environment
\item\S3 - Description of system-level integration tests (based on requirements)
\item\S4 - Explanation of test plans that were inspired by the PoC demonstration
\item\S5 - Comparison of the existing \textit{Rogue} to the current project in the context of testing
\item\S6 - Outline of the module-level unit tests
\item\S7 - Appendix for symbolic parameters and the aforementioned usability survey
\end{itemize}
\newpage
\section{Plan}
\section{Plan}
\subsection{Software Description}
\subsection{Software Description}
...
@@ -158,6 +191,7 @@ This document ...
...
@@ -158,6 +191,7 @@ This document ...
See Gantt Chart at the following url ... TODO
See Gantt Chart at the following url ... TODO
\newpage
\section{System Test Description}
\section{System Test Description}
\subsection{Tests for Functional Requirements}
\subsection{Tests for Functional Requirements}
...
@@ -235,6 +269,7 @@ This document ...
...
@@ -235,6 +269,7 @@ This document ...
\subsubsection{Area of Testing2}
\subsubsection{Area of Testing2}
...
...
\newpage
\section{Tests for Proof of Concept}
\section{Tests for Proof of Concept}
\subsection{Area of Testing1}
\subsection{Area of Testing1}
...
@@ -273,10 +308,11 @@ This document ...
...
@@ -273,10 +308,11 @@ This document ...
...
...
\newpage
\section{Comparison to Existing Implementation}
\section{Comparison to Existing Implementation}
\newpage
\section{Unit Testing Plan}
\section{Unit Testing Plan}
After examining the boost library's utilities for unit testing, we have decided we will not use a unit testing framework for testing the product. We concluded that adding a framework would not make the work significantly easier, while reducing our flexibility and adding installation difficulties.
After examining the boost library's utilities for unit testing, we have decided we will not use a unit testing framework for testing the product. We concluded that adding a framework would not make the work significantly easier, while reducing our flexibility and adding installation difficulties.
...
@@ -297,7 +333,6 @@ This document ...
...
@@ -297,7 +333,6 @@ This document ...
% \bibliography{SRS}
% \bibliography{SRS}
\newpage
\newpage
\section{Appendix}
\section{Appendix}
This is where you can place additional information.
This is where you can place additional information.
