Sciweavers

COMPUTER
2002

GUI Testing: Pitfalls and Process

13 years 4 months ago
GUI Testing: Pitfalls and Process
ion, so mapping between GUI events and the underlying code is not straightforward. Code-based coverage criteria do not necessarily address problematic interactions between the GUI's user events and the application. Second, even when experienced test designers focus on specific parts of a GUI, they may still find it impractical to generate all possible test cases for these parts. If the designers have to generate a subset of all possible test cases, they often must select the subset during test case generation. The difficulty of anticipating a test case's fault-detection capability makes it difficult, in turn, to select the most effective subset. Test oracles Verifying whether the GUI executes correctly poses a problem. The traditional verification tool is a test oracle-a separate program that generates expected results for a test case and compares them with actual results. In conventional software testing, the tester invokes the oracle after the test case executes and compare...
Atif M. Memon
Added 18 Dec 2010
Updated 18 Dec 2010
Type Journal
Year 2002
Where COMPUTER
Authors Atif M. Memon
Comments (0)