Walkthrogh: Very informal type of review or testing method. Done by peers, so its called peer review.

Inspection: very technical type of review or testing method, done by the highly technically sound people.

Exploratory testing: means testing an application without a test plan and test script. In exploring testing test explore the application on the basis on his knowledge. The tester has no knowledge about the application previously. He explores the application like an end user and try to use it. While using the application his main motive is to find the bugs which are in the application.

Specification-driven testing: means to test the functionality of software according to the user requirements. In this, tester inputs multiple data and monitors the outputs from, the test object. In this testing tester evaluate the showstopper bugs which break the major functionality of the application. This type of testing requires test plan and test.

Regression Testing: When changes in the code of the software are made to fix the previous bug. Then testing needs to be perform to ensure that it will not generate a new bug in the application and it works as specified and that it has not negatively impacted any functionality that it offered previously. Regression Testing is important because of following reason:

- That the application works even after the alteration in the code were made.

- The original functionality continues to work as specified even after doing changes in the software application.

- The alteration to the software application has not introduced any new bugs.

Automated testing cannot replace manual testing because of following reason:

- Automated testing cannot replace the analytical skills required to conduct testing. It can only enhance or supplement manual testing,

- Through manual testing, information can be gathered about the application, and real-time decisions can be made about how to enhance a test that would be too difficult to program into an automated script.

- We need a manual tester to analyze and maintain the automated scripts after they can run.

Bottom Up Approach:

The bottom up approach testing approach is carried out with the help of the test driver. The test driver calls a component to be tested.

The modules in the lower level of call hierarchy are tested independently. Then the next level modules are tested that call previously tested modules. This is done repeatedly until all the modules are included in the testing.

Bottom up testing stops when the top module in the call hierarchy is tested with all lower call hierarchy modules.

Top Down Approach:

The top down approach is carried out with the help of the test stub. Test stub are the dummy programs. The Stub is called from the software component to be tested.

Tests top layer of controlling subsystem first. Then combine modules that are called by the tested modules and test resulted collection of modules.

Do this until all the modules are combined and tested.

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.