This form of testing is where two or more variants of a system or component are fed with the same input. The outputs are then compared and, should there be differences, a detailed analysis of causes is carried out.
Beta testing is carried out externally on operational software by a sufficiently large and representative group of people - either clients or users in a related environment.
Beta testing allows producers to carry out a form of acceptance test before finally releasing the software onto the market. Feedback from potential customers and users can be gained at this stage.
This approach is most often used when the number of different user environments envisioned is large and diverse.
Cf. beta testing on Wikipedia.
Black-box testing takes an external perspective of the test object as a basis on which to develop test cases. These tests can be functional or non-functional, though they are usually functional.
The test designer selects valid and invalid inputs and determines the correct output. There is no reference to or examination of the test object's internal structure.
See also black-box testing on Wikipedia.
In a control flow graph, a vectored edge is called a branch.
In addition to this, a branch can aslo be:
This is a database of faults used to oversee processing. All information about the faults as well as their status are contained in this database.
Bug trackers are often used during testing so that faults detected by testers are passed onto developers.
There are several bug trackers available, from freeware through to commercial software. Well-know systems include: Mantis, Bugzilla, Jira, OTRS and OnTime. Microsoft's Team Foundation Server (TFS) can also be used as a bug-tracker.
Zeta Test currently supports integration with the following trackers:
Cf. bug tracking systems on Wikipedia.