Abstract
Executable test cases start at the beginning of testing as abstract requirements representing the system behavior. The manual development of these test cases is labor-intensive, error-prone, and costly. Describing the system requirements into behavioral models and transforming them into a scripting language has the potential to automate their propagation to executable tests. Ideally, an efficient testing process should begin as early as possible, refine the use cases with sufficient details and facilitate test case creation. We propose an approach that enables automation in propagating functional requirements to executable test cases through model transformation. The proposed testing process begins with capturing system behavior as visual use cases, adopting a domain-specific language, defining transformation rules, and finally transforming the use cases into executable tests.
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.
