TUHH/software-testing
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Finish first task

Browse Source
This commit is contained in:
Michael Chen 2022-05-04 19:17:14 +02:00
parent 5a08ed557c
commit e9dec446af
No known key found for this signature in database
GPG Key ID: 1CBC7AA5671437BB
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
project_task_sheets/phase_02/project_phase02_tasks/Solution_Phase02_MichaelChen.tex
View File

@ -63,8 +63,8 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\def\name{[Add name here]} \def\name{Michael Chen}
\def\group{[Add group here]} \def\group{Group 01 (fastjson)}
\begin{document} \begin{document}
\projectinfo{2}{Software Testing - Input Space Partitioning\small}{\today}{\name}{\group} \projectinfo{2}{Software Testing - Input Space Partitioning\small}{\today}{\name}{\group}
@ -78,22 +78,26 @@
\begin{enumerate} \begin{enumerate}
\item Input Domain \item Input Domain
\begin{answer} \begin{answer}
[TODO: Add answer here] The input domain is a set that contains all possible sets of input values a program accepts. For instance a function \texttt{int test(bool x, int y)} has the input domain:
\begin{equation}
\left\{ \left\{\texttt{true},0\right\}, \left\{\texttt{false},0\right\}, \left\{\texttt{true},1\right\}, \left\{\texttt{false},1\right\}, \left\{\texttt{true},-1\right\}, \left\{\texttt{false},-1\right\}, \dots \right\}
\end{equation}
Note however, that the input values to a function, especially in low-level programming also includes side-effects such as object state, global variables, persistent data, user input, and many others inherited from the environment. This makes pure functions or lambda functions with explicit captures easier to model.
\end{answer} \end{answer}
\item Domain Partition (include the two criteria a partitions needs to fulfill) \item Domain Partition (include the two criteria a partitions needs to fulfill)
\begin{answer} \begin{answer}
[TODO: Add answer here] A domain partition divides the domain in blocks that are pairwise distinct, meaning every element in the domain is contained by at most one of the blocks (\textit{disjointness}), and the union of those blocks is equivalent to the entire domain, meaning every element in the domain is contained by at least one of the blocks (\textit{completeness}). It follows that every element in the domain is contained by one and only one block in the partition.
\end{answer} \end{answer}
\item Characteristics \item Characteristics
\begin{answer} \begin{answer}
[TODO: Add answer here] A characteristic is a property of a domain that can be used to generate a corresponding partition that might be useful for testing. Characteristics usually capture interesting values or relations between different input values.
\end{answer} \end{answer}
\item Equivalence Class \item Equivalence Class
\begin{answer} \begin{answer}
[TODO: Add answer here] An equivalence class is set of values of a domain that are equivalent to another given an application specific equivalence relation, i.e. and area equivalence relation would create a set of equivalence classes of arbitrary shapes that have the same area. Using an equivalence relation corresponding to a well formed characteristic you can partition a domain.
\end{answer} \end{answer}
\end{enumerate} \end{enumerate}