Which of the following is not a static testing technique?

Correct Answer: Deliverable base-lining

Correct Answer: A test plan is the master document that contains all details pertaining to testing of the application Its contents include: Testing scope - what is included and what is not included in the testing of the current project Assumptions - what are the assumptions that are made for this project Milestones - major dates like when testing is going to begin, when it is planned to end, what is the trace review date, what is the production date etc Resources - the resources working on this project along with their contact details Defect tracking mechanism - what defect tracking tool will be used, what is the SLA for fixing Critical to Low level IRs etc Test management procedures - who will be notified when there is a critical IR, what reports will be sent daily, if status calls will be held daily or weekly, where will it be held, who is required to join etc Work allocation - resource distribution if more projects are being tested Entry and exit criterion - when can a project be accepted for testing (eg only when smoke testing passes) and when can a project be termed as testing complete (eg when all testcases are executed and all high level bugs are fixed)

Correct Answer: a) Testing and Debugging Testing is process of verifying if the application matches requirements and reporting bugs; Testing is usually done by an independent testing team while debugging is a process of finding and fixing bugs with the intention of reducing bugs; Debugging is usually done by the programmer b) Two tier and Three tier architecture In a two tier architecture there is a data server and a client application Client application directly accesses the server data In a three tier architecture there is a data server, a client application and a server application Client application calls the server application which in turn fetches data from the data server and returns back to client application c) Alpha testing and Beta testing 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 d) Static testing and dynamic testing Static testing is checking the application without actually running the application whereas dynamic testing checks the application by running it

Correct Answer: The biggest concern is the cost incurred for test automation Also, often s/w test automation requires skilled personnel and authentic test automation tools Purchasing license of such tools is a costly affair Also the time required for test automation is more Automation often requires recording the sequence of operations you need to perform in order to execute a particular test case and comparing the final o/p with the expected o/p Functions/macros need also be written sometimes for some test cases All this could be a time consuming job

Correct Answer: Missing Statements

Explanation:

Statement coverage is a white box test design technique which involves execution of all the executable statements in the source code at least once. It is used to calculate and measure the number of statements in the source code which can be executed given the requirements.

Correct Answer: Usability testing

Correct Answer: The parameters of Quality Cost are: Speed Accuracy Efficiency Performance Customer Satisfaction

Correct Answer: recovery testing

Explanation:

In software engineering, performance testing is in general, a testing practice performed to determine how a system performs in terms of responsiveness and stability under a particular workload.

Correct Answer: BackTracking

Explanation:

BackTracking is used for solving N-Queens problem

Correct Answer: Testing is a process used for revealing defects in s/w and for establishing that the s/w has attained a specific degree of quality The s/w testing group?s main objective is to ensure that the s/w is doing what it is supposed to do as well as the s/w is not doing what it is not supposed to do With this objective, it is clear that it is necessary to have a separate group for testing the s/w other than the group which developed it Also, bugs in the s/w can cause severe monetary as well as other loss to the organization So it is important to allocate some budget for the testing group