Author Topic: Software Test Methods  (Read 143 times)

0 Members and 1 Guest are viewing this topic.

Offline Transformer10

  • Full Member
  • *
  • Posts: 104
  • Karma: +0/-0
    • View Profile
Software Test Methods
« on: October 14, 2008, 06:52:46 PM »
Software testing methods are traditionally divided into black box testing and white box testing. These two approaches are used to describe the point of view that a test engineer takes when designing test cases.

Black box testing

Black box testing treats the software as a black box without any knowledge of internal implementation. Black box testing methods include equivalence partitioning, boundary value analysis, all-pairs testing, fuzz testing, model-based testing, traceability matrix, exploratory testing and specification-based testing.

Specification-based testing
    Specification-based testing aims to test the functionality according to the requirements.[16] Thus, the tester inputs data and only sees the output from the test object. This level of testing usually requires thorough test cases to be provided to the tester who then can simply verify that for a given input, the output value (or behavior), is the same as the expected value specified in the test case.

    Specification-based testing is necessary but insufficient to guard against certain risks.[17]

White box testing

White box testing, by contrast to black box testing, is when the tester has access to the internal data structures and algorithms (and the code that implement these)

Types of white box testing

    The following types of white box testing exist:

        * code coverage - creating tests to satisfy some criteria of code coverage. For example, the test designer can create tests to cause all statements in the program to be executed at least once.
        * mutation testing methods.
        * fault injection methods.
        * static testing - White box testing includes all static testing.

Code completeness evaluation

    White box testing methods can also be used to evaluate the completeness of a test suite that was created with black box testing methods. This allows the software team to examine parts of a system that are rarely tested and ensures that the most important function points have been tested.[18]

    Two common forms of code coverage are:

        * function coverage, which reports on functions executed
        * and statement coverage, which reports on the number of lines executed to complete the test.

They both return a coverage metric, measured as a percentage.

Grey Box Testing

In recent years the term grey box testing has come into common usage. This involves having access to internal data structures and algorithms for purposes of designing the test cases, but testing at the user, or black-box level.

Manipulating input data and formatting output do not qualify as grey-box because the input and output are clearly outside of the black-box we are calling the software under test. This is particularly important when conducting integration testing between two modules of code written by two different developers, where only the interfaces are exposed for test. Grey box testing may also include reverse engineering to determine, for instance, boundary values or error messages.

 Non Functional Software Testing

Special methods exist to test non-functional aspects of software.

    * Performance testing checks to see if the software can handle large quantities of data or users. This is generally referred to as software scalability.
    * Usability testing is needed to check if the user interface is easy to use and understand.
    * Security testing is essential for software which processes confidential data and to prevent system intrusion by hackers.
    * Internationalization and localization is needed to test these aspects of software, for which a pseudolocalization method can be used.

Techronnati | where technology never sleeps

Software Test Methods
« on: October 14, 2008, 06:52:46 PM »

Mountain View


Related Topics

  Subject / Started by Replies Last post
0 Replies
Last post November 13, 2008, 06:36:45 PM
by Berto
3 Replies
Last post January 06, 2009, 06:54:27 AM
by rpmolecule
0 Replies
Last post February 04, 2009, 12:17:34 PM
by techguy
0 Replies
Last post June 01, 2010, 11:53:57 PM
by MrSpecialist
1 Replies
Last post July 21, 2016, 06:25:10 AM
by MrSpecialist

Posting Disclaimer: Any individual may post a message in this forum and may do so anonymously. Therefore, the sole author is exclusively and entirely responsible for all opinions in that message. They do not represent the official opinions of Techronnati, its administrators or moderators or the Techronnati Management. Techronnati is merely acting as an impartial conduit for constitutionally protected free speech and is not responsible and will not be held liable for the content of such messages. All images and service logos are trademarks of their respective owners.