eLABa objektas:   "Programų vartotojo sąsajos automatinis testavimas pagrįstas UML modeliais", 2010,D:20100813:112653-98147
E. dokumentai
ETD (LT)
visi dokumentai ...
URL nuoroda http://vddb.laba.lt/obj/LT-eLABa-0001:E.02~2010~D_20100813_112653-98147
Dokumentas Magistro darbas
Prieigos teisės Laisvai prieinamas internete.
Institucija Kauno technologijos universitetas
Mokslo kryptis 07 T - Informatikos inžinerija
Atsakomybė Jasaitis, Robertas - Magistro baigiamojo darbo autorius
Motiejūnas, Kęstutis - Magistro baigiamojo darbo vertinimo posėdžio sekretorius
Bareiša, Eduardas - Magistro baigiamojo darbo vadovas
Butleris, Rimantas - Magistro baigiamojo darbo vertinimo komisijos narys
Tomkevičius, Arūnas - Magistro baigiamojo darbo vertinimo komisijos pirmininkas
Šeinauskas, Rimantas - Magistro baigiamojo darbo vertinimo komisijos narys
Štuikys, Vytautas - Magistro baigiamojo darbo vertinimo komisijos narys
Nemuraitė, Lina - Magistro baigiamojo darbo recenzentas
Kauno technologijos universitetas - Mokslinį laipsnį teikianti institucija
Antraštė (-ės) Programų vartotojo sąsajos automatinis testavimas pagrįstas UML modeliais
Program user interface automated testing based on UML models
Santrauka [EN]

In many cases, testing is an essential, but time and resource consuming activity in the software development process. In the case of model-based development, test construction and test execution can be partially automated. As the application size is constantly growing, the need for automated testing frameworks comes into place, particularly frameworks for automated testing of user interaction and graphical user interface.

This document describes an implementation of the GUI test generator framework based on UML models where specific UML activity diagrams are used for test case generation. It is not a usual case to use UML activity diagrams for UI modeling. However the existing stereotypes of activity diagram elements are not suitable for UI modeling. With usual activity diagram it is complicated to define buttons, containers, pages and other UI elements in the diagram and find differences between them. Even more complicated is to model the navigation of the testing application. Using this approach the UI can be defined in a set of UI elements along with a set of UI navigation elements. This is an optimal and suitable approach in most cases.

This document describes an implementation of the automated GUI tests runner framework as well. This framework is able to run the given application in test mode using the previously generated test cases. The framework collects all the information about each test case results and provides it to the tester.

Future improvements:

Find the solution to identify a set of optimal paths covering all elements in the diagram

Implement mechanism that allows user to set priorities to the pages in diagram and inspect the most important pages only while generating the test cases

Improve test case generator by implementing the automated notification of input fields and ability to generate user specific inputs to that input field.

Raktažodžiai: user interface, testing, UML