Welcome To Our Shell

Mister Spy & Souheyl Bypass Shell

\documentclass[12pt]{article}
%  <gfmt>  tex386 latex2e German 850tex

\usepackage{english}
\usepackage[utf8]{inputenc}
\usepackage{color}
\usepackage{graphicx}
\textwidth        170mm
\textheight       282mm
\oddsidemargin      0mm
\evensidemargin     0mm
\topmargin          0mm
\parindent  0mm 
\headheight 0mm
\headsep    4mm
%\topskip    0mm

\pagestyle{plain}

\sf
\begin{document}
{\huge\sf\bfseries Test Plan}

\vspace{30mm}

{\large\sf
<Project name> \\
PM-No. xxyy \\


\begin{tabular}{p{40mm}p{42mm}}
Date:   & dd.mm.yyy \\
Name:   & first name, surname, department
\end{tabular}
}

\newpage


{\large\sf\bfseries Document status} \\
\vspace{6mm}
\begin{tabular}{|p{60mm}|p{60mm}|}
Document details     &                                          \\ \hline
Publisher      & Project Team member name                       \\ \hline
Title          & Test Plan                                      \\ \hline
Document type  & Specification and Use Cases                    \\ \hline
Binding nature & Mandatory                                      \\ \hline
Document name  & TestPlan.doc                                   \\ \hline
Language       & English                                        \\ \hline
\end{tabular}

\vspace{30mm}

{\large\sf\bfseries Document history} \\
\vspace{6mm}
\begin{tabular}{|p{30mm}|p{40mm}|p{80mm}|}
Version        &  Date         & Details                          \\ \hline
1.0            &  tt-mmm-yyyy  &  First version of the Test Plan  \\ \hline
\end{tabular}

\newpage

{\small\sf \tableofcontents}


\newpage

\section{Introduction}

\subsection{Scope of the Document}

{\small\sf A ''Test Plan'' documents the strategy that will be used to verify and ensure
that a service meets its Design Specification and Requirements
Specification. It covers the testing during Development phase as well as
during Piloting phase and Rollout phase and specifies what is to be done
how and when and by whom. Furthermore test coverage (which requirements are
verified when?) has to be defined.
}


\subsection{Service Identification}

{\small\sf \begin{tabular}{|p{60mm}|p{60mm}|} \hline
Name:             & <xyz-service>  \\ \hline
Short name:       & <Name>         \\ \hline
Version:          & <1.0>          \\ \hline
Identification    & <0123>         \\ \hline
Number:           &                \\ \hline
Description:      & <Description>  \\ \hline
\end{tabular}
}


\subsection{References}

{\small\sf \begin{tabular}{|p{30mm}|p{60mm}|p{80mm}|} \hline
No. & Document Name & Link (if applicable) \\ \hline\hline
    &               &                      \\ \hline
    &               &                      \\ \hline
    &               &                      \\ \hline
\end{tabular}
}

\subsection{Definitions and acronyms}

{\small\sf All the terms necessary to properly interpret the “Test Plan”, including
acronyms and abbreviations are provided below.

\begin{tabular}{|p{30mm}|p{60mm}|p{80mm}|} \hline
No. &  Acronym / Term  & Description  \\ \hline\hline
    &                  &              \\ \hline
    &                  &              \\ \hline
    &                  &              \\ \hline
    &                  &              \\ \hline
\end{tabular}
}

\subsection{Instructions for filling this template}

{\small\sf Replace all text in angle brackets ('<...>') by your own text.
If there are different test cases for the rollout in different sites, add
additional subchapters for each site. \\
Fill chapters 1 and 2 for ITG40. Fill chapters 3 to 5 for ITG50. Document
is to be released for ITG50.
}

\newpage


\section{Test Strategy}


\subsection{Test Types}

{\small\sf This testing in Development phase includes the following types of tests:
<add other types / edit for your project>
\begin{itemize}
\item
   Functional / Feature test: Verification that the service meets its
   functional/feature requirements
\item
   Load and performance test: Testing to confirm that performance objectives
   are satisfied
\item
   Configuration and interoperability test: Testing to assure that all
   functions work under all combinations, on all required hardware platforms,
   with all necessary software versions, etc.
\item
   Stress test: Testing which attempts to break the service by stressing all
   of its resources
\item
   Recovery and error handling test: Testing to confirm that the service
   recovers from hardware and/or software malfunctions without losing data or
   control, or that it follows the error handling requirements defined for the
   service
\item
   Usability test: Testing to assure the user interface is appropriate to the
   audience; that the service is maintainable, etc.
\item
   Regression test: to be performed on an existing service, to verify that
   existing functionality didn't get broken when other aspects of the
   environment are changed
\item
   Information Security test: Testing to assure the security of all managed
   data, etc.
\item
   Etc.
\end{itemize}
}

\subsection{High Level Testing Timeline}

{\small\sf <Modify following table according to your needs.>

\begin{tabular}{|p{80mm}|p{70mm}|} \hline
Task                               & Data / Data range   \\ \hline 
Test environment preparation       &                     \\ \hline                 
Test start                         &                     \\ \hline                 
First test data and defect log     &                     \\ \hline                 
review                             &                     \\ \hline                 
Functional tests                   &                     \\ \hline                 
Performance and stress tests       &                     \\ \hline                 
Regression tests                   &                     \\ \hline                 
Etc.                               &                     \\ \hline                 
\end{tabular}
}

\subsection{Personnel / Resources involved}

{\small\sf <Identify all personnel to be involved directly in the testing or in
critical supporting roles. Define the responsibilities assigned to each.>

\begin{tabular}{|p{50mm}|p{30mm}|p{30mm}|p{30mm}|p{30mm}|} \hline
Who          & Role         & Responsibility & Contact       & Backup Contact \\ \hline\hline
             &              &                &               &                \\ \hline
             &              &                &               &                \\ \hline
\end{tabular}
}


\subsection{Equipment, Supplies, Facilities}

{\small\sf <Identify all tools, facilities, test equipment required and who is
expected to provide them.
}

\subsection{Problem Recording, Issue Management and Rework}

{\small\sf <Define the mechanism to be used for problem recording and resolution,
escalation of issues if necessary and recording of associated changes to
the service. Define the process for rework, review and retest of any
element which needs modification. This process must include sufficient
retests to verify that any modifications have not impacted other functions
already tested>
}


\newpage

\section{Test Cases for Development Phase}


\newpage

\section{Test Cases for Piloting Phase}

{\small\sf <Describe here the test cases for the piloting phase related to the
different pilot users (a separate chapter for each user/user group>.
}

\newpage


\section{Test Cases for Rollout Phase}

{\small\sf <If there are different test cases for different rollout sites this has to
be explained and defined here.>
}

\end{document}