Automation is the integration of testing tools into the test environment in such a manner that the test execution, logging, and comparison of results are done with little human intervention. A testing tool is a software application which helps automate the testing process. But the testing tool is not the complete answer for automation. One of the huge mistakes done in testing automation is automating the wrong things during development. Many testers learn the hard way that everything cannot be automated. The best components to automate are repetitive tasks. So some companies first start with manual testing and then see which tests are the most repetitive ones and only those are then automated.

Learn more »

BVT is boundary value testing.
The test data for this testing will always be : 
min-1, min, max, max+1.

It is done by testers.

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 »

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 »

Alpha testing is conducting acceptance testing in the environment where the application was developed. It is done by the customer. Beta testing is conducting acceptance testing is the customer environment. It is done by the group of customers or users who will actually be using it.

Learn more »