Dalarna University's logo and link to the university's website

du.sePublications
Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • chicago-author-date
  • chicago-note-bibliography
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Comparison of GUI test automation strategies in a Clearing System: A case study at Nasdaq Stockholm AB
Dalarna University, School of Information and Engineering.
2021 (English)Independent thesis Basic level (degree of Bachelor), 10 credits / 15 HE creditsStudent thesis
Abstract [en]

The effectiveness of GUI-based automated tests is a topic that is often discussed in the testing community. As software systems and GUIs are getting more advanced, the testing of these systems may sometimes be both time-consuming and repetitive. Therefore, automated tests are used more frequently to create more agile working and to decrease the number of manual tests.

There is an ongoing discussion about the benefits and shortcomings of implementing automated GUI test compared to performing manual GUI tests. Increasingly, companies today are implementing automated GUI tests, yet relatively few are analyzing enough when choosing their test strategy.

The purpose of this thesis was to explore different test strategies in a system as complex as Nasdaq’s clearing system NRTC. The first strategy used manual GUI tests, while the second strategy used a test tool called Selenium WebDriver to automate the GUI tests. Hopefully, this research will contribute to the already accumulated knowledge about automated GUI tests and potentially help in choosing the right testing strategy.

The findings of this research showed that the implementation time of manual tests was much faster, and that implementing automated test would be timeconsuming. The reason for this is that the GUI was not very testable, making it difficult to create the test scripts. In addition, the was a difference in runtime when using both strategies. The automated tests only took a couple of seconds to execute, compared to the manual tests that took a couple of minutes.

After both strategies was investigated, an analysis was done by looking at the effectivity, maintainability, robustness, and the overall results to be able to find benefits and shortcomings.

In conclusion, GUI automation cannot replace manual test completely. By not including the human capabilities, the testing process becomes very limited. 

Place, publisher, year, edition, pages
2021.
Keywords [en]
Test automation, Automated GUI testing, Manual testing, Selenium WebDriver
National Category
Information Systems
Identifiers
URN: urn:nbn:se:du-37600OAI: oai:DiVA.org:du-37600DiVA, id: diva2:1577975
Subject / course
Information Systems
Available from: 2021-07-05 Created: 2021-07-05 Last updated: 2025-10-09

Open Access in DiVA

fulltext(595 kB)380 downloads
File information
File name FULLTEXT01.pdfFile size 595 kBChecksum SHA-512
29ff597d2cdf98d5e164fc00c0357f4673680529287e487e859604210591b95725822646b9307a226120fbf5060a85e75c002e8521a87706d5059298c37d1141
Type fulltextMimetype application/pdf

By organisation
School of Information and Engineering
Information Systems

Search outside of DiVA

GoogleGoogle Scholar
Total: 380 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

urn-nbn

Altmetric score

urn-nbn
Total: 592 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • chicago-author-date
  • chicago-note-bibliography
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf