Model-Based Testing Service on the Web Antti Jääskeläinen 1 , Mika Katara 1 , Antti Kervinen 1 , Henri Heiskanen 1 , Mika Maunumaa 1 , and Tuula Pääkkönen 2 1 Tampere University of Technology Department of Software Systems P.O.Box 553 FI-33101 Tampere, FINLAND {antti.m.jaaskelainen,firstname.lastname}@tut.fi 2 Nokia Devices P.O.Box 68 FI-33721 Tampere, FINLAND Abstract. Model-based testing (MBT) seems to be technically superior to con- ventional test automation. However, MBT features some difficulties that can ham- per its deployment in industrial contexts. We are developing a domain-specific MBT solution for graphical user interface (GUI) testing of Symbian S60 smart- phone applications. We believe that such a tailor-made solution can be easier to deploy than ones that are more generic. In this paper, we present a service con- cept and an associated web interface that hide the inherent complexity of the test generation algorithms and large test models. The interface enables an easy-to-use MBT service based on the well-known keyword concept. With this solution, a better separation of concerns can be obtained between the test modeling tasks that often require special expertise, and test execution that can be performed by testers. We believe that this can significantly speed up the industrial transfer of model-based testing technologies, at least in this context. 1 Introduction A widespread problem in software development organizations is how to cut down on the money, time, and effort spent on testing without compromising the quality. A frequent solution is to automate the execution of predefined test cases using test automation tools. Unfortunately, especially in graphical user interface (GUI) testing, test automation often does not find the bugs that it should and the tools provide a return on the investment only in regression type of testing. One of the main reasons for this is that the predefined test cases are linear and static in nature – they do not include the necessary variation to cover defected areas of the code, and they (almost) never change. Moreover, since GUI is often very volatile, it takes time to update the test suites to test the new version of the system under test (SUT). Hence, costly but flexible manual testing is still often chosen as the primary method to ensure the quality, at least in the context of mass consumer products, where GUIs are extremely important. Model-based testing (MBT) practices [1] that generate tests automatically can in- troduce more variance to the tests, or even generate an infinite number of different tests. Moreover, maintenance of the testware should become easier when only the models