Abstract
Executable test cases originate at the onset of testing as abstract requirements that represent system behavior. Their manual development is time-consuming, susceptible to errors, and expensive. Translating system requirements into behavioral models and then transforming them into a scripting language has the potential to automate their conversion into executable tests. Ideally, an effective testing process should start as early as possible, refine the use cases with ample details, and facilitate the creation of test cases.We propose a methodology that enables automation in converting functional requirements into executable test cases via model transformation. The proposed testing process starts with capturing system behavior in the form of visual use cases, using a domain-specific language, defining transformation rules, and ultimately transforming the use cases into executable tests.
Sign-in/Register to access full text options 
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 callMore From: International Journal of Software Engineering & Applications
Disclaimer: 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.
