Gray box testing

Gray-box testing (International English spelling: grey-box testing) is a combination of white-box testing and black-box testing. The aim of this testing is to search for the defects if any due to improper structure or improper usage of applications.[1][2]

Overview

A black-box tester is unaware of the internal structure of the application to be tested, while a white-box tester has access to the internal structure of the application. A gray-box tester partially knows the internal structure, which includes access to the documentation of internal data structures as well as the algorithms used.[3]

Gray-box testers require both high-level and detailed documents describing the application, which they collect in order to define test cases.[4]

Need for gray-box testing

Gray-box testing is beneficial because it takes the straightforward technique of black-box testing and combines it with the code-targeted systems in white-box testing.

Gray-box testing is based on requirement test case generation because it presents all the conditions before the program is tested by using the assertion method. A requirement specification language is used to make it easy to understand the requirements and verify its correctness.[5]

Gray-box testing assumptions for object-oriented software

Object-oriented software consists primarily of objects; where objects are single indivisible units having executable code and/or data. Some assumptions are stated below which are needed for the application of use gray-box testing.

Examples

Techniques

Cem Kaner defines "gray-box testing as involving inputs and outputs, but test design is educated by information about the code or the program operation of a kind that would normally be out of view of the tester".[9] Gray-box testing techniques are:

Effects

Positive Effects

Negative Effects

Applications

Future scope

The distributed nature of Web services allows gray-box testing to detect defects within a service-oriented architecture (SOA). As we know, white-box testing is not suitable for Web services as it deals directly with the internal structures. White-box testing can be used for state art methods; for example, message mutation which generates the automatic tests for large arrays to help exception handling states, flow without source code or binaries. Such a strategy is useful to push gray-box testing nearer to the outcomes of white-box testing.

See also

Grey box model

References

  1. http://research.microsoft.com/pubs/81199/p1-kicillof.pdf
  2. http://eastwest.inf.brad.ac.uk/document/publication/Doungsa-ard-IWS06%20.pdf
  3. "Gray Box Testing". Software Testing Fundamentals. 4 November 2011. Retrieved 19 January 2012.
  4. "Example of grey box testing with definition". Geekinterview.com. Retrieved 19 January 2012.
  5. 1 2 Sunil Nanda. "Software Testing, Tutorials, Testing Tools, QTP Certification, Quicktest Professional, Web Testing". Softwaretestinggenius.com. Retrieved 19 January 2012.
  6. "Object-Oriented Extensions to Pascal". Pascal-central.com. Retrieved 19 January 2012.
  7. Patton, Ron (26 July 2005). Software Testing. Sams. p. 2. ISBN 0-672-32798-8.
  8. http://www.site.uottawa.ca/~ssome/Cours/SEG3203/gboxtesting.pdf
  9. Nguyen, Hung Q (2001). Testing Applications on the Web: Test Planning for Internet-Based Systems. John Wiley & Sons. ISBN 9780471437642.
  10. "Explore the World of Gray Box Testing". Extremesoftwaretesting.com. Retrieved 19 January 2012.
  11. 1 2 "SOA Testing Tools for Black, White and Gray Box SOA Testing Techniques". Crosschecknet.com. Retrieved 19 January 2012.
  12. http://www.sfisaca.org/events/conference04/presentations/E33-Gray-Box-Testing.pdf
  13. Ramdeo, Anand (5 May 2011). "Gray Box Testing - Software". Testing Geek. Retrieved 19 January 2012.
  14. Bach, James. Lessons Learned in Software Testing. Wiley Computer Publishing.
  15. Falk, Jack. Testing Computer Software, 2nd Edition. Wiley Computer Publishing.
  16. http://legacy.cleanscape.net/docs_lib/paper_graybox.pdf
  17. "IEEE Xplore - Business-process-driven gray-box SOA testing". Ieeexplore.ieee.org. 6 April 2010. doi:10.1147/sj.473.0457. Retrieved 19 January 2012.
This article is issued from Wikipedia - version of the Thursday, July 09, 2015. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.