Abstract
Component-based software systems consist of various components, such as third-party components and in-house built components. Component changes frequently occur in software maintenance, which refers to regression testing. When changes made to a component, the component could be affected, moreover, the changes could bring impacts on the entire system. Related existing research did not address the issue of systematic regression testing of component-based software, especially at system level. This paper proposes a systematic regression testing method from components to system, including analysis of change, impact and test suite refreshment. The paper also reports a case study based on a realistic component-based software system using a state-based testing practice, which shows that the approach is feasible and effective.
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 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.
