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
\item[\S 1] Brief overview of the report contents
\item[\S 2] Project logistics and the software testing environment
\item[\S 3] Description of system-level integration tests (based on requirements)
\item[\S 4] Explanation of test plans that were inspired by the PoC demonstration
\item[\S 5] Comparison of the existing \textit{Rogue} to the current project in the context of testing
\item[\S 6] Outline of the module-level unit tests
\item[\S 7] Appendix for symbolic parameters and the aforementioned usability survey
