Abstract
Data flow and domain testing are both well-known program-based testing techniques. Each has its intuitive appeal, but their widespread use has been hampered by practical limitations. Data flow testing provides a number of structural coverage criteria, which are of low cost but are not well-suited for finding faults involving special values or small shifts in domain boundaries. Domain testing is designed to uncover boundary shift faults of a given path domain, but it lacks a path selection criterion to guide the selection of testing paths from a program. By letting a variable definition be “domain tested”, this paper presents an integrated approach that keeps the strengths of the two testing strategies while avoiding their deficiencies.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
