9
Q:

main()

{

float me = 1.1;

double you = 1.1;

if(me==you)

printf("yes");

else

printf("No");

}

A) Yes B) No
C) Both D) Compilation error

Answer:   B) 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.

Q:

Unreachable code would best be found using

A) code inspections B) a static analysis tool
C) code reviews D) a test management tool
 
Answer & Explanation Answer: C) 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.

Report Error

View Answer Report Error Discuss

14 15398
Q:

Impact analysis helps to decide

A) How many more test cases need to written. B) How much regression testing should be done.
C) Different Tools to perform Regression Testing D) Exit Criteria
 
Answer & Explanation Answer: B) How much regression testing should be done.

Explanation:

Impact Analysis is used in software testing to define all the risks associated with any kind of changes in a product being tested.

Impact Analysis is nothing but analyzing the impact of changes in the deployed product or application. It gives the information about the areas of the system that may be affected due to the change in the particular section or features of the application.

 

Why Impact Analysis is done :


1. It is done to understand the possible outcome of implementing the change. Inducing too much functionality into a product can reduce the overall performance of the product.

2. To identify all the files, documents and models that might have to be modified if team decides to implement the change in product

3. To estimate the effort needed behind implementing the change

4. To identify the task required to implement the change

5. It will list the dependencies on a specific element

 

The impact is analyzed on Requirements, Design & Architecture, impact on Test and impact on schedule.

Report Error

View Answer Report Error Discuss

0 7950
Q:

Which of the following is not a static testing technique?

A) Inspections B) Data flow analysis
C) Error guessing D) Walkthrough
 
Answer & Explanation Answer: C) Error guessing

Explanation:

Static Testing, a software testing technique in which the software is tested without executing the code. This Techniques provide a powerful way to improve the quality and productivity of software development by assisting engineers to recognize and fix their own defects early in the software development process.

 

It has two parts as listed below:

Review - Typically used to find and eliminate errors or ambiguities in documents such as requirements, design, test cases, etc.

Static analysis - The code written by developers are analysed (usually by tools) for structural defects that may lead to defects.

 

In this software is tested without executing the code by doing Review, Walk Through, Inspection or Analysis etc.

 

Hence, Error guessing is not a static software testing technique.

Report Error

View Answer Report Error Discuss

6 17601
Q:

Which of the following is not part of performance testing?

A) simulating many users B) measuring response times
C) generating many transactions D) recovery testing
 
Answer & Explanation Answer: D) 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.

Report Error

View Answer Report Error Discuss

10 23906
Q:

Configuration management is not concerned with

A) maintaining versions of software B) controlling documentation changes
C) controlling changes to the source code D) choice of hardware configuration for an application
 
Answer & Explanation Answer: D) choice of hardware configuration for an application

Explanation:

Configuration management is not concerned with the choice of the hardware configuration for an application.

 

Configuration management is concerned with the development of procedures and standards for cost-effective managing and controlling charges in an evolving s/w system.

It includes

1)software versions maintenance

2)controlling changes in documentation

3)controlling changes to the source code

4) management activities

Report Error

View Answer Report Error Discuss

1 3044
Q:

Defect Management Process does not include

A) Deliverable base-lining B) Management reporting
C) Defect prevention D) None of above
 
Answer & Explanation Answer: A) Deliverable base-lining

Explanation:
Report Error

View Answer Report Error Discuss

Filed Under: Software Testing
Job Role: Analyst , IT Trainer

8 11977
Q:

Which is the simplest file structure?

A) Sequential B) Indexed
C) Random D) None
 
Answer & Explanation Answer: A) Sequential

Explanation:

Sequential is the simplest file structure

Report Error

View Answer Report Error Discuss

Filed Under: Software Testing

6 11096
Q:

What is a software project test plan?

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)

Report Error

View answer Workspace Report Error Discuss

Subject: Software Testing

3 2139