Spelling suggestions: "subject:"mjukvarutestning"" "subject:"mjukvarutestningen""
1 |
SOFTWARE TEST AUTOMATION : Implementation of End-to-End testing in web applicationBjörkman, Maria January 2024 (has links)
Today’s software applications are often scattered in many layers, suchas connected to cloud services or third-party solutions. This makes itimportant to ensure that a software application works as intended ina real-world setting, especially when changes are made to the codebase. End-to-End (E2E) tests are made to ensure the software has theexpected behavior from an end-user’s viewpoint. Automation of thesoftware testing process is often implemented since it has the potentialto be more time-efficient than manually inspecting the behavior of thesoftware application. This thesis describes the work of implementing automated E2E tests foran e-learning application. The first step in the project was to identifywhich automated testing tool would best suit the criteria laid out for theproject. The criteria were that the testing tool needed to have supportfor testing in the Chrome browser, support for using JavaScript as theprogramming language, and to be open-source and possible to be usedfree of charge. A literature review and a comparison of the most popu-lar E2E testing tools yielded the result that Playwright was best suitedas the automated testing tool because it has good documentation and isspecifically a tool for implementing End-to-End tests. After that, a testsuite consisting of 11 test cases was implemented in Playwright. Thetest cases were evaluated and improved in an iterative process con-cerning robustness and performance. This project supports previousobservations that automation of the test process is time-consuming inthe initial stage. This thesis concluded that Playwright is a suitable tool to use withinE2E testing, with a low learning curve. Furthermore, it concluded thatthe robustness of the tests is an important factor for the tests to be use-ful in the testing process. Tests that unexpectedly fail on occasion needto be properly investigated. It would be important to have a proper testenvironment where test data can be reset, so all the desired user flowscan get a test case. Developers and testers benefit from working closelytogether. The collaborative company can take the findings from this re-search for future reference, in case they decide to update the company’scurrent testing process.
|
Page generated in 0.0585 seconds