Software Testing - which of the following is not a coding defect?

GeekInterview.com > Interview Questions > Testing > Software Testing

Go To First | Previous Question | Next Question

Software Testing | Question 230 of 266

which of the following is not a coding defect?

which of the following is not a coding defect?
1)Test harness defect 2)Data flow defect 3)Initialisation defect 4)Algorithmic defect

Total Answers and Comments: 2

Last Update: February 19, 2008 Asked by: ranu agrawal

Sponsored Links

Best Rated Answer

—

Submitted by: Cryptic_sumon

Test Harness and Test Driver defect is not a coding defect.
Test harnesses allow for the automation of tests. They can call functions with supplied parameters and print out and compare the results to the desired value. The test harness is a hook to the developed code, which can be tested using an automation framework.

Test Driver: In "Unti Testing" and “Integration Testing” if program is not ready for doing the testing So during that time we are using drivers and stubs. sometime its neccesary to create Fake codes(stubs) that replaced called modules as like dummy programs. Upto completing the development we are using these drivers and stubs.

Above answer was rated as good by the following members:
vk1978, hirenmistry

January 07, 2008 04:17:00

maveric systems sarathi

Member Since: January 2008 Contribution: 4

RE: which of the following is not a coding defect?

Test Harness Defect

Is this answer useful? Yes | No

February 19, 2008 06:17:12

Cryptic_sumon

Member Since: February 2008 Contribution: 3

RE: which of the following is not a coding defect?

Test Harness and Test Driver defect is not a coding defect.
Test harnesses allow for the automation of tests. They can call functions with supplied parameters and print out and compare the results to the desired value. The test harness is a hook to the developed code which can be tested using an automation framework.

Test Driver: In "Unti Testing" and “Integration Testing” if program is not ready for doing the testing So during that time we are using drivers and stubs. sometime its neccesary to create Fake codes(stubs) that replaced called modules as like dummy programs. Upto completing the development we are using these drivers and stubs.

Is this answer useful? Yes | No

2 0

Overall Rating: +2

SQA Software and Tools

SQA Software and Tools In quality assurance it is always important to get all the help we could get In other industries developers could easily check the products manually and discard those that do not meet the standard The length and the width of the product are checked to maintain standardization

What is Software Quality Assurance?

What is Software Quality Assurance Business software is never built overnight It takes a lot of planning consultation and testing to be able to come up with an initial version of the application If a business hurries up the development of a certain application they would end up spending more in addr

Software Quality Assurance Training

Software Quality Assurance Training In this training session you will learn about SQA Software Quality Assurance SQA Principles SQA Planning SQA Project Metrics SQA Software and Tools SQA Analysis SQA Approaches and Methodologies SQA Planning and Requirements SQA Lifecycle Standards SQA Implementati

EDI and Software Applications

EDI and Software Applications EDI and JAVA Java is a programming language originally developed by Sun Microsystems and launched in 1995 While generally compiled to byte code direct hardware execution of byte code by a Java processor is also possible Currently almost all of Java’ s software

Which Supply Chain Management Software is Right for your Business?

Which Supply Chain Management Software is Right for your Business If you’ re a Business Leader Supply Chain Manager or Logistics Executive you’ re probably all too aware of the fact that there’ s an abundance of Supply Chain Management SCM software products available on

Three Tier Software Architectures

Three Tier Software Architectures In this tutorial you will learn about three tire software architectures purpose history technical details three tier architecture usage considerations maturity costs and alternatives mosgoogle center The concept of Three Tier and multi tier architectures originated

Software Maintenance

Management Maintenance vs. SDLC Maintenance The best way we can define maintenance in SDLC is to differentiate the developers meaning of maintenance against management’s idea of SDLC. In management, maintenance will always be a reaction to a problem. The only time management will become f

Software Acceptance and Installation

In this article, we will take a look at step by step process of accepting and installation of software. While systems design, planning and coding are important, this phase of SDLC will determine if the program created will actually work and is beneficial for the company or not.  Taking cu

Testing and Integration

Once the software is complete, it will go though rigorous testing before its actual integration.  In this article we will take a look at different types of software testing and also different types of integration. With the diversity of business setting and software development models, it al

Software Requirements Secrets

Secrets of Successful Software Requirements Although most companies do some form of requirements, there is often a lack of understanding as to exactly why the requirements need to be created and the level of detail that should be included in the requirements. Software is always created to solve a

Related Categories

—

User Name		Remember Me?
Password

Question Bank