WinRunner might fail to recognize an object in a GUI in following cases:

- If it is not a standard windows object

- If the browser used is not compatible with the version of WinRunner in use.

GUI Map Editor may not be able to learn the objects in these cases.

Learn more »

Checkpoints help to compare the behavior of current application to its previous version. There are four types of checkpoints in Winrunner:

a.) Text – reads and displays the text contents of GUI objects and bit map and in bitmaps

b.) Bitmap – compares application window or area snapshots to earlier versions of the same window or area

c.) GUI – validates GUI object information (i.e. whether a button is enabled, an item is selected in a list, etc.)

d.) Database – verifies the contents and size of a set of results (based on a database query)

Learn more »

1. Bad requirements - these requirements are unclear, incomplete, too general, or not testable. They cause problems.

2. Unrealistic schedule - Expecting too much result in too less time.

3. Inadequate testing - lack of testing causes problem as no one knows if the system will behave as expected.

4. Adding new features - after development; quite common.

5.Poor communication within the team or with the customer.

Learn more »

- Drivers and stubs are a part of incremental testing.

- The two approaches used in incremental testing are: the top down and the bottom up methods.

- Drivers are used for the bottom up approach.                            

- Drivers are the modules that run the components that are being tested.

- A stub is used for the top down approach.

- It is a replacement of sorts for a component which is used to test a component that it calls.

Learn more »

Inspection is deserving method with careful consideration of an organization, which concerns about the quality of the product. The process is being done by the quality control department.

Inspection is a disciplined practice for correcting defects in software artifacts.

A walk through is an evaluation process which is an informal meeting, which does not require preparation.

The product is described by the produced and queries for the comments of participants. The results are the information to the participants about the product instead of correcting it.

Learn more »

While a test plan is being created, risks involved in testing the product are to be taken into consideration along with possibility of their occurrence and the damage they may cause along with solutions; if any. Detailed study of this is called as Risk Analysis.

Some of the risks could be:

New Hardware

New Technology

New Automation Tool

Sequence of code delivery

Availability of application test resources

Identify and describe the risk magnitude indicators: High, Medium and Low

High magnitude means the effect of the risk would be very high and non-tolerable. Company may face severe loss and its reputation is at risk. Must be tested.

Medium: tolerable but not desirable. Company may suffer financially but there is limited liability or loss of reputation. Should be tested.

Low: tolerable. Little or no external exposure. Little or no financial loss. Company’s reputation unaffected. Might be tested.

Three perspectives of Risk Assessment: Effect, Cause and Likelihood.

To assess risk by Effect, identify a condition, event or action and try to determine its impact.

To asses risk by Cause is opposite of by Effect. Begin by stating an undesirable event or condition and identify the set of events that could have permitted the condition to exist.

To asses risk by Likelihood is to determine the probability that a requirement will not be satisfied.

Learn more »

Pilot testing involves having a group of end users try the system prior to its full deployment in order to give feedback on its performance.

Beta testing is testing of the product in the user environment.

From the definitions, its is evident that beta testing comes at last in development cycle; whereas pilot testing takes place before deployment of the system. Also, beta testing takes place in real time user environment and pilot testing in development environment. A selected group of users do pilot testing whereas beta testing is carried by all users.

Learn more »

severity describes seriousness of the defect with respect to functionality where priority describes importance of defect to solve with respect to customer.
Example:

Suppose we identify two bugs

-The client logo is not appearing on the web site but the site is working fine... in this case the severity is low but the priority is high because from company's reputation it is most imp to resolve. After all the reputation wins more clients and projects and hence increases revinue

Learn more »

Automation is chosen when

-A same set of tests need to be repeated again and again

-When a single test needs to be repeated for a large number of data

-When stable modules needs to be regressed frequently.

Learn more »

Testing is process of verifying if the application matches requirements and reporting bugs; Testing is usually done by an independent testing team while debugging is a process of finding and fixing bugs with the intention of reducing bugs; Debugging is usually done by the programmer.

Learn more »

A bug leakage results when a bug is detected which should have been detected in earlier builds/versions of the application.

A defect which exists during testing yet unfound by the tester which is eventually found by the tester/end-user is also called bug leakage.

A bug release is when a particular version of s/w is released with a set of known bug(s)/defect(s). These bugs are usually low severity and/or low priority bugs. It is done when the company can afford the existence of bug in the released s/w rather than the time/cost for fixing it in that particular version. These bugs are usually mentioned in the Release Notes.

Learn more »

Integration testing is done at module level when various modules are integrated with each other to form a system or sub-system. Its main purpose is to ensure that interfaces between various modules are working properly; i.e. modules which are working individually are also working correctly together.

System testing is done on a complete, integrated system to evaluate the system’s compliance with its specified requirements. It validates that the system meets its functional and non-functional requirements.

From these definitions, it is clear that the purpose of Integration and purpose of System Testing are different. Therefore, Integration test cases focus more on the interfaces between modules (interface integrity) - the data transfer and their interaction with each other. System test cases focus on testing the product as a whole; i.e. whether the functional, non-functional requirements of the System are met or not. Since System Testing is the final phase before delivery of the product, System test cases should pinpoint configuration related errors along with testing for performance, security, reliability etc.

Learn more »

Glass Box (or white box) testing is the process of giving i/p to the system and checking how the system processes i/p to generate o/p

Black Box testing is the process of giving i/p to the system and checking if the system is giving correct o/p without bothering how the o/p is generated.

As we can see from the definitions, the role of black box testing is to ensure that the o/p generated is correct. And role of white box testing is to ensure that methods used to generate the o/p are correct.

Learn more »