White box
testing is concerned only with testing the software product; it cannot
guarantee that the complete specification has been implemented. Black box
testing is concerned only with testing the specification; it cannot
guarantee that all parts of the implementation have been tested. Thus black
box testing is testing against the specification and will discover
faults of omission, indicating that part of the specification has
not been fulfilled. White box testing is testing against the implementation
and will discover faults of commission, indicating that part
of the implementation is faulty. In order to fully test a software product
both black and white box testing are required.
White box testing is much more expensive than black box
testing. It requires the source code to be produced before the tests can be
planned and is much more laborious in the determination of suitable input data
and the determination if the software is or is not correct. The advice given is
to start test planning with a black box test approach as soon as the
specification is available. White box planning should commence as soon as all
black box tests have been successfully passed, with the production of flow
graphs and determination of paths. The paths should then be checked against the
black box test plan and any additional required test runs determined and
applied.
The consequences of test failure at this stage may be very
expensive. A failure of a white box test may result in a change which requires
all black box testing to be repeated and the re-determination of the white box
paths. The cheaper option is to regard the process of testing as one of
quality assurance rather than quality control. The intention is that
sufficient quality will be put into all previous design and production stages so
that it can be expected that testing will confirm that there are very few faults
present, quality assurance, rather than testing being relied upon to
discover any faults in the software, quality control.
Test Director Interview Questions | Software testings FAQ Test Director Interview Questions ... Software testings FAQs ..What is Test Director ... What are all the main features of Test Director.. How the assessment of the application will be taken place in Test Director .. etc etc
QA interview questions What is verification, What is validation, What is a walkthrough, What is an inspection, What is quality, What is good code, What is good design, What is software life cycle, What is the difference between alpha and beta testing, What is the difference between volume testing and load testing etc...
Software Quality Engineer Certification - CSQE The Certified Software Quality Engineer understands software quality development and implementation, software inspection, testing, verification and validation; and implements software development and maintenance processes and methods.
Certified Software Quality Analyst | CSQA Acquiring the designation of Certified Software Quality Analyst (CSQA) indicates a professional level of competence in the principles and practices of quality assurance in the IT profession.
HP LoadRunner software—tips and tricks for configuration, scripting and execution This guide provides tips and tricks for HP LoadRunner software configuration, scripting, and execution. It is a conglomerate of lessons learned by HP LoadRunner power user Opral Wisham,including unique code as well as code collected from other testers. This guide is intended to help testers just learning to use HP LoadRunner, as well as to provide new best practices for those who have used HP LoadRunner for many years.
Web HTTP Connection Patterns When Load-Testing Using LoadRunner HTTP Connections In a web environment clients communicate with the server using HTTP connections. A connection can be one-shot or persistent. One shot connection are used for one interaction, when the server has responded the connection is closed. Persistent connections are kept open for use in subsequent interactions. Persistent connections are closed by the client when it has finished with the server or by the server if the connection is inactive for too long.
what is LoadRunner LoadRunner is a performance and load testing product by Hewlett-Packard (since it acquired Mercury Interactive in November 2006) for examining system behaviour and performance, while generating actual load.
Popular 5 QA / Testing Documents
QA interview questions What is verification, What is validation, What is a walkthrough, What is an inspection, What is quality, What is good code, What is good design, What is software life cycle, What is the difference between alpha and beta testing, What is the difference between volume testing and load testing etc...
Test Director Interview Questions | Software testings FAQ Test Director Interview Questions ... Software testings FAQs ..What is Test Director ... What are all the main features of Test Director.. How the assessment of the application will be taken place in Test Director .. etc etc
site contact support@testingbrain.com All of the product names here are trademarks of their respective companies. Use information on this site at your own risk. Informations about software testing tools, software testing jobs, software testing tutorials, certifications, interview questions furnished in the site is collected from various sites and posts from users. This site does not host any files on its server. If any compliants about the posts please contact us at support@testingbrain.com, we are ready to move the posts.