summaryrefslogtreecommitdiffstats
path: root/notFinishedCode
diff options
context:
space:
mode:
authorRefik Hadzialic2011-10-21 16:38:18 +0200
committerRefik Hadzialic2011-10-21 16:38:18 +0200
commita33c1f37817ec4579cc4d3d6db6ab977c8782e1a (patch)
tree69073255371cf8f88d8e21f5e38d07cb78079f13 /notFinishedCode
parentReport writing! (diff)
downloadgsm-selftest-a33c1f37817ec4579cc4d3d6db6ab977c8782e1a.tar.gz
gsm-selftest-a33c1f37817ec4579cc4d3d6db6ab977c8782e1a.tar.xz
gsm-selftest-a33c1f37817ec4579cc4d3d6db6ab977c8782e1a.zip
Report writing!
Diffstat (limited to 'notFinishedCode')
-rw-r--r--notFinishedCode/Report/test.log14
-rw-r--r--notFinishedCode/Report/test.pdfbin1468047 -> 1469203 bytes
-rw-r--r--notFinishedCode/Report/test.tex8
-rw-r--r--notFinishedCode/Report/test.tex.backup11
-rw-r--r--notFinishedCode/Report/test.tex~8
5 files changed, 30 insertions, 11 deletions
diff --git a/notFinishedCode/Report/test.log b/notFinishedCode/Report/test.log
index e3f0a4b..b0594ed 100644
--- a/notFinishedCode/Report/test.log
+++ b/notFinishedCode/Report/test.log
@@ -1,4 +1,4 @@
-This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 21 OCT 2011 15:52
+This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2011.9.27) 21 OCT 2011 16:33
entering extended mode
%&-line parsing enabled.
**test.tex
@@ -343,9 +343,9 @@ File: serialPort.png Graphic file (type png)
<use serialPort.png>
[11 <./dbClass.png (PNG copy)>]
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <9> on input line 210.
+(Font) <9> on input line 216.
LaTeX Font Info: External font `cmex10' loaded for size
-(Font) <5> on input line 210.
+(Font) <5> on input line 216.
<serverClass.png, id=59, 302.12875pt x 181.67876pt>
File: serverClass.png Graphic file (type png)
@@ -386,17 +386,17 @@ File: sshTunnel.png Graphic file (type png)
<use sshTunnel.png> [19
<./sshTunnel.png (PNG copy)>] [20] [21]
-LaTeX Font Info: Try loading font information for OMS+cmr on input line 492.
+LaTeX Font Info: Try loading font information for OMS+cmr on input line 498.
(/usr/share/texmf-texlive/tex/latex/base/omscmr.fd
File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions
)
LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <9> not available
-(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 492.
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 498.
[22] [23] [24]
LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10.95> not available
-(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 564.
+(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 570.
<resultsImage.png, id=114, 702.625pt x 431.6125pt>
File: resultsImage.png Graphic file (type png)
@@ -425,7 +425,7 @@ r/fonts/pk/ljfour/jknappen/ec/ecrm1728.600pk></usr/share/texmf-texlive/fonts/ty
pe1/public/amsfonts/cm/cmmi10.pfb></usr/share/texmf-texlive/fonts/type1/public/
amsfonts/cm/cmsy10.pfb></usr/share/texmf-texlive/fonts/type1/public/amsfonts/cm
/cmsy9.pfb>
-Output written on test.pdf (28 pages, 1468047 bytes).
+Output written on test.pdf (28 pages, 1469203 bytes).
PDF statistics:
683 PDF objects out of 1000 (max. 8388607)
0 named destinations out of 1000 (max. 500000)
diff --git a/notFinishedCode/Report/test.pdf b/notFinishedCode/Report/test.pdf
index 2cd55f7..3c7f22d 100644
--- a/notFinishedCode/Report/test.pdf
+++ b/notFinishedCode/Report/test.pdf
Binary files differ
diff --git a/notFinishedCode/Report/test.tex b/notFinishedCode/Report/test.tex
index 331df7c..647261d 100644
--- a/notFinishedCode/Report/test.tex
+++ b/notFinishedCode/Report/test.tex
@@ -167,7 +167,13 @@ The \emph{taskNo} attribute identifies the test number but not a single test (e.
Before any test attempt is made, our test software first tries to ping the servers. These results are then stored in the \emph{PingResultTable}.
\par The \emph{ErrorCodeTable} table defines all the error codes in the project, in other words it represents a list with error codes with their meanings. It consists of two attributes (\emph{errorcode} and \emph{description}), the first is of integer type and the second of varchar type (the description message is allowed to be only 100 characters long).
The \emph{ErrorCodeTable} table is used by the main test software (i.e. controller) to report the operator user what kind of error had appeared in the system.
-\par The \emph{DeviceAddressTable} is the table containing the location and identification data for each server and device. The table consists of seven attributes. \emph{deviceName} is the attribute with the name of the device (e.g. GSMRZ1 or landline).
+\par The \emph{DeviceAddressTable} is the table containing the location and identification data for each server and device. The table consists of seven attributes, \emph{deviceName, portName, number, lastChange, username, password, server}.
+\emph{deviceName} is the attribute with the name of the device or server (e.g. GSMRZ1 or landline), it is of varchar type. \emph{portName} is the attribute field with the location address for a cell phone (e.g. \emph{/dev/ttyUSB1}) or 'localhost' instead of NULL value for a server, it is of the varchar type.
+\emph{number} represents the number of the used service (i.e. number of the cell phone, SIP, etc.) and is of varchar type.
+\emph{lastChange} is a time value and represents the date and time the given entry was modified (we had plans in future versions of our test software that if an device gets a new IP address assigned it automatically changes it in the database).
+\emph{username} is the field with the username stored in for a server/service, like SIP and landline. \emph{password} attribute stores the password information for the given service. The \emph{server} attribute stores information about the location of the server, IP or DNS address of the server. All three fields, \emph{username}, \emph{password} and \emph{server} are of varchar type.
+The information stored in the given table is used by the test software to obtain usernames, passwords and addresses of the used services for the tests.
+\par The \emph{ResultTable} table is used by the test system to store final results for the performed tests. Our given table consists of two fields, \emph{taskID} and \emph{result} and both are of integer type.
\newpage
\section{Software design} % section 2.1
\begin{figure}[ht!]
diff --git a/notFinishedCode/Report/test.tex.backup b/notFinishedCode/Report/test.tex.backup
index 8e92706..4e3b28d 100644
--- a/notFinishedCode/Report/test.tex.backup
+++ b/notFinishedCode/Report/test.tex.backup
@@ -165,8 +165,15 @@ The \emph{taskNo} attribute identifies the test number but not a single test (e.
\emph{gsmBox1} and \emph{gsmBox2} are the two single-chip Linux computers (BeagleBoard), that controll two cell phones each one (i.e. they are also known under the name of \emph{nanoBTSx}).
\emph{taskNo} is the primary and unique key in the table \emph{PingResultTable}. Rest of the attributes (i.e. \emph{sipServer, sipGate, uniSip, gsmBox1, gsmBox2}) are used to insert the ping results, if the assigned servers are reachable or not.
Before any test attempt is made, our test software first tries to ping the servers. These results are then stored in the \emph{PingResultTable}.
-\par The \emph{ErrorCodeTable} table defines all the error codes in the project, in other words it represents a list with numbers with their meanings. It consists of two attributes (\emph{errorcode} and \emph{description}).
-In the first field the error code number can be seen and in the later its description.
+\par The \emph{ErrorCodeTable} table defines all the error codes in the project, in other words it represents a list with error codes with their meanings. It consists of two attributes (\emph{errorcode} and \emph{description}), the first is of integer type and the second of varchar type (the description message is allowed to be only 100 characters long).
+The \emph{ErrorCodeTable} table is used by the main test software (i.e. controller) to report the operator user what kind of error had appeared in the system.
+\par The \emph{DeviceAddressTable} is the table containing the location and identification data for each server and device. The table consists of seven attributes, \emph{deviceName, portName, number, lastChange, username, password, server}.
+\emph{deviceName} is the attribute with the name of the device or server (e.g. GSMRZ1 or landline), it is of varchar type. \emph{portName} is the attribute field with the location address for a cell phone (e.g. \emph{/dev/ttyUSB1}) or 'localhost' instead of NULL value for a server, it is of the varchar type.
+\emph{number} represents the number of the used service (i.e. number of the cell phone, SIP, etc.) and is of varchar type.
+\emph{lastChange} is a time value and represents the date and time the given entry was modified (we had plans in future versions of our test software that if an device gets a new IP address assigned it automatically changes it in the database).
+\emph{username} is the field with the username stored in for a server/service, like SIP and landline. \emph{password} attribute stores the password information for the given service. The \emph{server} attribute stores information about the location of the server, IP or DNS address of the server. All three fields, \emph{username}, \emph{password} and \emph{server} are of varchar type.
+The information stored in the given table is used by the test software to obtain usernames, passwords and addresses of the used services for the tests.
+\par The \emph{ResultTable} table is used by the test system to store final results for the test cases.
\newpage
\section{Software design} % section 2.1
\begin{figure}[ht!]
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index a38ea54..4e3b28d 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -167,7 +167,13 @@ The \emph{taskNo} attribute identifies the test number but not a single test (e.
Before any test attempt is made, our test software first tries to ping the servers. These results are then stored in the \emph{PingResultTable}.
\par The \emph{ErrorCodeTable} table defines all the error codes in the project, in other words it represents a list with error codes with their meanings. It consists of two attributes (\emph{errorcode} and \emph{description}), the first is of integer type and the second of varchar type (the description message is allowed to be only 100 characters long).
The \emph{ErrorCodeTable} table is used by the main test software (i.e. controller) to report the operator user what kind of error had appeared in the system.
-\par The \emph{DeviceAddressTable} is the table containing the location and identification data for each server and device. The table consists of seven attributes.
+\par The \emph{DeviceAddressTable} is the table containing the location and identification data for each server and device. The table consists of seven attributes, \emph{deviceName, portName, number, lastChange, username, password, server}.
+\emph{deviceName} is the attribute with the name of the device or server (e.g. GSMRZ1 or landline), it is of varchar type. \emph{portName} is the attribute field with the location address for a cell phone (e.g. \emph{/dev/ttyUSB1}) or 'localhost' instead of NULL value for a server, it is of the varchar type.
+\emph{number} represents the number of the used service (i.e. number of the cell phone, SIP, etc.) and is of varchar type.
+\emph{lastChange} is a time value and represents the date and time the given entry was modified (we had plans in future versions of our test software that if an device gets a new IP address assigned it automatically changes it in the database).
+\emph{username} is the field with the username stored in for a server/service, like SIP and landline. \emph{password} attribute stores the password information for the given service. The \emph{server} attribute stores information about the location of the server, IP or DNS address of the server. All three fields, \emph{username}, \emph{password} and \emph{server} are of varchar type.
+The information stored in the given table is used by the test software to obtain usernames, passwords and addresses of the used services for the tests.
+\par The \emph{ResultTable} table is used by the test system to store final results for the test cases.
\newpage
\section{Software design} % section 2.1
\begin{figure}[ht!]