Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21b011a29131e9f

Jump to content

Domain testing

From Wikipedia, the free encyclopedia

Domain testing is a software testing technique that involves selecting a small number of realistic test cases from a nearly infinite group of candidate test cases. It is one of the most widely practiced software testing techniques. Domain knowledge plays a very critical role while testing domain-specific work.[1][2][3][4][5][6][7]

References

[edit]
  1. Kaner 1997, p. 28.
  2. Clarke 1976, pp. 215–222.
  3. Clarke, Hassell & Richardson 1982, pp. 380–390.
  4. Myers 1979.
  5. Ostrand & Balcer 1988, pp. 676–686.
  6. Weyuker & Jeng 1991, pp. 703–711.
  7. White, Cohen & Zeil 1981, pp. 103–112.

Sources

[edit]
Books
  • Myers, Glenford J. (1979). The Art of Software Testing. New York: John Wiley & Sons. ISBN 0-471-04328-1. OCLC 4194539.
  • White, Lee J.; Cohen, Edward I; Zeil, Steven J. (1981). "A Domain Strategy for Computer Program Testing". In Chandrasekaran, B.; Radicchi, S. (eds.). Computer Program Testing: Proceedings of the Summer School on Computer Program Testing Held at SOGESTA, Urbino, Italy, June 29-July 3, 1981. Amsterdam; New York: North Holland. pp. 103–112. ISBN 0-444-86292-7. OCLC 7875177.
Journals
[edit]