Difference between dynamic white box testing and debugging.

-

 Solution:-


Dynamic white box testing

Debugging

1. The goal of dynamic white box testing is to find bugs. 

1. The goal of debugging is to fix bugs.

2. It include information about what line of code look suspicious.

 2. The programmer who does debugging picks process up from there and determines exactly what is causing the bug and attempts to fix it.

3. Dynamic white –box testing  is a general investigation process of checking. 

3. Debugging is done once a problem has been identified and is reproducible

4. Dynamic white-box testing is testing effort.

4. Debugging is defect addressing effort.

5. This testing is done on architectural basis

5. Debugging is done on thread basis.

Comments

Post a Comment

Popular posts from this blog

What is the process and project matrics? Explain 3 P's in software engineering.

-
Solution:-  a) Process Metrics These are the metrics pertaining to the Process Quality. They measure efficiency and effectiveness of various processes. b) Project Metrics These are the metrics pertaining to the Project Quality. They measure defects, cost, schedule, productivity and estimation of various project resources and deliverables.found in acceptance)/ total no of testing defects) x 100 THE THREE Ps:- The People • People factor is very much important in the process of software development. • There are following areas for software people like, recruiting, selection performance management, training, compensation, career development, organization and work design, and team/culture development. • Organizations achieve high levels of maturity in the people management area. The Product • Before a project can be planned, product objectives and scope should be established, alternative solutions should be considered and technical and management constraints should be identified. • With...
Read more

Explain general format of Software Requirement Specification (SRS).

-
 Solution:- Software requirements specification (SRS) is a document that is created when a detailed description of all aspects of the software to be built must be specified before the project is to commence.  It is important to note that a formal SRS is not always written. In fact, there are many instances in which effort expended on an SRS might be better spent in other software engineering activities.  However, when software is to be developed by a third party, when a lack of specification would create severe business issues, or when a system is extremely complex or business critical, an SRS may be justified.  Karl Wiegers has developed a worthwhile template that can serve as a guideline for those who must create a complete SRS.  A topic outline follows: 1. Introduction 1.1. Purpose1.2. Document Conventions 1.3. Intended Audience and Reading Suggestions 1.4. Project Scope 1.5. References 2. Overall Description 2.1 Product Perspective 2.2 Product Features 2.3 U...
Read more

Difference between file processing system and Database management System.

-
solution:-    File processing System Database Management System 1. PC- based Systems. 1. Mini-mainframe based large system. 2. Relatively cheaper. 2. Relatively expensive.    3. Less number of files used. 3. More number of files used. 4. Single user system. 4. Multiple user system. 5. Data redundancy and inconsistency                      occur . 5. Data is independent and non-redundant. 6. Data access is difficult. 6. Data access is efficient. 7. Data is isolated. 7. Data is integrated. 8. Concurrent access to a file is not possible. 8. Concurrent access and crash recovery possible. 9. Security problems. 9. Better security. 10. Little preliminary d...
Read more