PHILBY

Testing for Quality Systems

Why you need PHILBY

The Year 2000 problem requires retesting of all critical applications. In a typical TP Application Implementation, system testing accounts for 35% - 40% of the software development expenditure. With good management, sound methodologies and the right software, this cost can easily be halved, and really should not exceed 15%.

Furthermore, these methods should result in a higher quality system with fewer errors.

PHILBY is a Computer Aided Software Testing (CAST) tool which makes a major contribution to this enormous saving. It is a 'Capture and Playback' tool whose purpose is to document the system test and to automate re-runs as well as regression testing.

What is PHILBY?

PHILBY analyses the activity on the TPMS service and produces complete and exact documentation of the man machine interface.

It produces:

• A clearly printed report showing, in screen image format, all transactions which have taken place,
• A file of the input which can be used to replicate automatically the transactions from the same start point.

The results of the test are in an easily readable report, so that there is no need for the person at the terminal to take notes or local prints. Thus the test can be performed quickly and efficiently.

How you use PHILBY

The tester can use copies of the test report as evidence for the programmer, the analyst or the user. Therefore any problems are clearly documented and understood by all concerned.

The keyboard input from the first interactive run of any test is captured into a file. When the test is repeated the file is applied as input from simulated terminals. So the re-test is very fast and economical.

The reported results from re-tests can be matched automatically against a previous report and differences identified.

For live systems, the Audit Department or Technical Support services can select clear, exact and complete reports of the activity on the service, so that they can analyse user problems.

The benefits of using PHILBY

PHILBY can be used throughout the development project.

At the prototyping stage it is used to document the user interface and provide the user with a clear and simple way of commenting on the interpretation of the requirement.

The Production and Documentation of Test Scripts are an integral part of the development process.

With PHILBY each stage of testing is enormously simplified and streamlined:

Basic system testing is easier

because of the quality of the reports produced, and because PHILBY eliminates re-keying of tests.

Test data generation is simple

because the Terminal Simulator input file is simply edited with PHILBY utilities.

Acceptance testing and Regression testing is quick and easy

because PHILBY can be used to produce and re-run a 'standard' test pack of a TP session after new versions of software have been installed.

Acceptance testing and Volume testing are more reliable

and indeed, many tests can be performed which are not feasible without PHILBY.

Volume testing is more intensive

and can be much more flexible, and can be performed with minimal manpower.

Live Service Analysis is possible

because an understandable picture of exactly what has taken place can be produced.

PHILBY is also used in the production of support material for training as well as in the production of manuals.