Traffic and Feature SW is a department based in Kista. At this department the main processor software, or MPSW in short, in Ericssons Radio Base Stations is tested prior to integration of new releases. Traffic and Feature SW, also called MPSW in this thesis, works closely with another department of Ericsson called RBS System I&V which tests the same software but for complete RBS nodes. MPSW uses black- and greybox scripted testing in regression suites that are executed on a daily basis. These regression suites are separated into different subsets of functionality that maps to the capabilities of the Radio Base Station software. The authors of this thesis has performed an implementation of automated test cases for a subset of the Radio Base Station software using an automated software tool called QuickCheck. These test cases were successfully integrated into the test framework and were able to find several issues with the main processor software and its subsystems in the Radio Base Station. The commissioner of this thesis have plans to further integrate the QuickCheck tool into the test framework, possibly automating test cases for several subsets of the Radio Base Station software. The authors have therefore analysed and put forth metrics that compares the testing of the Radio Base Station software using QuickCheck with the conventional regression test cases. These metrics covers areas such as the cost related to and the inherent capabilities of QuickCheck. The evaluation of these metrics was performed by the authors to give the commissioner decisive information. These evaluations showed that QuickCheck was able to generate complex message stuctures in complex sequences. QuickCheck was also able to shrink both the content of these messages and the length of the sequences of messages to be able to provide a minimal counterexample when a fault was discovered. The only metric that QuickCheck failed to support was to inherit functionality to support the handling of statistics from executions. / Traffic and Feature SW is a department based in Kista. At this department the main processor software, or MPSW in short, in Ericssons Radio Base Stations is tested prior to integration of new releases. Traffic and Feature SW, also called MPSW in this thesis, works closely with another department of Ericsson called RBS System I&V which tests the same software but for complete RBS nodes. MPSW uses black- and greybox scripted testing in regression suites that are executed on a daily basis. These regression suites are separated into different subsets of functionality that maps to the capabilities of the Radio Base Station software. The authors of this thesis has performed an implementation of automated test cases for a subset of the Radio Base Station software using an automated software tool called QuickCheck. These test cases were successfully integrated into the test framework and were able to find several issues with the main processor software and its subsystems in the Radio Base Station. The commissioner of this thesis have plans to further integrate the QuickCheck tool into the test framework, possibly automating test cases for several subsets of the Radio Base Station software. The authors have therefore analysed and put forth metrics that compares the testing of the Radio Base Station software using QuickCheck with the conventional regression test cases. These metrics covers areas such as the cost related to and the inherent capabilities of QuickCheck. The evaluation of these metrics was performed by the authors to give the commissioner decisive information. These evaluations showed that QuickCheck was able to generate complex message stuctures in complex sequences. QuickCheck was also able to shrink both the content of these messages and the length of the sequences of messages to be able to provide a minimal counterexample when a fault was discovered. The only metric that QuickCheck failed to support was to inherit functionality to support the handling of statistics from executions.

SIMON is an automated testing application developed by WM-Data Consulting in Växjö, Sweden. Previously the test cases, called BIFs, run by SIMON to test the applications under test has been written manually in a very time consuming manner offering no protection against errors in the structure or misspellings. This thesis investigates a replacement to the manual method when creating the BIFs; my own developed application called the BIF-Editor. The usage of the BIF-Editor guaranteed correct syntax and structure and made the creation of the BIFs faster, but did it increase the quality of the BIFs? So to evaluate the BIF-Editor, the quality regarding path coverage of BIFs manually created was compared with BIFs created during the same elapsed time using the BIF-Editor. This evaluation showed that the usage of the BIF-Editor increased the quality of the BIFs by making the creation safer, but primarily faster which enabled the user to produce more BIFs than previously possible resulting in a raised path cover.

This thesis was carried out at Scania CV AB, at the cab software testing group, RCIV. One of RCIV’s responsibilities includes testing of the instrument cluster used in Scania’s heavy trucks and buses. Today, this is done semi-automated. The tests are executed automatically in Vector’s CANoe software but are verified manually by a tester who needs to observe the instrument cluster. We have investigated the possibility to automate this testing procedure with the use of a camera based vision system and have studied different solutions available on today’s market. We studied five company’s solutions for a complete, or partial, automated test environment solutions as well as the possibility to have Scania develop a system of their own. The pros and cons we have found along with the cost of the systems are listed in this report. We also built a prototype with one of the image processing software alternatives. Our investigation showed that an automated test environment with a camera based vision system could be very beneficial for RCIV and could support much of the current testing but the system must be fully verified before replacing today’s semi-automated tests.

To gain confidence in that a dynamic real-time system behaves correctly, we test it. Automated verification & validation can be used to conduct testing of such systems in an effective and economic way. An event monitor can be used as a part of a test oracle to monitor the system that is being tested. The test oracle could use the data (i.e., the streams of events) derived from the tested system, to determine if an executed test case gave a positive or negative result. To do this, the test oracle compares the streams of events received from the event monitor with the event expressions derived from the formal specification, and decides if the executed test case has responded positive or negative. Any deviations between observed behaviour and accepted behaviour should be reported by the test oracle as a negative result. If the executed test case gave a negative result, the monitor part should signal this to the reporter part of the test oracle. This work aims to investigate how the event expressions can be derived from the formal specification, and in particular, how the event specification language Solicitor can be used to represent these event expressions. We also discuss the need for parameterized event types in Solicitor, and any other event specification languages used in event monitoring. We also show that support for parameterized event types is a significant requirement for such languages.

The aim of the project is to develop software to automatically test line current supervision and interference monitoring devices for Bombardier trains. The software, called MALTE, it to replace the manual testing done by an engineer, thereby freeing up the tester to do other tasks, and increasing the test rigorousness. The test software, written in LabView, was developed in tandem with a hardware rack, with interfaces to the train hardware enabling communication between the two, to set test conditions and simulate the environment encountered by the hardware when on the train. When completed, MALTE was found to be an order of magnitude faster than a test engineer performing the tests, meaning a large save in time and cost for the engineering team.

Android is one of the most popular mobile operating systems on the market today with a vast majority of the market share when it comes to mobile devices. Graphical user interfaces (GUI) are often seen on the applications on these devices. Testing of these GUIs is important since they often make up for half of the source code of the application, and they are used to interact with the application. Automating these tests is very useful since it saves a lot of time, but can be difficult. The tools that are available for automating the tests are often not suitable for the developers’ needs, because of the lack of functionality. Therefore, the need for a characterization of the frameworks is needed, so that developers more easily can fit a framework for their needs. In this study, four open source frameworks for Android GUI testing have been selected for evaluation: Robotium, Selendroid, UI Automator and Espresso. Criteria used in the evaluation have been identified with the help of a literature analysis.The results show that two of the frameworks, Robotium and Espresso, lack the ability to fully test activities, which is the main component of Android application GUIs. Furthermore, the study resulted in characterizations of the frameworks.

Software testing plays an important role in the process of verifying software functionality and preventing bugs in production code. By writing automated tests using code instead of conducting manual tests, the amount of tedious work during the development process can be reduced and the software quality can be improved. This thesis presents the results of a conducted case study on how automated testing can be used when implementing new functionality in a Ruby on Rails web application. Different frameworks for automated software testing are used as well as test-driven development methodology, with the purpose of getting a broad perspective on the subject. This thesis studies common issues with testing web applications, and discuss drawbacks and advantages of different testing approaches. It also looks into quality factors that are applicable for tests, and analyze how these can be measured.

Development of web applications with JavaScript language has been moving forward really fast recently. Methodic for software development, on the other hand, not so much. Those methodic were often created way before JavaScript was so popular and so they might not reflect needs, which development of modern web applications using JavaScript brings. This thesis focus on opportunities, needs or threats of modern web applications development and its combination with Methodic for small software projects. Thesis define what is considered as a modern web application, identify practices and tools needed for development and how they relate to the existing version of MMSP. Based on this comparison thesis offers extension of this methodic for development of modern web applications.

This thesis deals with the methodology used for application testing, using the Robot Framework. Its main objective is to develop a methodology which describes an approach to automated testing using this tool. An important part of the methodology is to design a user guide for the Robot Framework - at the time of writing this thesis assignment, this guide does not exist in the Czech language. In this thesis the basic concepts and approaches to automation testing in accordance with defined objectives are explained. An integral part of this is the description of the Robot Framework, its architecture and tools used, libraries, other built-in tools and the syntax used for creating test cases.

The purpose of this thesis is to design and implement integration interface, which represents the core of the Integrated testing tool. Integrated testing tool provides support in the whole process of software testing. This support involves requirement specification and management of the corresponding tests, bug management and creation and execution of automated testing scripts. Integrated testing tool uses existing open-source tools to provide this functionality. The communication of these tools is provided by the integration interface, implementation of which is the purpose of this thesis. Currently there is no so complex open-source solution in the testing area, Integrated testing tool endeavours to fill this gap. The tool is being developed within the activity of the competence centre Software Quality Assurance at the University of Economics in Prague. The analytical phase of the development is described in the diploma thesis written by Bc. Jan Ženíšek Project of the development of Integrated testing tool.