QA Testing Questions

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 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.

1) List down usecases (taken from business cases) from function specs. For each use case write a test case and categorize them into sanity tests, functionality, GUI, performance etc. Then for each test case, write its workflow. 

2) For a GUI application - make a list of all GUI controls. For each control start writing test cases for testing of the control UI, functionality (impact on the whole application), negative testing (for incorrect inputs), performance etc. 

Generally,test plan document is prepared by TL&QM.

Entry &Exit criteria is part of test plan document

Entry criteria is 

- Testing environment established

- Test cases prepared

- Build received from development team

Exit criteria is

- All modules are covered or not

- All test cases are completely executed or not

- All bugs resolved or not

Requirements tracing, a process of documenting the links between the requirements and the work products developed to implement and verify those requirements. Requirement Traceability Matrix (RTM) is a document which records the mapping between the high-level requirements and the test cases in the form of a table. The RTM captures all requirements and their traceability in a single document delivered at the conclusion of the life cycle. 

That’s how it ensures that the Test Plan covers all the requirements and links to their latest version.

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.

1) List down usecases (taken from business cases) from function specs. For each use case write a test case and categorize them into sanity tests, functionality, GUI, performance etc. Then for each test case, write its workflow. 

2) For a GUI application - make a list of all GUI controls. For each control start writing test cases for testing of the control UI, functionality (impact on the whole application), negative testing (for incorrect inputs), performance etc.  

Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.

Quality Control (QC): Concern with the quality of the product. QC finds the defects and suggests improvements. The process set by QA is implemented by QC. The QC is the responsibility of the tester.

Software Testing: is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed.