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 »

Static testing is checking the application without actually running the application whereas dynamic testing checks the application by running it.

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 »

I have used following 4 types of Methodologies:

1. Boundary value analysis

2. Equivalence partitioning

3. Error guessing

4. Cause effect graphing

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 »