Verification: Verification is a process to ensure that the software that is made, matches the original design. In other words, it checks whether the software is made according to the criteria and specification described in the requirement document. It is to check whether you built the product right as per design. It is a low level checking. (It is done in walk-through meetings generally). It checked whether it is made accordingly to the design..

Validation: Validation is a process to check whether the product design fits the client’s need. It checks whether you built the right thing. It checks whether it is designed properly.

The QA testing process that was followed in my last company where I worked was like this: First of all the Business Requirement Document was prepared as per the client’s requirement (with the muck-up screen shots). Then on the basis of the requirement document, Test Strategy, Test Plans and Test Cases were written in sequential order. Once the Build is made and deployed to the different testing environments where different types of testing were performed to check whether there are any defects.

Basically Load, Stress and Performance Testing are the same. However, Load testing is the test to check the users’ response time of number of users of any one scenario of the application whereas Performance Testing is the test to check the user response time for multiple scenario of the same application.

Use case is nothing but the functional specification document in which all the customer requirements are documented.

Test case is a document which tells wat to test, steps to test and expected and actual results.

The Bug Tracking System role is discussed below:

- Testers and developers can know the status of the bug at every stage.

- Changes to the Status will be available to all team members.

- Developers and Testers can easily interact with bugs.

- Repetition of bugs will be avoided.

- Easy to distribute the bug among the developer.

- It will act as a centralized one for defects.

The differences in responsibilities are listed below:

- QA is concern for Process Quality and Programmers are concern for Product Quality.

- QA ensure that the processes used for developing the product of high quality where as programmers used these processes so that end product is of good quality.

- Processes are decided by QA. Programmers are supposed to follow the processes so that they can produce a good quality product.

- Any issue found during execution of process by the programmers is communicated to the QA so that they can improve the process.

The main attributes are discussed below:

Maintainability: For each new release need to update the test automation suites.

Reliability: Accuracy and repeatability of the test automation.

Flexibility: Ease of working with all the different kinds of automation test ware. 

Efficiency: Total cost related to the effort needed for the automation.

Portability: Ability of the automated test to run on different environments.

Robustness: Effectiveness of automation on an unstable or rapidly changing system. 

Usability: Extent to which automation can be used by different types of user.

For web application we perform following time of test:

1. Functionality Testing.

2. Usability Testing.

3. Navigation Testing.

4. Configuration and Compatibility testing.

5. Reliability and Availability Testing.

6. Performance Testing.

7. Load and Stress Testing.

8. Security Testing