Software Testing Tools

Test Life Cycle

2009-11-13T23:44:00.001+05:30

Identify Test Candidates

Test Plan

Design Test Cases

Execute Tests

Evaluate Results

Document Test Results

Casual Analysis/ Preparation of Validation Reports

Regression Testing / Follow up on reported bugs.

Test Plan and Test Specification

2009-11-12T23:13:00.002+05:30

Test Plan :

A Test Plan is a detailed project plan for testing, layering the possibility of testing, the tactics to be used, the tasks to be performed, resources, schedules, risks, and dependencies. A Test Plan is developed earlier to the implementation of a project to provide a well defined and understood project road map.

Test Specification :

A Test Specification defines exactly what tests will be performed and what their scope and objectives will be. A Test Specification is produced as the first step in implementing a Test Plan, prior to the onset of manual testing and/or automated test suite development. It provides a repeatable, wide-ranging definition of a testing operation

Purpose Of Security testing

2009-11-09T00:39:00.001+05:30

If your site wants firewalls, encryption, user authentication, economic dealings, or access to databases with sensitive data, you may need to test these and also test your site's overall safeguard against illegal internal or external access.

Purpose Of Usability testing

2009-11-09T00:35:00.001+05:30

Usability means that systems are easy and fast to learn, capable to use, easy to remember, cause no operating errors and offer a high grade of satisfaction for the user. Usability means bringing the usage viewpoint into focus, the side towards the user.

Purpose of Stress testing

2009-11-09T00:31:00.000+05:30

This refers to testing system functionality while the system is under extraordinarily heavy or peak load; it's similar to the validation testing but is carried out in a "high-stress" environment. This requires that you make some calculation about expected load levels of your Web site.

Purpose Of Volume Testing

2009-11-09T00:21:00.003+05:30

The purpose of Volume Testing is to find weak point in the system with respect to its managing of large amounts of data during short time periods. For example, this kind of testing ensures that the system will process data across physical and logical boundaries such as across servers and across disk partitions on one server.

System Testing

2009-11-09T00:12:00.000+05:30

• A system is the big component
• System testing is designed at revealing bugs that cannot be attributed to a component as such, to irregularity between components or planned contacts between components
• Concern: issues, behaviors that can only be exposed by testing the entire integrated system
(e.g., performance, security, recovery).

Alpha and Beta Testing

2009-11-09T00:06:00.000+05:30

Alpha testing:

Testing of an application when development is approaching to achievement minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.

Beta testing:

Testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers

Integration Testing

2009-11-08T23:55:00.001+05:30

Integration is a systematic approach to build the complete software structure specified in the design from unit-tested modules or components. There are two ways integration performed. It is called Pre-test and Pro-test.

1. Pre-test: the testing performed in Module development area is called Pre-test. The Pre-test is required only if the development is done in module development area.

2. Pro-test: The Integration testing performed in baseline is called pro-test. The development of a release will be scheduled such that the customer can break down into smaller internal releases.

Functional Testing

2009-11-08T23:45:00.001+05:30

Functional Testing

1. Study SRS (Software Requirement Study)
2. Identify Unit Functions
3. For each unit function:

• Take each input function
• Identify Equivalence class
• Form Test cases
• Form Test cases for boundary values
• From Test cases for Error Guessing
4. Form Unit function v/s Test cases, Cross Reference Matrix
5. Find the coverage

Testing Techniques

2009-11-08T23:34:00.000+05:30

Black Box Testing
White Box Testing
Regression Testing
These principles & techniques can be applied to any type of testing.

Black Box Testing :

Testing of a function without knowing internal structure of the program.

White Box Testing :

Testing of a function with knowing internal structure of the program.

Regression Testing :

To ensure that the code changes have not had an undesirable affect to the other modules or on existing functions.

Purpose of testing

2009-11-08T23:26:00.002+05:30

Testing :

A review of the behavior of a program by executing on sample data sets.
Testing comprises of set of activities to detect defects in a produced material.

To discover & correct defects
To detect defects early & to reduce cost of defect fixing
To avoid user detecting problems
To make sure that product works as users expected it to.

To discover and correct defects.

• To detect defects early and to reduce cost of defect fixing.
• To guarantee that product works as user expected it to.
• To avoid user detecting problems.

Questions On Testing tools

2009-11-08T23:14:00.004+05:30

1. Write and explain any one Sdlc which u know?
2. Describe Testing process which u follow?
3. Differentiate between Static and Dynamic testing?
4. Define Types of Testing - unit, integration and system?
5. Define Testing standards ?
6. Difference between Black Box and White box testing?
7. Difference between Top Down and Bottom Up testing?
8. Describe why We need automation?
9. Differentiate between Validation and verification?
-----------------------&-------------------------
1. What is the tester's role in software development?
2. What does the tester do in white box testing?
3. How does the tester perform black box testing?
4. What does the tester do in automated testing?
5. What are the benefits of automated testing over white box and black box testing?
6. Name three types of tests that should be automated.
7. Name three types of tests that should NOT be automated.
8. What are the four steps of automated testing?
9. What is an IDE?
10. What are the three aspects of GUI software to test for with WinRunner?
11. What are the two ways to create test scripts?
12. What are the four steps to record a test script?
13. Why position WinRunner and the AUT so they do not overlap?
14. What icon is used in WinRunner to get an explanation of the syntax of TSL?
15. What are the two recording modes in WinRunner?
16. Which recording mode is suggested for most situations?
17. Name three reasons why the tester may choose to record in Context Sensitive mode.
18. Name three reasons why the tester may choose to record in Analog mode.
19. When we are recording in WinRunner and interact with the AUT, what does WinRunner do?
20. How does the tester run or playback a test script?
21. Name two ways the AUT can be changed when the tester interacts with it during recording.

22. What are initial conditions?
23. What are end conditions?
24. Why are initial and end conditions necessary?
25. If a test script instructs WinRunner to open an application to test it, what end conditions might be good?
26. If the tester names a test test1, what will be the name of the directory for this test?
27. Why is a lock file created?
28. What is contained in a chklist subdirectory?

29. If the AUT does not respond quickly enough for an action to be executed in the test script and WinRunner moves to the next action, why would this be a problem?
30. Name three actions that may take the AUT more time to perform that would require synchronization.
31. What is a synchronization point?
32. Name four types of synchronization.
33. The AUT we tested did not have a synchronization problem, how did we create the problem?
34. How many milliseconds are in one second?