Abstract
Testing as a service (TaaS) provides features like easiness of use, high availability, low installation and maintenance cost, thus can aid programmers and white-box testers in improving software quality. Automatic test data generation being embedded in a TaaS must consume significant amount of time and computer resources while dealing with mid- or large-scale programs. However, allowing large volume of long-lived test sessions in a TaaS will incur adverse impact on the scalability of the TaaS and its hosting servers. To enable a TaaS supports time-consuming testing jobs and keeps its scalability simultaneously; a message queuing system could be adopted for holding un-processed test jobs temporarily. This article describes the corresponding design rationale, implementation details of a testing as a service with message queuing system and discusses its advantages.
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.
