Explain Test case, Test Script, Test Environment, Test Procedure and Test Log?

There are several terms related to software testing like test cases, test scripts, test environment, test procedures, test logs and the list goes on. So many terms make the whole concept of testing go topsy turvy inside our brains. 

What is a Test Case?

- A test case can be thought of as a case or a set of conditions that when executed or implemented will determine whether the aspect of the software system or application under the test is working properly or not. 

- Usually formal test cases are used for any type of software testing. 

- One positive test case and one negative test case should be used for testing a requirement of the software system. 

- Informal test cases are best suited for the applications having informal requirements. 

What is a Test Script?

- A test script as the term suggests is instructional script that is implemented on the software system or application to be tested. 

- This is done so that the system functionality are tested as expected. 

- Test scripts can be executed either manually or through automated process. 

What is a Test Environment?

- For a testing to be carried out, the tester needs to set up the right environment for the test i.e., the right set up of the hardware and software requirements using which the software testing is to be performed. 

- Two types of set up namely physical set up (hardware requirements) and logical set up (server operating system, data base server, client operating system, browser, front end running environment and IIS etc.) together constitute a proper testing environment. 

- While setting up the perfect test environment, the tester needs to keep in mind, all the requirements and specifications of the software system or application. 

What is a Test Procedure?

- Like a normal procedure for a task tells us what all steps to follow and how to follow to successfully complete the task, the test procedure also does the same.

- It lays out all the formal specifications of the test cases to be executed up on the software system. - The executability of a test procedure is one of its fundamental properties.

- A good test procedure is always executable. 

- The test procedure is implemented on its target via a process called “verifier” and a report is obtained regarding the passing status of all the executed test cases.

- Other characteristics of a good test procedure are:

1. Completeness

2. Self containment

3. Self validation and

4. Automatic execution

- Test procedures are used in every phase of the software testing right form the first phase to the last phase of regression testing.

- A specially coded language called “TPL (test procedure language)”  has been designed for writing the  test procedures. 

- The test procedure like test cases is also documented and all the instructions for the set up and execution of the test procedure as well the evaluation of its outcomes is stated in this documentation. 

- The documentation of a test procedure can be thought of as a set of associated instructions which are used in the identification of the actions in a particular sequence during a test case execution. 

What is a Test Log?

- It is defined as a record of the passing status (pass or fail) of all the test cases executed during a particular software testing. 

What is meant by peer review in software testing?

In the process of software development at every stage the software system or application under development has to be reviewed be it before its completion or after its completion. Many techniques have been designed to carry out an effective review of the software systems or applications.

What is Peer Review in Software Testing?

- Peer review is one such technique employed in software testing.

- Peer review is a type of software review technique which involves the examination of the software product or code or documentation by its author or developer as well as by his/ her colleagues for the evaluation of the quality of the product and its technical content.

- The number of peers for carrying out a peer review may vary from one to any number the author wishes.

- The process of peer review is aimed at providing an engineering practice which is well disciplined for the detection as well as the correction of the bugs and errors in the software product.

- It is also aimed at the prevention of the defects from leaking in to the operational field.

- These aims of the peer review have been defined on the basis of the CMM or capability maturity model.

- Peer reviews form an essential part of the software development cycle and proves to be very helpful in the detection of the bugs in the early stages of the software development.

- A requirements problem as identified by the peer review during the requirements testing is a lot easier and cheaper to rectify than what it would have been in the development stages of the software testing and architecture.

Now the question comes “how the peer review is different from the other kinds of reviews?”

- Peer reviews are somewhat different from their counterpart of management reviews.

- The management reviews are performed by the management representatives rather than by colleagues as in peer review.

- The management reviews are focussed up on the control and management purposes and not on the technical evaluation like the peer review.

- Peer reviews are also a way apart from the software audit reviews in the way that the software audit reviews are carried out by the personnel external for the evaluation of the level of compliance with the standards, specifications and agreements etc.

- Several formal and informal approaches have been designed for carrying out the peer reviews.

- Buddy checking is one informal approach.

- Some formal approaches are:

1. Technical peer reviews
2. Walk throughs and
3. Software inspections.

- The roles, processes and structures for the above mentioned formal processes are governed by the IEEE standards.

- Management representatives are chosen to carry out a peer review only very rarely when specific technical expertise is required or when the documentation to be reviewed is of management level.

- The third formal approach i.e., software inspection involves the assignment of specific roles to the participants, quantification of the stages by defining the entry and exit criteria, and capturing of the software metrics.

- The peer review carried out for the open sources is commonly known as open source review.

Advantages of Peer Reviews

- Peer reviews have always been observed as a powerful methodology for a great improvement in the software quality.

- A peer review can be performed in many forms like an inspection, team review, pair programming, peer desk check or pass around etc.

Which approach is to be followed is decided on the basis of the rigor, cost, spectrum of formality and of course effectiveness!

The cheapest review method should be selected that is more effective in reducing the project associated risks. But, the inspections are always the best approach and are fit for both high level and low level risk projects.