Context: Software testing is expensive, labor intensive and consumes lot of time in a software development life cycle. There was always a need in software testing to decrease the testing time. This also resulted to focus on Automated Software Testing (AST), because using automated testing, with specific tools, this effort can be dramatically reduced and the costs related with testing can decrease [11]. Manual Testing (MT) requires lot of effort and hard work, if we measure in terms of person per month [11]. Automated Software testing helps to decrease the work load by giving some testing tasks to the computers. Computer systems are cheap, they are faster and don‘t get bored and can work continuously in the weekends. Due to this advantage many researches are working towards the Automation of software testing, which can help to complete the task in less testing time [10]. Objectives: The main aims of this thesis is to 1.) To systematically classify contributions within AST. 2.) To identify the different benefits and challenges of AST. 3.) To identify the whether the reported benefits and challenges found in the literature are prevalent in industry. Methods: To fulfill our aims and objectives, we used Systematic mapping research methodology to systematically classify contributions within AST. We also used SLR to identify the different benefits and challenges of AST. Finally, we performed web based survey to validate the finding of SLR. Results: After performing Systematic mapping, the main aspects within AST include purpose of automation, levels of testing, Technology used, different types of research types used and frequency of AST studies over the time. From Systematic literature review, we found the benefits and challenges of AST. The benefits of AST include higher product quality, less testing time, reliability, increase in confidence, reusability, less human effort, reduction of cost and increase in fault detection. The challenges include failure to achieve expected goals, difficulty in maintenance of test automation, Test automation needs more time to mature, false expectations and lack of skilled people for test automation tools. From web survey, it is observed that almost all the benefits and challenges are prevalent in industry. The benefits such as fault detection and confidence are in contrary to the results of SLR. The challenge about the appropriate test automation strategy has 24 % disagreement from the respondents and 30% uncertainty. The reason is that the automation strategy is totally dependent on the test manager of the project. When asked “Does automated software testing fully replace manual testing”, 80% disagree with this challenge. Conclusion: The classification of the AST studies using systematic mapping gives an overview of the work done in the area of AST and also helps to find research coverage in the area of AST. These results can be used by researchers to use the gaps found in the mapping studies to carry on future work. The results of SLR and web survey clearly show that the practitioners clearly realize the benefits and challenges of AST reported in the literature. / Mobile no: +46723069909

The topic of this thesis is the issue of software testing. The thesis places main emphasis on tools to support test management, manual and automated functional testing and last but not least the tools for defect tracking. The aim of this thesis is introduce readers with software testing, especially with tools that can be used to support testing. The aim is offer an overview of the basic commercial and freely distributed tools for test management, manual testing, automated functional testing and defect tracking. Another aim is design criteria that simplify selection of tool. The second aim of this thesis is practical example of the configuration and description of the basic work with tools IBM Rational - ClearQuest, ClearCase, Manual Tester and Functional Tester. The aims of this thesis were achieved by studying available sources and by own practical experience with the tools to support testing. The contribution of this thesis lies in the characteristics of the selected tools to support testing and especially in design of criteria by which tools can be selected. The last part of thesis provides practical instruction how to configure and work with the tools to support testing of IBM Rational. The thesis is conceived in three main parts. The first part attends to basic terms, which can be found in the area of testing, and to overview of types of tests. There are also described two most famous life-cycle models and methodology RUP. The second part attends to overview of tools to support testing, attention is given to areas: test management, manual testing, defect tracking, and automated functional testing. For each category of tools has been defined criteria according to which tools can be selected. The last part attends to practical example of setting and basic work with the selected tools to support testing of IBM Rational.

Nowadays the development speed of new software products is a key to success and it is not important whether the aim is to make customer's urges satisfied or get ahead of one's competitors and fill the market gap. Because of the increase of development speed the demands on the saving process of software quality are increasing. There are two types of tools that are supporting the process of software quality assurance. Firstly, we talk about comprehensive testing tools of commercial character that usually include many functions, but their purchase is extremely expensive. On the other hand there are open-source tools that are available for free, they function on many kinds of operating systems and it is possible to modify them. Unfortunately their functions are basically focused on a certain subset of controlling the software quality assurance. Company TRASK solution a.s. has decided to change this current situation, so it asked competence centre Software Quality Assurance at the University of Economics in Prague in order to create Integrated Testing Node (ITN) that would combine the advantages of open-source tools. Moreover, it would offer broad range of functions as commercial solution. The purpose of this thesis is to describe relevant phases of the process of creating the Integrated Testing Node from the factual and methodical point of view. This aim is divided into partial aims included task analysis and the proposal of solving system, open-source products portfolio analysis, choice of the most convenient tools for following integration, choosing the method of information system building, evaluating the feedback from a client and the proposal of future development of this tool. As far as the biggest contribution of this thesis is concerned, it is the realisation of ITN project that can be used during information classes at the University of Economics in Prague. Furthermore, it can be used as the control of software quality in commercial companies.