An Enhanced Parallel Automation Testing Architecture for Test Case Execution

Customer requests for incorporating complicated business logic into software applications are common. As a result, as business requirements expand, the demand on the testing team to deliver a high-quality product in a short amount of time grows. Software testing guarantees that customers receive hig...

Full description

Saved in:
Bibliographic Details
Published in2022 5th International Conference on Computing and Informatics (ICCI) pp. 369 - 373
Main Authors Nagy, Sarah M., Maghawry, Huda A., Badr, Nagwa L.
Format Conference Proceeding
LanguageEnglish
Published IEEE 09.03.2022
Subjects
Online AccessGet full text
DOI10.1109/ICCI54321.2022.9756109

Cover

More Information
Summary:Customer requests for incorporating complicated business logic into software applications are common. As a result, as business requirements expand, the demand on the testing team to deliver a high-quality product in a short amount of time grows. Software testing guarantees that customers receive high-quality software. Manual testing becomes difficult since it is time-consuming. Besides, its cost rises as test suite sizes grow. In addition, human mistakes can slip into a system, resulting in losses for the company. Therefore, automation testing is best suited in situations when requirements change frequently, and a large volume of regression testing is required. Automation testing enhances accuracy while also saving the tester's time and the organization's money. The aim of this work is to propose an improved parallel automation testing architecture to significantly decrease testing time. The main problem with parallel testing is the existence of idle nodes that causes an increase in execution time. The proposed architecture solved this problem by running test cases in parallel using Selenium, Docker containers and implementing a dispatcher to ease and faster the process of distributing test cases between the network's nodes. As a result, the proposed architecture decreases testing process time, and no idle nodes exists anymore.
DOI:10.1109/ICCI54321.2022.9756109