bit-twist -> tcpdump. geen host OS gedoe. en wat over performance toegevoegd.

diff --git a/2approach.tex b/2approach.tex
index b6b5ca6..6c2d3e6 100644 (file)
--- a/2approach.tex
+++ b/2approach.tex
@@ -94,7 +94,7 @@ of the SUT.
 
 \subsection{Levels and types of testing} \label{levels}
 
-The client will deliver a product for certification. This means our team will only conduct acceptance testing and assume that the client who requested certification has conducted unit, module and integration testing. We will only be conducting black-box testing and the client is not required to handover any source-code. Initially we will conduct several basic test cases based on experience acquired from previous certification requests (error guessing). If the product fails these basic tests we reject it and seize all further activities. If the product is not rejected we will proceed with more thorough testing. For each test we produce a test report. If any of the test cases fail the product is still rejected but in order to deliver usable feedback to the client we will still produce a test report.
+The client will deliver a product for certification. This means our team will only conduct acceptance testing and assume that the client who requested certification has conducted unit, module and integration testing. We will only be conducting black-box testing and the client is not required to handover any source-code. Initially we will conduct several basic test cases based on experience acquired from previous certification requests (error guessing). If the product fails these basic tests we reject it and seize all further activities. If the product is not rejected we will proceed with more thorough testing. For each test we produce a test report. If any of the test cases fail the product is still rejected but in order to deliver usable feedback to the client we will still produce a test report. For each test case a performance analysis will be included. 
 
 \subsubsection{Test generation}
 
@@ -149,22 +149,22 @@ We will test all possible combinations of requests/packet order/packet content.
 
 \subsubsection{Test environment en automatization}
 
-All the tools we are going to use togetter with the SUT gives us the following collection of software.
+All the tools we are going to use together with the SUT gives us the following collection of software.
 
 \begin{enumerate}
        \item Windows, used as a host OS.
        \item Linux, used as both a host and guest OS.
        \item VirtualBox, used to run the guest OS containing the SUT.
-       \item Wireshark, used on the host in order to capture and analyze network traffic.
-       \item Bit-Twist, used to prepare network packets.
+       \item Wireshark, used on the guest in order to capture and analyze network traffic.
+       \item Tcpdump, used to prepare network packets.
 \end{enumerate}
 
-All test will be conducted in a virtual environment. We will use VirtualBox to run a Linux distro with the product installed. All the different tests are performed either in VirtualBox (basic tests) or from the host system (transmission analysis). When testing network transmissions we will only analyze the packets received on the host system which originate from the product running in the virtual environment. The host system is disconnected from the Internet or any other network in order to prevent unnecessary traffic.
+All test will be conducted in a virtual environment. We will use VirtualBox to run a Linux distro with the product installed. All the tests are performed from within the VirtualBox environment. When testing network transmissions we will only analyze the packets sent/received to/from the guest OS. The host system is disconnected from the Internet or any other network in order to prevent unnecessary traffic.
 
-For each test case (except for the basic tests) a file containing previously captured network traffic will be replayed using Wireshark. We will use Bit-Twist to update the prepared packets with the MAC address of the guest network adapter. The response packets coming from the guest OS will be recorded and analyzed at a later stage. The valid packets are obtained by capturing traffic between known working alternatives to the SUT. The invalid packets are generated from this valid traffic using Bit-Twist. The boundary values for the different parameters (fields in packets) are determined by hand.
+For each test case (except for the basic tests) a file containing previously captured network traffic will be replayed using Wireshark. We will use tcpdump to update the prepared packets with the MAC address of the guest network adapter. The response packets coming from the guest OS will be recorded and analyzed at a later stage. The valid packets are obtained by capturing traffic between known working alternatives to the SUT. Invalid packets are generated from this valid traffic using tcpdump. The boundary values for the different parameters (fields in packets) are determined by hand. Automated scripts are written that will generate packets with some fields replaced with these boundary values. The performance analysis will consists of measured latencies for all packets sent.
 
 \begin{enumerate}
        \item VirtualBox, https://www.virtualbox.org/
        \item Whireshark, https://www.wireshark.org/
-       \item Bit-Twist, http://bittwist.sourceforge.net/
+       \item Tcpdump, http://www.tcpdump.org/
 \end{enumerate}