University of Buea

CSC 404
Software Engineering

Patriott Web Browser

Testing/Debugging/Validation
Version <1.0>
http://www.patriott.zzl.org

GROUP MEMBERS
Name Student ID
MADI WAMBA GILLES SC08A738
TCHAMDOU TCHATAT JULES AUDREY SC08A800
TONKEU NENDA FRANCE CYNTICHE SC08A810
NDANGANG YAMPA HAROLD SC08A757

Revision History
Date Version Description Author

INDEX

1. INTRODUCTION
2. TESTING

3. DEBUGGING

4. VALIDATION

1. INTRODUCTION
At this level of our project, a usable version of the program is already available, and we are very
happy; mostly happy because we each time found a way to bypass our difficulties in any aspect of the
program writing. The main difficulty we encountered was writing the code for the user interface, we
went across this one by using Qt designer; it is an automated GUI writing program. Here we are now
concerned in testing, debugging and validating the programm.

2. TESTING

Since the development of the program was strictly private, the main method of test was BENCH
TESTING, by each member of our project group.

In this testing, we discovered many bugs and errors (more than hundreds).

We could fix many of them just by reading the codes and identified some common syntax errors. More
difficult errors/bugs to fixe were logical errors, we perseverance, we also went across these ones.

The biggest errors/Bug were those making the program to crash, these error were very difficult, almost
impossible to identify by just reading the code, since most of them were due to an uninitialized
pointer, in other to identify these errors, we needed to Debug the program.

3. DEBUGGING

The debugger we used here was gdb (GNU Debugger).

The main command we used in other to follow the flow control in the program, and identify errors
were:
● Break, Continue, Next, Continue, Step
To stop the flow of the program at a particular line of code, to see if the bug occur befor or
after.

● Print, Watch
To keep track of values of variables at different time.

● Backtrace, Where
To identify the line of code that made the program to crash.

In this way, we fixed all bugs in the program, It was then time for Validation of the program.

2. VALIDATION

At this step, the program is ready; we just do some checks to see if all aspects of the specification
document are satisfied, so that we can deploy the program.
We did our validation testing; all the features mentioned in the specification document are well
implemented in accordance to that document except the support for HTML5 content.

In fact due to the web motors it uses ( Webkit ), Patriott does not render correctly HTML5 contents,
may be in a feature update of the Webkit module. this issue will be solved.

Also, HTML5 is a new language in writing web contents, so it is not yet generalized, so this issue is at
this moment a minor issue (That of course will be fixed).

Another issue is that on Ubuntu, the program will require the Qt libraries to be installed on the system;
the user can easily come across this.

The last issue is that the program will not start in some Linux distro, but this is not a major issue since
the program was intended for Windows operating systems, and Ubuntu.

At this stage, the program is existing, it is not perfect because of these issues, and probably many
others a used may encounter in everyday use, but these are minor issues, so we can validate the
program.