Correct Answer: code reviews

Explanation:

Code review is a software quality assurance activity in which one or several humans check a program mainly by viewing and reading parts of its source code, and they do so after implementation or as an interruption of implementation.

Correct Answer: A bug leakage results when a bug is detected which should have been detected in earlier builds/versions of the application A defect which exists during testing yet unfound by the tester which is eventually found by the tester/end-user is also called bug leakage A bug release is when a particular version of s/w is released with a set of known bug(s)/defect(s) These bugs are usually low severity and/or low priority bugs It is done when the company can afford the existence of bug in the released s/w rather than the time/cost for fixing it in that particular version These bugs are usually mentioned in the Release Notes

Correct Answer: No

Explanation:

For floating point numbers (float, double, long double) the values cannot be predicted exactly. Depending on the number of bytes, the precession with of the value represented varies. Float takes 4 bytes and long double takes 10 bytes. So float stores 0.9 with less precision than long double.

Correct Answer: Sequential

Explanation:

Sequential is the simplest file structure

Correct Answer: Complete Binary Tree

Explanation:

Full binary tree loses its nature when operations of insertions and deletions are done. For incomplete binary trees, extra storage is required and overhead of NULL node checking takes place. So complete binary tree is the better one since the property of complete binary tree is maintained even after operations like additions and deletions are done on it.

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: 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: 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: 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: Deliverable base-lining