To see the other types of publications on this topic, follow the link: Automation and software testing.

Dissertations / Theses on the topic 'Automation and software testing'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the top 50 dissertations / theses for your research on the topic 'Automation and software testing.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.

1

Eatinger, Christopher J. "Testing automation tools for secure software development." Thesis, Monterey, Calif. : Naval Postgraduate School, 2007. http://bosun.nps.edu/uhtbin/hyperion-image.exe/07Jun%5FEatinger.pdf.

Full text
Abstract:
Thesis (M.S. in Computer Science)--Naval Postgraduate School, June 2007.
Thesis Advisor(s): Mikhail Auguston. "June 2007." Description based on title screen as viewed on August 14, 2007. Includes bibliographical references (p. 61). Also available in print.
APA, Harvard, Vancouver, ISO, and other styles
2

Jayachandran, Naveen. "Understanding roi metrics for software test automation." [Tampa, Fla.] : University of South Florida, 2005. http://purl.fcla.edu/fcla/etd/SFE0001241.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Di, Silvestro Fabio. "Improving testing reusability and automation for software product lines." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-48635.

Full text
Abstract:
Software product lines are widely used in industrial environments for developing complex software systems. One of the main advantages deriving from the adoption of this software engineering development methodology is increased reusability. In fact, software product lines offer convenient means for representing different products belonging to the same family and different families of products by grouping shared functionalities and highlighting differences. Despite software product lines inherently improve the design and the development of complex software systems, they usually require ad-hoc strategies for the testing of such systems.To this end, testing strategies for software product lines need to account for the extensive amount of artefacts reuse and for possible differences among such artefact, too.In fact, even though software product line products might share several functionalities, the interfaces of such functionalities might differ due to the specificities imposed by the products or their designs. In this thesis, we propose a testing approach for software product lines, which allows to test functionalities that are shared among the products, accounting for the potential heterogeneity of the exposed interfaces.The main contribution of this approach is the definition of generic test-cases from which product-specific test-scripts are automatically generated, so to enhance the reusability of the handcrafted artefacts and overcome the issue of different interfaces.What is more, the proposed approach discloses the opportunity to reduce the time required to develop testing artefacts.
APA, Harvard, Vancouver, ISO, and other styles
4

Seppänen, T. (Tuomas). "Automation improvements to LTE eNodeB user plane software integration testing." Master's thesis, University of Oulu, 2016. http://urn.fi/URN:NBN:fi:oulu-201602111170.

Full text
Abstract:
The LTE eNodeB base station software is composed of various interconnected components, which handle different functionalities. Integration testing is used to test the interfaces and interactions between the components when they are combined together. In agile software development new software component builds are created frequently, which leads to a need for a quick and automated testing environment. This thesis focuses on improving the level of automation in the LTE User Plane software integration testing continuous integration environment. Two different subjects, interface specification adaptation and test scenario configuration, are addressed in this study. An automated system triggered by the continuous integration platform is implemented to update the testing environment so that it complies with the latest interface specification. In addition, a new software tool is developed as a proof of concept for an alternative method for test script writing and test case creation. The tool is used to create and configure test scenarios in a graphical user interface and to automatically generate test scripts from the configuration instead of writing the test scripts manually. The operation of the automated adaptation system was observed for more than a year with over a hundred interface specification changes. Results show a substantial reduction in processing time when comparing to the earlier manual process and no errors were detected in the output. The new software tool for creating test scenarios achieves its goal. The tool enables the creation and configuration of basic test scenarios in the graphical user interface and the generated test scripts can be executed successfully
LTE eNodeB -tukiasema koostuu useasta toisiinsa yhteydessä olevasta komponentista, jotka käsittelevät eri toiminnallisuuksia. Integraatiotestausta käytetään komponenttien välisten rajapintojen ja vuorovaikutusten testaamiseen. Ketterässä ohjelmistokehityksessä uusia käännöksiä ohjelmistokomponenteista luodaan usein, mikä luo tarpeen nopealle ja automatisoidulle testiympäristölle. Tämä diplomityö keskittyy parantamaan automaation tasoa LTE User Plane -ohjelmiston integraatiotestauksen jatkuvan integroinnin ympäristössä. Työssä käsitellään kahta eri aihetta: rajapintamäärittelyihin mukautumista sekä testiskenaarioiden konfiguraatiota. Automatisoitu järjestelmä, jonka käynnistää jatkuvan integroinnin alusta, toteutetaan päivittämään testiympäristö noudattamaan viimeisintä rajapintamäärittelyä. Lisäksi uusi ohjelmistotyökalu kehitetään osoituksena vaihtoehtoisesta tavasta testikoodin kirjoittamiseen ja testitapausten luomiseen. Työkalua käytetään graafisessa käyttöliittymässä testiskenaarioiden muodostamiseen ja konfigurointiin sekä testikoodin automaattiseen tuottamiseen konfiguraatioiden pohjalta käsin kirjoittamisen sijaan. Automatisoidun mukautumisjärjestelmän toimintaa tarkkailtiin yli vuoden ajan, jona aikana havaittiin yli sata rajapintamäärittelyiden muutosta. Tulokset osoittavat huomattavan vähennyksen suoritusajassa verrattuna edeltäneeseen manuaaliseen prosessiin. Järjestelmän tuotoksissa ei tarkkailuajanjakson aikana havaittu virheitä. Uusi ohjelmistotyökalu testiskenaarioiden luomiseen täyttää sille asetetun tavoitteen. Työkalu mahdollistaa yksinkertaisten testiskenaarioiden luomisen ja konfiguraation graafisessa käyttöliittymässä. Työkalulla tuotetut testikoodit voidaan suorittaa onnistuneesti
APA, Harvard, Vancouver, ISO, and other styles
5

Eada, Priyanudeep. "Experiment to evaluate an Innovative Test Framework : Automation of non-functional testing." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-10940.

Full text
Abstract:
Context. Performance testing, among other types of non-functional testing, is necessary to assess software quality. Most often, manual approach is employed to test a system for its performance. This approach has several setbacks. The existing body of knowledge lacks empirical evidence on automation of non-functional testing and is largely focused on functional testing. Objectives. The objective of the present study is to evaluate a test framework that automates performance testing. A large-scale distributed project is selected as the context to achieve this objective. The rationale for choosing such a project is that the proposed test framework was designed with an intention to adapt and tailor according to any project’s characteristics. Methods. An experiment was conducted with 15 participants at Ericsson R&D department, India to evaluate an automated test framework. Repeated measures design with counter balancing method was used to understand the accuracy and time taken while using the test framework. To assess the ease-of-use of the proposed framework, a questionnaire was distributed among the experiment participants. Statistical techniques were used to accept or reject the hypothesis. The data analysis was performed using Microsoft Excel. Results. It is observed that the automated test framework is superior to the traditional manual approach. There is a significant reduction in the average time taken to run a test case. Further, the number of errors resulting in a typical testing process is minimized. Also, the time spent by a tester during the actual test is phenomenally reduced while using the automated approach. Finally, as perceived by software testers, the automated approach is easier to use when compared to the manual test approach. Conclusions. It can be concluded that automation of non-functional testing will result in overall reduction in project costs and improves quality of software tested. This will address important performance aspects such as system availability, durability and uptime. It was observed that it is not sufficient if the software meets the functional requirements, but is also necessary to conform to the non-functional requirements.
APA, Harvard, Vancouver, ISO, and other styles
6

Amlinger, Hanna. "Application of a New Software Tool for the Automated Test of Automotive Electronic Control Unit Software." Thesis, Linköping University, Department of Electrical Engineering, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-16785.

Full text
Abstract:

Testing plays a very important role for assuring the quality of developed software. In a modern vehicle, more and more of the functionality is controlled by software and the complexity of the software always increases. The expectations on automating the testing process are to save time and to reach an even higher quality.

In this thesis, which was performed at ZF Friedrichshafen AG, a new tool for automated tests is studied. The tool is used for software in the loop simulation based system tests. The user specifies which outputs that shall be observed and which inputs that can be controlled. Based on these prerequisites, test cases are generated.

It has been studied how to apply the tool, how the test case generation can be influenced, on which systems it successfully could be used and which results that could be reached with the tool. The tool has been evaluated on the hand of two real-life examples; the software of an automatic transmission and of a pressure controller, a module of this software. It was found that there are many interesting possibilities to apply the tool in order to support the present testing process.

APA, Harvard, Vancouver, ISO, and other styles
7

Penmetsa, Jyothi Spandana. "AUTOMATION OF A CLOUD HOSTED APPLICATION : Performance, Automated Testing, Cloud Computing." Thesis, Blekinge Tekniska Högskola, Institutionen för kommunikationssystem, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-12849.

Full text
Abstract:
Context: Software testing is the process of assessing quality of a software product to determine whether it matches with the existing requirements of the customer or not. Software testing is one of the “Verification and Validation,” or V&V, software practices. The two basic techniques of software testing are Black-box testing and White box testing. Black-box testing focuses solely on the outputs generated in response to the inputs supplied neglecting the internal components of the software. Whereas, White-box testing focuses on the internal mechanism of the software of any application. To explore the feasibility of black-box and white-box testing under a given set of conditions, a proper test automation framework needs to be deployed. Automation is deployed in order to reduce the manual effort and to perform testing continuously, thereby increasing the quality of the product. Objectives: In this research, cloud hosted application is automated using TestComplete tool. The objective of this thesis is to verify the functionality of cloud application such as test appliance library through automation and to measure the impact of the automation on release cycles of the organisation. Methods: Here automation is implemented using scrum methodology which is an agile development software process. Using scrum methodology, the product with working software can be delivered to the customers incrementally and empirically with updating functionalities in it. Test appliance library functionality is verified deploying testing device thereby keeping track of automatic software downloads into the testing device and licenses updating in the testing device. Results: Automation of test appliance functionality of cloud hosted application is made using TestComplete tool and impact of automation on release cycles is found reduced. Through automation of cloud hosted application, nearly 24% of reduction in level of release cycles can be observed thereby reducing the manual effort and increasing the quality of delivery. Conclusion: Automation of a cloud hosted application provides no manual effort thereby utilisation of time can be made effectively and application can be tested continuously increasing the efficiency and
AUTOMATION OF A CLOUD HOSTED APPLICATION
APA, Harvard, Vancouver, ISO, and other styles
8

Ståhlberg, Povel, and Hannes Persson. "Practical Approach to Developing an Automation Testing Tool." Thesis, Linköpings universitet, Programvara och system, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-149311.

Full text
Abstract:
Manually verifying a software under development can be time consuming because ofits complexity, but also because of frequent updates to different parts of the system. As thesoftware grows larger, a way of verifying the software automatically withoutuser-interaction is a good approach. Verifying a software systematically and automaticallywill both save time for the developers; and assure that the updated version functions asbefore. This report will present a starting point for automatic testing. This is done incooperation with XperDi, a company developing a plug-in for CAD-software thatcurrently verifies their functionality manually. This was achieved by developing a testingtool that support communication between Windows applications used by the plug-in; thiswas needed to automate the testing process. The reached conclusions during this thesisare promising as a starting point for XperDi; to move from manually to automaticverification. There are however several improvements that this report presents for furtherdevelopment of testing tool.
APA, Harvard, Vancouver, ISO, and other styles
9

Bathla, Rajender, and Anil Kapil. "Analytical Scenario of Software Testing Using Simplistic Cost Model." IJCSN, 2012. http://hdl.handle.net/10150/219531.

Full text
Abstract:
Software testing is the process of executing a program with the intention of finding errors in the code. It is the process of exercising or evaluating a system or system component by manual automatic means to verify that it satisfies specified requirements or to identify differences between expected and actual results [4]. Software Testing should not be a distinct phase in System development but should be applicable throughout the design development and maintenance phases. ‘Software Testing is often used in association with terms verification & validation ‘Software testing is the process of executing software in a controlled manner, in order to answer the question: Does the software behave as specified. One way to ensure system‘s responsibility is to extensively test the system. Since software is a system component it requires a testing process also.
Software can be tested either manually or automatically. The two approaches are complementary: automated testing can perform a huge number of tests in short time or period, whereas manual testing uses the knowledge of the testing engineer to target testing to the parts of the system that are assumed to be more error-prone. Despite this contemporary, tools for manual and automatic testing are usually different, leading to decreased productivity and reliability of the testing process. Auto Test is a testing tool that provides a “best of both worlds” strategy: it integrates developers’ test cases into an automated process of systematic contractdriven testing. This allows it to combine the benefits of both approaches while keeping a simple interface, and to treat the two types of tests in a unified fashion: evaluation of results is the same, coverage measures are added up, and both types of tests can be saved in the same format. The objective of this paper is to discuss the Importance of Automation tool with associate to software testing techniques in software engineering. In this paper we provide introduction of software testing and describe the CASE tools. The solution of this problem leads to the new approach of software development known as software testing in the IT world. Software Test Automation is the process of automating the steps of manual test cases using an automation tool or utility to shorten the testing life cycle with respect to time.
APA, Harvard, Vancouver, ISO, and other styles
10

Suwala, Pawel. "Challenges with modern web testing." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-118268.

Full text
Abstract:
The number of web applications continues to grow rapidly. Many applications that were traditionally desktop-based such as word processors, email clients or even file managers have now their web alternatives that often have bigger user base. While the software world is shifting from providing desktop-based applications to offering cloud-based services, challenges arise to provide high quality software in this radically different environment. Web-based applications are different in many aspects to their desktop equivalents. Web-based and desktop-based applications have radically dissimilar architecture, user interface, execution environment, requirements and limitations. To mention a few specific differences: the web application is executed in the context of a web browser, not operating system; code is executed in two separate places: on the server and in the web browser; code for the server is written in a different language than code for the client. Because of these differences, the traditional software testing techniques are only of limited use. To properly test a web application one needs to take into account numerous differences in Web-Browsers such as Internet Explorer, Mozilla Firefox, Google Chrome or Apple Safari. Simple input-output testing is useful only to limited degree, because output cannot be just compared to the predefined value but must be compared within the context of all the environments and operating systems the application supports. The fact that an application works in one browser does not guarantee that it will work at all in other browsers. The entire complexity of the problem makes testing web applications a very time consuming and difficult task. Often it takes significantly longer time to test the application than it is to implement it. Because of these difficulties, web applications are often tested exclusively manually by humans, and only to a limited degree. New techniques and technologies are necessary to approach the problem of web application testing. This paper includes a case study carried out during author’s work on a web-based application. It examines the current state-of-the-art of web application testing and suggests useful techniques in tackling the problem.
APA, Harvard, Vancouver, ISO, and other styles
11

Aksu, Muharrem Ugur. "Environment behavior models for real-time reactive system testing automation." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2006. http://library.nps.navy.mil/uhtbin/hyperion/06Sep%5FAksu.pdf.

Full text
Abstract:
Thesis (M.S. in Computer Science and M.S. in Software Engineering)--Naval Postgraduate School, September 2006.
Thesis Advisor(s): Mikhail Auguston, Man-Tak Shing. "September 2006." Includes bibliographical references (p. 71-). Also available in print.
APA, Harvard, Vancouver, ISO, and other styles
12

Singh, Inderjeet. "A Mapping Study of Automation Support Tools for Unit Testing." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-15192.

Full text
Abstract:
Unit testing is defined as a test activity usually performed by a developer for the purpose of demonstrating program functionality and meeting the requirements specification of module. Nowadays, unit testing is considered as an integral part in the software development cycle. However, performing unit testing by developers is still considered as a major concern because of the time and cost involved in it. Automation support for unit testing, in the form of various automation tools, could significantly lower the cost of performing unit testing phase as well as decrease the time developer involved in the actual testing. The problem is how to choose the most appropriate tool that will suit developer requirements consisting of cost involved, effort needed, level of automation provided, language support, etc. This research work presents results from a systematic literature review with the aim of finding all unit testing tools with an automation support. In the systematic literature review, we initially identified 1957 studies. After performing several removal stages, 112 primary studies were listed and 24 tools identified in total. Along with the list of tools, we also provide the categorization of all the tools found based on the programming language support, availability (License, Open source, Free), testing technique, level of effort required by developer to use tool, target domain, that we consider as good properties for a developer to make a decision on which tool to use. Additionally, we categorized type of error(s) found by some tools, which could be beneficial for a developer when looking at the tool’s effectiveness. The main intent of this report is to aid developers in the process of choosing an appropriate unit testing tool from categorization table of available tools with automation unit testing support that ease this process significantly. This work could be beneficial for researchers considering to evaluate efficiency and effectiveness of each tool and use this information to eventually build a new tool with the same properties as several others.
APA, Harvard, Vancouver, ISO, and other styles
13

Muval, Sérgio Fernando José. "Soluções globais para sistemas industriais-teste de software." Master's thesis, Instituto Politécnico de Setúbal. Escola Superior de Ciências Empresariais, 2016. http://hdl.handle.net/10400.26/14191.

Full text
Abstract:
Relatório de estágio apresentada para cumprimento dos requisitos necessários à obtenção do grau de Mestre em Sistemas de Informação Organizacionais
O presente relatório surge no âmbito do estágio do curso de Mestrado em Sistemas de Informação Organizacionais. O estágio foi realizado na empresa Mind software, SA., num período de 9 meses, que teve como objetivo proporcionar um contacto direto e continuado com o exercício profissional desenvolvido, a capacidade de inserção profissional, o relacionamento interpessoais no contexto real de trabalho, bem como a capacidade de refletir sobre as experiencias proporcionadas como forma de aprendizagem. Durante período de estágio, o estagiário trabalhou diretamente com a equipa de desenvolvimento e manutenção de software da unidade de Sistemas Industriais e teve como objetivo detetar bugs nas aplicações e transmiti-los à restante equipa para que fossem resolvidos e dessa forma, melhorar a robustez dos produtos. Durante estes nove meses o estagiário teve de aprender a funcionalidade de programas que se destinam à indústria do calçado, pois para ser possível realizar os testes corretamente é necessário conhecer a fundo cada uma das aplicações. Realizou-se planos de testes, testes manuais e automatização de testes aplicacionais, que consistiu na realização de testes funcionais, testes não funcionais, testes de regressão e teste de usabilidade sobre a aplicação MindCut nas configurações Twin, Small e Large, com a utilização da ferramenta de automatização TestComplete10 e posteriormente o TestComplete11. Antes de dar início aos testes das aplicações foi feita uma introdução aos produtos. Após isso foi necessário fazer uma leitura exaustiva aos manuais das aplicações MinCAD 3D, MindCAD 2D, MindGest e MindCut. Posteriormente foram realizados os cadernos de testes, os testes e automatização com a utilização do TestComplete10 e posteriormente TestComplete11. Durante estas tarefas todos os bugs encontrados foram colocados na plataforma de colaboração TFS (Team Foundation Server) para o devido tratamento na equipa de desenvolvimento. A automatização dos testes aplicacionais teve por parte da organização um acompanhamento constante, pois com o planeamento existente para equipa de desenvolvimento e na tentativa de responder de forma ágil ao cliente, torna-se necessário poder executar os testes das aplicações de forma automática, poupando tempo e trabalho a quem realiza essas tarefas. Após a automatização dos testes, seguiu-se a análise crítica dos resultados gerados pela plataforma de testes Testcomplete. Foi feita uma reflexão da mesma sobre o benefício da plataforma de testes automáticos para empresa e para aplicação MindCut. Percebendo a importância do trabalho em equipa, a partilha de informação e comunicação entre os membros da equipa. Em seguida foram analisados mais profundamente os módulos realizados e os cadernos de testes para procederem à sua execução, os respetivos processos contribuiu significativamente na melhoria da aplicação, na redução significativa em termos de tempo de execução de testes.
This report comes in the Master's course in stage Organizational Information Systems. The stage was held in the company Mind software, SA., a period of nine months, which aimed to provide a direct contact and continued with the professional practice developed, the employability, the interpersonal relationship in a real work environment, as well as the ability to reflect on the experiences provided as a way to learning. During the probationary period, the trainee worked directly with the development team and Industrial Systems unit of software maintenance and aimed to detect bugs in the applications and forward them to the rest of the team to be solved and thus improve the robustness of products. During these nine months the trainee had to learn the functionality of programs that are intended for footwear industry as to be able to perform the tests correctly is necessary to know the background each application. Held flat testing, manual testing and automation of application tests, which consisted in performing functional tests, no functional test, regression test and usability test on MindCut application in twin configurations, Small and Large, with the use of TestComplete10 automation tool and then the TestComplete11. Before beginning the tests of applications was an introduction to the products. After it was necessary to make a thorough reading to manual application MinCad 3D, 2D MindCad, MindGest and MindCut. Subsequently the rolls were performed tests, tests and automation with the use of TestComplete10 and then TestComplete11. During these tasks all found bugs were placed in TFS collaboration platform (Team Foundation Server) for proper treatment in the development team. The automation of applicational tests had by the organization constant monitoring, as with the existing planning to development team and attempt to answer customer agile manner, it is necessary to be able to run the tests of automatic applications, saving time and work to who performs these tasks. After the automation of tests, followed by a critical analysis of the results generated by TestComplete test platform. A reflection of the same on the benefit of automated testing platform for the company and MindCut application was made. Realizing the importance of teamwork, information sharing and communication among team members. Then they were analyzed further the realized modules and notebooks testing to proceed to its implementation, the respective processes contributed significantly to the improvement of the application in a significant reduction in terms of test execution time.
APA, Harvard, Vancouver, ISO, and other styles
14

Čecháková, Lucie. "Automatizace regresního testování." Master's thesis, Vysoká škola ekonomická v Praze, 2015. http://www.nusl.cz/ntk/nusl-203822.

Full text
Abstract:
This study is primarily focused on software testing, especially on regression tests and their automation. The main objective is to introduce and verify a novel procedure for implementation and automation of software regression testing. Specific objectives include putting regression testing into the context of other types of tests applied to software testing, introduction of a novel Methodology for analysis of automation of regression tests, introduction of a novel Methodology for analysis of implementation of regression tests, practical verification of the applicability of both methodologies on a real project and a suggestion of how to adapt these methodologies on the basis of practical usage. The theoretical part of this study summarizes the basic theory of software testing, decomposing it in detail, and introducing its various levels, types and categories. It also presents the field of test automation, explains its advantages and disadvantages and introduces an overview of test types, which are generally recommended for automation. More attention is paid to regression testing and its prerequisites and potential for automation. The practical part of this study consists of the proposition of two methodologies, explaining their usage in a particular practical project and focuses on the evaluation of success of practical utilization of both methodologies. Based on this evaluation, these methodologies are consequently extended. Outputs of the study are also extended variants of Methodology for analysis of automation of regression tests and Methodology for analysis of implementation of regression tests, which are available for usage on other practical projects.
APA, Harvard, Vancouver, ISO, and other styles
15

Collins, Eliane Figueiredo. "Modelo de automação de testes funcionais para desenvolvimento ágil de software." Universidade Federal do Amazonas, 2013. http://tede.ufam.edu.br/handle/tede/3295.

Full text
Abstract:
Made available in DSpace on 2015-04-22T22:00:48Z (GMT). No. of bitstreams: 1 Eliane Figueiredo Collins.pdf: 2314673 bytes, checksum: 8403bd67cffed913ac9029447401f980 (MD5) Previous issue date: 2013-04-25
CAPES - Coordenação de Aperfeiçoamento de Pessoal de Nível Superior
For some time, the professional software development companies are looking for new technical alternatives in order to optimize their processes, to deliver products to market as soon as possible and to meet customer expectations, increasingly demanding and intolerant of software failures. In this sense, the agile software development is gaining more space and consequently the software testing area which was previously considered a separate phase of development has changed over time to adapt to this new reality. The test automation activity is seen as key of agile development, but many teams still don t know how it should be done, who should take responsibility and run it and the correct procedures for this activity to be successful. Although the literature mentions about the particularities activities and best practices in this scenario, there are few related works and lack of experience reports or case studies that show, in practice, examples of use this from start to finish the automation strategy adopted. This paper aims to contribute to improving the quality of agile processes, and proposes an approach that involves the application of agile manifesto values in the activities of test automation, which can be used regardless of agile methodology adopted. In this study, observations were made on empirical about testing practices in agile projects developed at Nokia Technology Institute (INdT) and an experimental implementation of this approach at the Center for Electronic and Information Technology (CETELI), Federal University of Amazonas (UFAM). Experimental reports are available with different strategies for the automation of software testing and identification of some important issues to deal with difficulties in adapting testers and developers in this new scenario.
Há algum tempo as empresas desenvolvedoras de software profissional vêm buscando novas alternativas técnicas com o objetivo de otimizar seus processos, entregar produtos para o mercado o mais cedo possível e ainda atender as expectativas dos clientes cada vez mais exigentes e intolerantes a falhas de software. Com isso, as metodologias ágeis de desenvolvimento de software estão ganhando mais espaço e consequentemente a área de testes de software que antes era considerada uma fase separada do desenvolvimento vem passando por mudanças para se adaptar a esta nova realidade. A atividade de automação de teste passou a ser vista como peça chave para o desenvolvimento ágil, porém muitas equipes ainda não sabem como ela deve ser feita, quem deve assumir a responsabilidade e execução dela e os procedimentos para que essa atividade seja bem sucedida. Embora a literatura mencione particularidades sobre as atividades realizadas e as melhores práticas nesse cenário, são poucos os trabalhos relacionados e há falta de relatos de estudos de caso ou exemplos de utilização que mostrem, na prática, do início ao fim, a estratégia de automação adotada. Este trabalho tem como objetivo contribuir para a melhoria da qualidade dos processos ágeis, propondo uma abordagem que envolve a aplicação de valores presentes no manifesto ágil nas atividades de automação de teste, que podem ser utilizadas independentemente da metodologia ágil adotada. Nesta pesquisa, foram realizadas observações empíricas sobre as práticas de testes em projetos ágeis desenvolvidos no Instituto Nokia de Tecnologia (INdT) e um experimento de aplicação dessa abordagem no Centro de Tecnologia Eletrônica e da Informação (CETELI), da Universidade Federal do Amazonas (UFAM). São disponibilizados relatos experimentais com diferentes estratégias relativas a automação de teste de software e a identificação de algumas questões importantes para lidar
APA, Harvard, Vancouver, ISO, and other styles
16

Wiklund, Kristian. "Impediments for Automated Software Test Execution." Doctoral thesis, Mälardalens högskola, Inbyggda system, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-27830.

Full text
Abstract:
Automated software test execution is a critical part of the modern software development process, where rapid feedback on the product quality is expected. It is of high importance that impediments related to test execution automation are prevented and removed as quickly as possible. An enabling factor for all types of improvement is to understand the nature of what is to be improved. The goal with this thesis is to further the knowledge about common problems encountered by software developers using test execution automation, in order to enable improvement of test execution automation in industrial software development. The research has been performed through industrial case studies and literature reviews. The analysis of the data have primarily been performed using qualitative methods, searching for patterns, themes, and concepts in the data.  Our main findings include: (a) a comprehensive list of potential impediments reported in the published body of knowledge on test execution automation, (b) an in-depth analysis of how such impediments may affect the performance of a development team, and (c) a proposal for a qualitative model of interactions between the main groups of phenomena that contribute to the formation of impediments in a test execution automation project. In addition to this, we contribute qualitative and quantitative empirical data from our industrial case studies.  Through our results, we find that test execution automation is a commonly under-estimated activity,  not only in terms of resources but also in terms of the complexity of the work. There is a clear tendency to perform the work ad hoc, down-prioritize the automation in favor of other activities,  and ignore the long-term effects in favor of short-term gains. This is both a technical and a cultural problem that need to be managed by awareness of the problems that may arise, and also have to be solved in the long term through education and information. We conclude by proposing a theoretical model of the socio-technical system that needs to be managed to be successful with test execution automation.
Syftet med denna avhandling är att utöka den vetenskapliga kunskapen om problem som kan uppstå under användning av automatiserad testning i industriell programvaruutveckling. Utveckling av programvara består principiellt av ett antal processteg: kravbehandling, detaljerad systemkonstruktion, implementation i form av programmering, och slutligen testning som säkerställer att kvaliteten på programvaran är tillräcklig för dess tilltänkta användare. Testning representerar en stor del av tiden och kostnaden för utveckling av programvaran, och detta gör att det är attraktivt att automatisera testningen. Automatiserade tester kan bidra med många positiva effekter. Testning som utförs om och om igen, för att säkerställa att gammal funktionalitet inte slutar att fungera när ändringar görs i programvaran, kan med fördel göras automatiserat. Detta frigör kvalificerad personal till kvalificerat arbete. Automatisering kan även minska ledtiden för testningen och därmed möjliggöra snabbare leveranser till kund. Ett annat mål med testautomatisering är att vara säker på att samma tester utförs på ett likartat sätt varje gång produkten testas, så att den håller en jämn och stabil kvalitetsnivå. Automatiserad testning är dock en mer komplex och kostsam verksamhet än vad man kan tro, och problem som uppstår under dess användning kan ha stora konsekvenser. Detta gäller i ännu större utsträckning i organisationer som använder moderna utvecklingsmetoder där automatisering är grundstenen för en effektiv kvalitetskontroll. För att kunna undvika så många problem som möjligt, är det därför mycket viktigt att förstå vad som händer när man använder testautomatisering i stor skala. Denna avhandling presenterar resultat från fallstudier i svensk industri, som, kombinerat med en systematisk genomgång av befintlig forskning inom området, har utförts för att söka djupare kunskap och möjligheter till generalisering. Arbetet har varit beskrivande, och förklarande, och bygger på empirisk forskningsmetodik.  I avhandlingen bidrar vi med (a) information om de problem relaterade till automatiserad testning som vi har identifierat i de empiriska fallstudierna, (b) en diskussion av dessa problem i relation till andra studier i området, (c) en systematisk litteraturstudie som ger en översikt över relevanta publikationer i området, (d) en analys av bevisen som insamlats genom litteraturstudien, samt (e) en modell av det organisatoriska och tekniska system som måste hanteras för att man skall nå framgång med ett testautomatiseringsprojekt. Resultaten tyder på att rent tekniska problem inte utgör huvuddelen av de problem som upplevs med testautomatisering. Istället handlar det till stora delar om organisationell dynamik: hantering av förändringen det innebär att införa automatisering, planering av automatisering och dess användning, samt vilka finansiella förväntningar man har på automatiseringen.
ITS-EASY Post Graduate School for Embedded Software and Systems
APA, Harvard, Vancouver, ISO, and other styles
17

Saff, David 1976. "Automatic continuous testing to speed software development." Thesis, Massachusetts Institute of Technology, 2004. http://hdl.handle.net/1721.1/30096.

Full text
Abstract:
Thesis (S.M.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2004.
Includes bibliographical references (p. 147-152).
Continuous testing is a new feature for software development environments that uses excess cycles on a developer's workstation to continuously run regression tests in the background, providing rapid feedback about test failures as source code is edited. It is intended to reduce the time and energy required to keep code well-tested, and to prevent regression errors from persisting uncaught for long periods of time. The longer that regression errors are allowed to linger during development, the more time is wasted debugging and fixing them once they are discovered. By monitoring and measuring software projects, we estimate that the wasted time, consisting of this preventable extra fixing cost added to the time spent running tests and waiting for them to complete, accounts for 10-15% of total development time. We present a model of developer behavior that uses data from past projects to infer developer beliefs and predict behavior in new environments -in particular, when changing testing methodologies or tools to reduce wasted time. This model predicts that continuous testing would reduce wasted time by 92-98%, a substantial improvement over other approaches we evaluated, such as automatic test prioritization and changing manual test frequencies. A controlled human experiment indicates that student developers using continuous testing were three times more likely to complete a task before the deadline than those without, with no significant effect on time worked.
(cont.) Most participants found continuous testing to be useful and believed that it helped them write better code faster. 90% would recommend the tool to others. We show the first empirical evidence of a benefit from continuous compilation, a popular related feature. Continuous testing has been integrated into Emacs and Eclipse. We detail the functional and technical design of the Eclipse plug-in, which is publicly beta-released.
by David Saff.
S.M.
APA, Harvard, Vancouver, ISO, and other styles
18

Grape, Victor. "Comparing Costs of Browser Automation Test Tools with Manual Testing." Thesis, Linköpings universitet, Programvara och system, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-133170.

Full text
Abstract:
Testing is a necessary component of software development, but it is also an expensive one, especially if performed manually. One way to mitigate the cost of testing is to implement test automation, where the test cases are run automatically. For any organisation looking to implement test automation, the most interesting cost is time. Automation takes time to implement and one of the most obvious benefits of automation is that the automated test execution time is lower than that of manual execution. This thesis contains a literature study covering testing methodology, especially in regards to the domain of web application testing. The literature covered also included three economic models that may be used to calculate the costs of automation compared to manual testing. The models can be used to calculate the time it would take, or the number of necessary executions, for the total cost of test automation to be lower than of that of manual testing. The thesis is based on a case study of test automation for the StoredSafe platform, a web application. Three sets of test automation frameworks were used to implement three different test suits and the test implementation times were collected. The data collected were then used to calculate the time it would take, using the three economic models, for the cost of automated test cases to become equal to that of with manual testing. The data showed that the estimated time to reach breakeven for the three frameworks varied between 2½ and at worst 10 years, with an average of 3½ years. The models and data presented in this thesis may be used in order to estimate the cost of test automation in comparison to manual testing over longer periods of time, but care must be taken in order to ensure that the data used is correct in regards to one’s own organisation or else the estimate may be faulty.
APA, Harvard, Vancouver, ISO, and other styles
19

Hrozek, Jakub. "Penetrační testování open-source software." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2010. http://www.nusl.cz/ntk/nusl-237145.

Full text
Abstract:
This thesis discusses the design and implementation of integrated penetration testing system. In the first two chapters, the reader is introduced to the topic of penetration testing. The basic techniques and classification of tests are described as well as some of the most widely used methodologies. It also discusses the need to automate the testing process. The fifth and sixth chapter discuss specification and detailed design of integrated penetration testing tool. Its implementation and the problems that had arisen during the process are the theme of chapter seven. The last part of the thesis describes practical experiments done with the tool and gives the reader some advice on securing computer networks.
APA, Harvard, Vancouver, ISO, and other styles
20

Shrivatri, Ankit. "Selection and implementation of test framework for automated system test of mobile application." Master's thesis, Universitätsbibliothek Chemnitz, 2016. http://nbn-resolving.de/urn:nbn:de:bsz:ch1-qucosa-202553.

Full text
Abstract:
Software Quality is a key concern for any companies working with software development. This is true due to the fact that the success of any software directly depends on Quality of software. It is expected that the software is of best quality for a long duration of time. With the introduction of Mobile applications the task of maintaining the quality of an application has been difficult and have faced many challenges. Many companies working with mobile application have reformed their process in order to maintain the quality of their application. The introduction of Automation testing in the test process is one such reform that have changed the face of mobile application testing in today’s world. This work deals with the concepts of Automation System testing for the mobile application which is until now a new thing and it has many things yet to be explored. The approach to automation testing is simple yet unique for the department of PT-MT/Quality Management in Robert Bosch GmbH based in Leinfelden, Stuttgart. Over here a selection and implementation of a test framework will be done for Automation testing of the mobile Applications that are being developed. For this a requirement specification document is being created which will form the basis for selecting a framework from the KT Analysis table. Finally, a framework TestComplete will be implemented for the already developed application "PLR measure&go" The implementation will include all the procedure required to set up the test framework as a part of documentation. The framework TestComplete will be used to create System test for iOS and Android operation system. Lastly the execution of test and the Result reporting is being shown as a complete process for Automation testing.
APA, Harvard, Vancouver, ISO, and other styles
21

Frykman, Daniel, and Henrik Wemmersten. "Automation of Electrical Fault Induction for Safety Testing of the Power Train Software in Heavy Vehicles." Thesis, KTH, Maskinkonstruktion (Inst.), 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-141656.

Full text
Abstract:
En av de främsta prioriteringarna vid utveckling av mjukvara till tunga lastbilar på Scania är att verifiera att lastbilens beteende är säkert. Således spenderas mycket tid på säkerhetstester vars syfte är att verifiera att ny mjukvara inte medför säkerhetskritiska förändringar i fordonets beteende. De säkerhetstester som behandlas i rapporten testar beteendet av mjukvaran i motorns styrenhet när den utsätts för elektriska fel. Bakgrunden till varför säkerhetstesterna genomförs beskrivs i ett säkerhetskritiskt och juridiskt perspektiv samt vilken testmetodik som används. Dessutom tydliggörs vilken del av utvecklingsprocessen som testerna genomförs i. Slutligen utvecklas ett automatiskt testsystem för att effektivisera samt höja kvalitén av säkerhetstesterna som genomförs på Scania. De elektriska fel som kan induceras med det automatiska testsystemet är kortslutning avstyrenhetens kablage mot lastbilens batteri samt kabelbrott. Resultaten ifrån tester genomförda på det automatiska testsystemet visar att säkerhetstesterna utförda manuellt respektive automatiskt är ekvivalenta. Vidare så minskar exekveringstiden för ett testfall signifikant samt att valideringsmöjligheterna förbättras genom bättre dokumentation och ökad repeterbarhet.
In the development of software for heavy-duty trucks at Scania one of the main priorities is to ensure that the behavior of the truck is safe. Hence, much time is spent on safety tests where the purpose is to verify that new software does not imply safety critical changes in the behavior of the vehicle. The safety tests treated in this thesis are about testing the reliability of thesoftware in the electronic control unit while it is exposed to electrical malfunctions.The background of why the safety tests are performed is describedin a legal and safety critical perspective and also what test methodology thatis used. Further the phase in which the safety tests are carried out in thedevelopment process is highlighted.Finally, an automated test system is developed for increasing the e-ciency as well as the quality of the safety tests performed at Scania. Theelectrical malfunctions that are possible to induce with the automated test system are short-circuiting to battery of the truck and disconnections. The results from the tests performed on the automated test system indicate that the safety tests that are performed manually respectively automatically are equivalent. Further, the results show that the time to perform the tests signicantly decreases and the possibility for validation is improved through better documentation and increased repeatability.
APA, Harvard, Vancouver, ISO, and other styles
22

Sarala, Devi Krishna. "Hardware and software integration and testing for the automation of bright-field microscopy for tuberculosis detection." Master's thesis, University of Cape Town, 2011. http://hdl.handle.net/11427/11360.

Full text
Abstract:
Automated microscopy for the detection of tuberculosis (TB) in sputum smears would reduce the load on technicians, especially in countries with a high TB burden. This dissertation reports on the development and testing of an automated system built around a conventional microscope for the detection of TB in Ziehl-Neelsen (ZN) stained sputum smears. Microscope auto-focusing, image analysis and stage movement were integrated. Images were captured at 40x magnification.
APA, Harvard, Vancouver, ISO, and other styles
23

Fu, Jiangbiao, and Jiaqi Song. "Model-based Testing of supporting testing of PAC based controlling systems in industrial plants - A case study in printing plants." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-16753.

Full text
Abstract:
Context. Testing is a very critical process to evaluate whether a related function is correctly implemented in the control system. There is an upward trend to using PAC based control system in the automation production context. However, currently, most testing of PAC based controlling system is in manual testing, which has low efficiency and high complexity. Furthermore, there has been little research on the systematic testing of PAC in an industry environment. Objectives. Due to this problem, this study is to investigate whether a model-based testing method can overcome the challenge of manual testing and improve the testing effectiveness in PAC based controlling system. Methods. We use three steps to achieve the objective, and the first one is to implement a systematic mapping study to find existing model-based testing method that is using in the industrial area, what the process and the context. The second one is to implement a case study in a printing house, to see what the real challenge of manual testing, the third one is to find if exist MBT method could be used under such context to overcome challenges. Results. Through mapping study and case study, we found there are many testing methods and implement under diverse context, but none of them focus on the PAC based controlling system. And we found there exist MBT that also can be used in PAC based controlling system to mitigate some manual testing challenges. Conclusions. In our thesis, we implement a mapping study from 38 papers to collect data for existing model-based testing methods to have a deep understanding of this area. We found there are five main contexts that MBT are usually being used and we extract implement process and advantages and disadvantages for MBT methods which value to practitioners and researchers. And we conducted a case study in a printing house in Switzerland to observe the challenges of manual testing of PAC based controlling system. We found one exist MBT method that can be used in our context that makes the test case generation step more effective. And we proposed a simulation testing model that hopefully can address all the manual testing challenges by combined with the exist MBT method.
APA, Harvard, Vancouver, ISO, and other styles
24

Dalal, Malay A. "An object-oriented simulation-based method for emulation development for testing shop control software." Diss., This resource online, 1996. http://scholar.lib.vt.edu/theses/available/etd-06062008-151722/.

Full text
APA, Harvard, Vancouver, ISO, and other styles
25

Panáková, Pavla. "Návrh a implementace automatizace testování v softwarovém vývoji." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2021. http://www.nusl.cz/ntk/nusl-444605.

Full text
Abstract:
This Master’s thesis deals with the introduction of the testing process into the information department of IREKS ENTYMA s.r.o. In this thesis is firstly introduced the theoretical foundation necessary for the understanding of this topic and subsequently is analysed the current state of the company with an emphasis on the software testing. The third part of the thesis focuses on the selection of the testing automation and its implementation, which is described using the techniques of project management.
APA, Harvard, Vancouver, ISO, and other styles
26

Marinov, Darko 1976. "Automatic testing of software with structurally complex inputs." Thesis, Massachusetts Institute of Technology, 2005. http://hdl.handle.net/1721.1/30161.

Full text
Abstract:
Thesis (Ph. D.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2005.
Includes bibliographical references (p. 123-132).
Modern software pervasively uses structurally complex data such as linked data structures. The standard approach to generating test suites for such software, manual generation of the inputs in the suite, is tedious and error-prone. This dissertation proposes a new approach for specifying properties of structurally complex test inputs; presents a technique that automates generation of such inputs; describes the Korat tool that implements this technique for Java; and evaluates the effectiveness of Korat in testing a set of data-structure implementations. Our approach allows the developer to describe the properties of valid test inputs using a familiar implementation language such as Java. Specifically, the user provides an imperative predicate--a piece of code that returns a truth value--that returns true if the input satisfies the required property and false otherwise. Korat implements our technique for solving imperative predicates: given a predicate and a bound on the size of the predicate's inputs, Korat automatically generates the bounded-exhaustive test suite that consists of all inputs, within the given bound, that satisfy the property identified by the predicate. To generate these inputs, Korat systematically searches the bounded input space by executing the predicate on the candidate inputs. Korat does this efficiently by pruning the search based on the predicate's executions and by generating only nonisomorphic inputs. Bounded-exhaustive testing is a methodology for testing the code on all inputs within the given small bound.
(cont.) Our experiments on a set of ten linked and array- based data structures show that Korat can efficiently generate bounded-exhaustive test suites from imperative predicates even for very large input spaces. Further, these test suites can achieve high statement, branch, and mutation coverage. The use of our technique for generating structurally complex test inputs also enabled testers in industry to detect faults in real, production-quality applications.
by Darko Marinov.
Ph.D.
APA, Harvard, Vancouver, ISO, and other styles
27

Gawell, Anders, and Anton Kallin. "Teaching software testing in a modern development environment." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-261162.

Full text
Abstract:
All developers understand the benefits of testing their code to ensure its functionality. Today’s market is moving further towards design principles where testing is a central or driving force during development. This puts a certain pressure on academia to supply these skills to their students.Recently the course II1302 Projects and project methods at the Royal Institute of Technology in Kista made a concerted effort to introduce the students of the course to these modern concepts. This thesis investigates how areas of testing can effectively be introduced to the students in the course, utilizing a tailored example that takes the area of testing into particular consideration and how to automate it via DevOps-tools provided by a cloud-based service. Further, it also makes an attempt to provide additional material to be used for teaching testing in conjunction with the example provided.The case study covers the development of an example application, meant to mirror a typical student project. It also covers how this was used for teaching the students about the testing areas considered. The covered testing areas include unit testing, integration testing and UI testing. With these given testing areas, the application and an associated learning module was developed for each area in question. Relevant standards, strategies and approaches was also identified for each of these areas.The thesis also presents important properties to take into consideration when developing similar examples in the future, based on the experiences obtained during the study. These include needs such as understandable by inexperienced students, applicability outside the course, adherence to established standards, tools that are simple to use and an architectural structure that allows for testing.Some improvements are also recommended: the students would benefit from learning software testing from an early stage of their studies. The content of the learning modules should also be brought to the students earlier in the course, so it can be applied in their projects at an early stage as well.Further research is also recommended to evaluate the suitability of using other cloud-based environments instead, and to evaluate the applicability of the learning modules for students of varying disabilities.
Alla utvecklare förstår fördelarna med att testa kod för att garantera dess funktionalitet. Dagens industri går i en riktning där testning spelar en central del av design under utveckling av mjukvara. Denna tendens lägger en viss press på högskolan att lära ut dessa erfarenheter till dess studenter.På senare tid har kursen II1302 Projekt och projektmetoder på Kungliga Tekniska Högskolan i Kista tagit en stor ansats för att introducera sina studenter inför dessa moderna koncept. Denna uppsats undersöker hur testningsområdet effektivt kan introduceras till studenterna inom denna kurs, genom att utnyttja ett egengjort exempel som har området i fokus, samt att automatisera detta via DevOps-verktyg tillhandahållna av molnbaserade tjänster. Dessutom görs även en ansats för att tilldela ytterligare material som kan användas för att lära ut testning av mjukvara i samband med det givna exemplet.Fallstudien omfattar utvecklingen av en exempelapplikation, som var avsedd att likna ett typiskt studentprojekt. Den täcker även hur denna användes för att lära ut de betraktade testningsområdena till studenterna. De täckta områdena av testning inkluderar enhetstestning, integrationstestning och testning av användargränssnitt. Med dessa givna testningsområden utvecklades både applikationen och dess associerade lärmoduler för vardera testningområde i fråga. Relevanta standarder, strategier och metoder var också identifierade för vardera av dessa områden.Denna uppsats presenterar även ett antal viktiga egenskaper att hålla i åtanke vid utveckling av liknande exempel i framtiden, baserat på erfarenheterna från studien. Detta inkluderar behov som tillgänglighet för mindre erfarna studenter, applicerbarhet utanför själva kursen, tillämpning av etablerade standarder, utnyttjande av lättanvända verktyg och en arkitektur som tillåter testning.Några förbättringar föreslås även: studenterna skulle gynnas av att lära sig om mjukvarutestning i ett tidigt skede av sina studier. Innehållet i lärmodulerna bör även presenteras för studenterna tidigare i kursen för att kunna appliceras i deras projekt.Ytterligare forskning rekommenderas även för att utvärdera andra lämpliga molnbaserade miljöer, samt för att utvärdera tillämpbarheten av lärmodulerna hos studenter med inlärningssvårigheter.
APA, Harvard, Vancouver, ISO, and other styles
28

Lindahl, Eric. "Pimp My Test Process : Introducing Test Automation and Process Maturity in an IT Consulting Context." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-76867.

Full text
Abstract:
Ipendo Systems in Linköping, Sweden, is a small IT consulting firm developing among other things custom portal applications based on Microsoft Sharepoint 2010. The purpose of this thesis is to investigate whether the test tools TestComplete and LoadComplete provide sufficient compatibility for functional and non-functional testing of Ipendo Systems’ Sharepoint based applications, as well as design testing related activities to be incorporated into their existing software development framework. A test process maturity framework was chosen and applied for the design of the testing activities, while the test tool investigation resulted in guidelines on how to apply the tools effectively and circumvent any issues discovered.
APA, Harvard, Vancouver, ISO, and other styles
29

Aziz, Yama. "Exploring a keyword driven testing framework : a case study at Scania IT." Thesis, Uppsala universitet, Avdelningen för datalogi, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-326139.

Full text
Abstract:
The purpose of this thesis is to investigate organizational quality assurance through the international testing standard ISO 29119. The focus will be on how an organization carries out testing processes and designs and implements test cases. Keyword driven testing is a test composition concept in ISO 29119 and suitable for automation. This thesis will answer how keyword driven testing can facilitate the development of maintainable test cases and support test automation in an agile organization. The methodology used was a qualitative case study including semi-structured interviews and focus groups with agile business units within Scania IT. Among the interview participants were developers, test engineers, scrum masters and a unit manager. The results describe testing practices carried out in several agile business units, maintainability issues with test automation and general ideas of how test automation should be approached. Common issues with test automation were test cases failing due to changed test inputs, inexperience with test automation frameworks and lack of resources due to project release cycle. This thesis concludes that keyword driven testing has the potential of solving several maintainability issues with test cases breaking. However, the practicality and effectiveness of said potential remain unanswered. Moreover, successfully developing an automated keyword driven testing framework requires integration with existing test automation tools and considering the agile organizational circumstances.
APA, Harvard, Vancouver, ISO, and other styles
30

Westberg, Martin. "TestLink : Software for connecting laboratory equipment and automation of workflow." Thesis, Karlstads universitet, Fakulteten för hälsa, natur- och teknikvetenskap (from 2013), 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:kau:diva-34962.

Full text
Abstract:
Software development is of great significance in manufacturing and process industry. Software can, for example, make production more efficient and monitoring easier. In paperboard industry testing the product, that is, paperboard, is important. Testing is done to make sure that the product meets the requirements of the customers who transform the paperboard to packaging products. In the Skoghall paperboard Mill operators make use of a range of different test methods. Since the work pace is high and the product is being continuously tested improvements of the workflow at the laboratory are always of interest.   The aim of this project is to develop a program that connects test instruments at Skoghall Mill’s test laboratory to the Mill’s network. The motivation is to automate part of the work process by removing the step of manually reading measurement values from the test instruments. The scope of this project includes developing software that connects one of the instruments (the Short Span Compression tester [1] or SCT) at the laboratory to the Mill’s network. This program, named TestLink, will work as a proof of concept for connecting instruments using a common interface. The software is constructed using a modular approach forming a platform where an additional instrument can be connected by creating a new module. The software is developed in Visual Studio using C# as the programming language. The software architecture follows the MVVM [2] (Model View ViewModel) design pattern paradigm and WPF [3] (Windows Presentation Foundation) is used to construct the graphical user interface. The result shows that time savings can be made when automating part of the work with the introduction of new software.
APA, Harvard, Vancouver, ISO, and other styles
31

Kurin, Erik, and Adam Melin. "Data-driven test automation : augmenting GUI testing in a web application." Thesis, Linköpings universitet, Programvara och system, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-96380.

Full text
Abstract:
For many companies today, it is highly valuable to collect and analyse data in order to support decision making and functions of various sorts. However, this kind of data-driven approach is seldomly applied to software testing and there is often a lack of verification that the testing performed is relevant to how the system under test is used. Therefore, the aim of this thesis is to investigate the possibility of introducing a data-driven approach to test automation by extracting user behaviour data and curating it to form input for testing. A prestudy was initially conducted in order to collect and assess different data sources for augmenting the testing. After suitable data sources were identified, the required data, including data about user activity in the system, was extracted. This data was then processed and three prototypes where built on top of this data. The first prototype augments the model-based testing by automatically creating models of the most common user behaviour by utilising data mining algorithms. The second prototype tests the most frequent occurring client actions. The last prototype visualises which features of the system are not covered by automated regression testing. The data extracted and analysed in this thesis facilitates the understanding of the behaviour of the users in the system under test. The three prototypes implemented with this data as their foundation can be used to assist other testing methods by visualising test coverage and executing regression tests.
APA, Harvard, Vancouver, ISO, and other styles
32

Kahlström, Joakim, and Johan Hedlin. "Automating software installation for cyber security research and testing public exploits in CRATE." Thesis, Linköpings universitet, Databas och informationsteknik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-177401.

Full text
Abstract:
As cyber attacks are an ever-increasing threat to many organizations, the need for controlled environments where cyber security defenses can be tested against real-world attacks is increasing. These environments, called cyber ranges, exist across the world for both military and academic purposes of various scales. As the function of a cyber range involves having a set of computers, virtual or physical, that can be configured to replicate a corporate network or an industrial control system, having an automated method of configuring these can streamline the process of performing different exercises. This thesis aims to provide a proof of concept of how the installation of software with known vulnerabilities can be performed and examines if the software is vulnerable directly after installation. The Cyber Range And Training Environment (CRATE) developed by the Swedish Defence Research Agency (FOI) is used as a testbed for the installations and FOI-provided tools are used for launching automated attacks against the installed software. The results show that installations can be performed without Internet access and with minimal network traffic being generated and that our solution can rewrite existing software packages from the package manager Chocolatey to work with an on-premises repository with an 85% success rate. It is also shown that very few publicly available exploits succeed without any manual configuration of either the exploit or the targeted software. Our work contributes to making it easier to set up environments where cyber security research and training can be conducted by simplifying the process of installing vulnerable applications.
APA, Harvard, Vancouver, ISO, and other styles
33

Rungta, Neha Shyam. "Guided Testing for Automatic Error Discovery in Concurrent Software." Diss., CLICK HERE for online access, 2009. http://contentdm.lib.byu.edu/ETD/image/etd3175.pdf.

Full text
APA, Harvard, Vancouver, ISO, and other styles
34

Kajan, Miroslav. "Metody a organizace testování software." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2015. http://www.nusl.cz/ntk/nusl-235007.

Full text
Abstract:
This document's objective is to propose a set of methods for improvement of the organization and methodology of software testing and subsequent application of those in a real environment of the Siemens CZ company. The first part discusses the development models in terms of testing segment and the following section focuses specifically on the methodology of agile testing and development as a whole, including applicable metrics for evaluating various aspects of software exiting the testing phase. The third major section lets the reader get acquainted with the Siemens organization and methods of their software testing and by analyzing real-world project it assesses the strengths and weaknesses of the particular testing process and its management. The practical part of this thesis lies in the design and implementation of a plug-in for the JIRA environment. This tool is able to identify and quantify the long term status of the project phases of agile development and testing in a clear and interactive way, while the outputs are represented by clearly defined problems that can be more easily treated, as one can argue further progress.
APA, Harvard, Vancouver, ISO, and other styles
35

Löjdquist, Axel. "Net benefit analysis of Visual Regression Testing in a Continuous integration environment: An industrial Case study." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-166347.

Full text
Abstract:
Maintaining quality in software is a difficult task for several reasons, such as, company growth, time-to-market demands, code complexity and more. GUI testing tools and Continuous Integration (CI) are common practice today to tackle some of the issues with maintaining software quality. However, these techniques bring a set of challenges. Visual Regression Testing (VRT) is a special kind of GUI testing technique focused upon image-based assertions. This study presents an implementation and investigation of the benefits and drawbacks of introducing VRT for a CI environment in an industrial context. Additionally, the thesis investigates factors that need to be considered upon this transition. The results show that benefits are associated with this approach, such as, quicker feedback times and an increase in testing frequency. However, drawbacks and implications were also identified, such as, test maintenance and organizational concerns, indicating careful consideration needs to be taken by an organization before proceeding with an implementation.
APA, Harvard, Vancouver, ISO, and other styles
36

Namli, Tuncay. "Testbatn - A Scenario Based Test Platform For Conformance Andinteroperability Testing." Phd thesis, METU, 2011. http://etd.lib.metu.edu.tr/upload/12613285/index.pdf.

Full text
Abstract:
Today, interoperability is the major challenge for e-Business and e-Government domains. The fundamental solution is the standardization in different levels of business-to-business interactions. However publishing standards alone are not enough to assure interoperability between products of different vendors. In this respect, testing and certification activities are very important to promote standard adoption, validate conformance and interoperability of the products and maintain correct information exchange. In e-Business collaborations, standards need to address different layers of interoperability stack
communication layer, business document layer and business process layer. Although there have been conformance and interoperability testing tools and initiatives for each one of these categories, there is currently no support for testing an integration of the above within a test scenario which is similar to real life use cases. Together with the integration of different layers of testing, testing process should be automated so that test case execution can be done at low cost, and repeated if required. In this theses, a highly adaptable and flexible Test Execution Model and a complementary XML based Test Description Language consisting of high level test constructs which can handle or simulate different parts or layers of the interoperability stack is designed. The computer interpretable test description language allow dynamic set up of test cases and provides flexibility to design, modify, maintain and extend the test functionality in contrast to a priori designed and hard coded test cases. The work presented in this thesis is a part of the TestBATN system supported by TUBITAK, TEYDEB Project No: 7070191.
APA, Harvard, Vancouver, ISO, and other styles
37

Meudec, Christophe. "Automatic generation of software test cases from formal specifications." Thesis, Queen's University Belfast, 1998. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.263505.

Full text
APA, Harvard, Vancouver, ISO, and other styles
38

Malý, Michal. "Automatizované testování s využitím nástroje HP Quick Test Professional." Master's thesis, Vysoká škola ekonomická v Praze, 2014. http://www.nusl.cz/ntk/nusl-198596.

Full text
Abstract:
This thesis deals with software testing and its possible automation and compares the pros and cons of automated testing with manual testing. In the automated approach is introduced tool for automated testing HP QuickTest Professional (HP QTP). The main objective is to analyze the advantages of using this tool in conditions of a real project, based on predefined criteria. In the theoretical section I introduce basic terms within the field of software testing and identify testing in the software development process. A comparison of manual and automated approach to software testing and introduction of tool HP QTP for automated tests follows. Target of practical part is to analyze the advantages of automation by using HP QTP on a real project according to defined criteria and recommend for what conditions the automation in this case worthwhile. In the practical part is also created manual which describing the basic functionality of HP QTP, which is demonstrated on examples. Manual, which is also the output of this work, has to help testers to quickly understand the work with this tool and therefore better plan process of tests automation.
APA, Harvard, Vancouver, ISO, and other styles
39

Ho, Chun-fai Jeffrey. "Towards automatic oracles for the testing of mesh simplification software." Click to view the E-thesis via HKUTO, 2005. http://sunzi.lib.hku.hk/hkuto/record/B36393228.

Full text
APA, Harvard, Vancouver, ISO, and other styles
40

Ho, Chun-fai Jeffrey, and 何晉輝. "Towards automatic oracles for the testing of mesh simplification software." Thesis, The University of Hong Kong (Pokfulam, Hong Kong), 2005. http://hub.hku.hk/bib/B36393228.

Full text
APA, Harvard, Vancouver, ISO, and other styles
41

Enoiu, Eduard. "Automatic test generation for industrial control software." Doctoral thesis, Mälardalens högskola, Inbyggda system, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-33364.

Full text
Abstract:
Since the early days of software testing, automatic test generation has been suggested as a way of allowing tests to be created at a lower cost. However, industrially useful and applicable tools for automatic test generation are still scarce. As a consequence, the evidence regarding the applicability or feasibility of automatic test generation in industrial practice is limited. This is especially problematic if we consider the use of automatic test generation for industrial safety-critical control systems, such as are found in power plants, airplanes, or trains. In this thesis, we improve the current state of automatic test generation by developing a technique based on model-checking that works with IEC 61131-3 industrial control software. We show how automatic test generation for IEC 61131-3 programs, containing both functional and timing information, can be solved as a model checking problem for both code and mutation coverage criteria.  The developed technique has been implemented in the CompleteTest tool. To evaluate the potential application of our technique, we present several studies where the tool is applied to industrial control software. Results show that CompleteTest is viable for use in industrial practice; it is efficient in terms of the time required to generate tests that satisfy both code and mutation coverage and scales well for most of the industrial programs considered. However, our results also show that there are still challenges associated with the use of automatic test generation. In particular, we found that while automatically generated tests, based on code coverage, can exercise the logic of the software as well as tests written manually, and can do so in a fraction of the time, they do not show better fault detection compared to manually created tests. Specifically, it seems that manually created tests are able to detect more faults of certain types (i.e, logical replacement, negation insertion and timer replacement) than automatically generated tests. To tackle this issue, we propose an approach for improving fault detection by using mutation coverage as a test criterion. We implemented this approach in the CompleteTest tool and used it to evaluate automatic test generation based on mutation testing. While the resulting tests were more effective than automatic tests generated based on code coverage, in terms of fault detection, they still were not better than manually created tests. In summary, our results highlight the need for improving the goals used by automatic test generation tools. Specifically, fault detection scores could be increased by considering some new mutation operators as well as higher-order mutations. Our thesis suggests that automatically generated test suites are significantly less costly in terms of testing time than manually created test suites. One conclusion, strongly supported by the results of this thesis, is that automatic test generation is efficient but currently not quite as effective as manual testing. This is a significant progress that needs to be further studied; we need to consider the implications and the extent to which automatic test generation can be used in the development of reliable safety-critical systems.
APA, Harvard, Vancouver, ISO, and other styles
42

Csallner, Christoph. "Combining over- and under-approximating program analyses for automatic software testing." Diss., Atlanta, Ga. : Georgia Institute of Technology, 2008. http://hdl.handle.net/1853/24764.

Full text
Abstract:
Thesis (Ph.D.)--Computing, Georgia Institute of Technology, 2009.
Committee Chair: Smaragdakis, Yannis; Committee Member: Dwyer, Matthew; Committee Member: Orso, Alessandro; Committee Member: Pande, Santosh; Committee Member: Rugaber, Spencer.
APA, Harvard, Vancouver, ISO, and other styles
43

Bertilsson, Henrik, and Gustav Näsman. "Improving progress tracking using automated testing techniques." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3863.

Full text
Abstract:
One of the problems when developing software is the difficulty of knowing how much that is done in a project. This is a basic condition to be able to estimate the remaining efforts with increased accuracy over time. To get accurate progress information it is important that the progress tracking is done in an objective way and also in an as simple way as possible. Our focus in this work has been software projects in general but a case study has also been performed at Ericsson Software Technology AB in Ronneby. We have studied the organization and performed interviews with project managers to find out if this really is a problem and if the process can be improved in some way to ease the task of progress tracking. This case study together with our literature study has resulted in a proposition for a solution. Our approach has been to use automated testing as a way to make progress tracking more objective. The result presented in this thesis is a base for a system that could ease the tracking of progress. In short, the system extracts information from an automated testing process and compares it with estimated figures to be able to automatically generate progress information.
0708-574327
APA, Harvard, Vancouver, ISO, and other styles
44

Ivan, Michal. "Optimalizácia procesu testovania s využitím voľne dostupných nástrojov na vytváranie automatizovaných testov." Master's thesis, Vysoká škola ekonomická v Praze, 2015. http://www.nusl.cz/ntk/nusl-203932.

Full text
Abstract:
Diploma thesis deals with the implementation of automated tests to the process of testing web applications. Introduction of the theoretical part is devoted to familiarizing the reader with the concept of testing and illustration of its importance not only in software development. Author then defines the term, introduces the principles, and attention is paid to the interpretation of terms which are commonly used in testing. The next section contains specific division of this process in terms of of the used techniques, methods and levels of testing. By description, and stating the fundamental differences between manual and automated testing creates conditions for understanding the issues, on which work is focused. At the end of theoretical part there are characterized basic models of software development life cycle, in which the process of testing has its place. In the practical part the author at first draws attention to introduction of of web application in which automated tests will be implemented. Subsequently, based on the introduced methodology, he analyzes the process of testing this application. He defines the reasons for the implementation of automated testing, he marks the areas of coveragecreates working team and the timetable for implementation. On the basis of established criteria justifies the choice of tools to be used in automation. In the next chapter he accompanies reader systematically across the entire process of creation and implementation of automated tests, and intentionally complements it with practical examples. End is devoted to assessment of the results that have been achieved by the implementation of automated tests. By comparing them with manual tests author determines the effectiveness of automation. Calculating the estimated savings is determined by the return on investment in automated tests.
APA, Harvard, Vancouver, ISO, and other styles
45

Ferrari, Daniele. "Testing automatico di applicazioni web." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2018. http://amslaurea.unibo.it/15162/.

Full text
Abstract:
In questa tesi vengono spiegati i principali vantaggi e ostacoli dell'utilizzo di testing automatico, con particolare enfasi sul testing di web application. Vengono elencate una serie di regole di buona condotta per la scrittura di test automatici e analizzati e confrontati tre dei principali strumenti per la scrittura e gestione di test automatici. Viene poi descritto un caso reale: l'utilizzo di Cypress per scrivere una serie di test automatici per un editor web di wireframe, Balsamiq Mockup. In quest'ultima fase vengono analizzati i pro e i contro del software, i problemi riscontrati e le soluzioni adottate.
APA, Harvard, Vancouver, ISO, and other styles
46

Aho, P. (Pekka). "Automated state model extraction, testing and change detection through graphical user interface." Doctoral thesis, Oulun yliopisto, 2019. http://urn.fi/urn:isbn:9789526224060.

Full text
Abstract:
Abstract Testing is an important part of quality assurance, and the use of agile processes, continuous integration and DevOps is increasing the pressure for automating all aspects of testing. Testing through graphical user interfaces (GUIs) is commonly automated by scripts that are captured or manually created with a script editor, automating the execution of test cases. A major challenge with script-based GUI test automation is the manual effort required for maintaining the scripts when the GUI changes. Model-based testing (MBT) is an approach for automating also the design of test cases. Traditionally, models for MBT are designed manually with a modelling tool, and an MBT tool is used for generating abstract test cases from the model. Then, an adapter is implemented to translate the abstract test cases into concrete test cases that can be executed on system under test (SUT). When the GUI changes, the model has to be updated and the test cases can be generated from the updated model, reducing the maintenance effort. However, designing models and implementing adapters requires effort and specialized expertise. The main research questions of this thesis are 1) how to automatically extract state-based models of software systems with GUI, and 2) how to use the extracted models to automate testing. Our focus is on using dynamic analysis through the GUI during automated exploration of the system, and we concentrate on desktop applications. Our results show that extracting state models through GUI is possible and the models can be used to generate regression test cases, but a more promising approach is to use model comparison on extracted models of consequent system versions to automatically detect changes between the versions
Tiivistelmä Testaaminen on tärkeä osa laadun varmistusta. Ketterät kehitysprosessit ja jatkuva integrointi lisäävät tarvetta automatisoida kaikki testauksen osa-alueet. Testaus graafisten käyttöliittymien kautta automatisoidaan yleensä skripteinä, jotka luodaan joko tallentamalla manuaalista testausta tai kirjoittamalla käyttäen skriptieditoria. Tällöin scriptit automatisoivat testitapausten suorittamista. Muutokset graafisessa käyttöliittymässä vaativat scriptien päivittämistä ja scriptien ylläpitoon kuluva työmäärä on iso ongelma. Mallipohjaisessa testauksessa automatisoidaan testien suorittamisen lisäksi myös testitapausten suunnittelu. Perinteisesti mallipohjaisessa testauksessa mallit suunnitellaan manuaalisesti käyttämällä mallinnustyökalua, ja mallista luodaan abstrakteja testitapauksia automaattisesti mallipohjaisen testauksen työkalun avulla. Sen jälkeen implementoidaan adapteri, joka muuttaa abstraktit testitapaukset konkreettisiksi, jotta ne voidaan suorittaa testattavassa järjestelmässä. Kun testattava graafinen käyttöliittymä muuttuu, vain mallia täytyy päivittää ja testitapaukset voidaan luoda automaattisesti uudelleen, vähentäen ylläpitoon käytettävää työmäärää. Mallien suunnittelu ja adapterien implementointi vaatii kuitenkin huomattavan työmäärän ja erikoisosaamista. Tämä väitöskirja tutkii 1) voidaanko tilamalleja luoda automaattisesti järjestelmistä, joissa on graafinen käyttöliittymä, ja 2) voidaanko automaattisesti luotuja tilamalleja käyttää testauksen automatisointiin. Tutkimus keskittyy työpöytäsovelluksiin ja dynaamisen analyysin käyttämiseen graafisen käyttöliittymän kautta järjestelmän automatisoidun läpikäynnin aikana. Tutkimustulokset osoittavat, että tilamallien automaattinen luominen graafisen käyttöliittymän kautta on mahdollista, ja malleja voidaan käyttää testitapausten generointiin regressiotestauksessa. Lupaavampi lähestymistapa on kuitenkin vertailla malleja, jotka on luotu järjestelmän peräkkäisistä versioista, ja havaita versioiden väliset muutokset automaattisesti
APA, Harvard, Vancouver, ISO, and other styles
47

Pernikář, Aleš. "Automatická kontrola kvality software na embedded zařízení." Master's thesis, Vysoké učení technické v Brně. Fakulta elektrotechniky a komunikačních technologií, 2019. http://www.nusl.cz/ntk/nusl-400645.

Full text
Abstract:
This thesis concerns automation of software and hardware testing using the robotic testing system called RQA. It aims to design an interface to produce test scenarios using the robotic testing system. Next it elaborates metrics measured during testing used for quality assurance of the system uder test. One of the topics covered is a visualization of test data and measurements for an easy overview of quality.
APA, Harvard, Vancouver, ISO, and other styles
48

Andersson, Sebastian, and Gustav Carlstedt. "Automated Testing of Robotic Systems in Simulated Environments." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-44572.

Full text
Abstract:
With the simulations tools available today, simulation can be utilised as a platform for more advanced software testing. By introducing simulations to software testing of robot controllers, the motion performance testing phase can begin at an earlier stage of development. This would benefit all parties involved with the robot controller. Testers at ABB would be able to include more motion performance tests to the regression tests. Also, ABB could save money by adapting to simulated robot tests and customers would be provided with more reliable software updates. In this thesis, a method is developed utilising simulations to create a test set for detecting motion anomalies in new robot controller versions. With auto-generated test cases and a similarity analysis that calculates the Hausdorff distance for a test case executed on controller versions with an induced artificial bug. A test set has been created with the ability to detect anomalies in a robot controller with a bug.
APA, Harvard, Vancouver, ISO, and other styles
49

Perez, Ivan Rodolfo Duran Cruz. "Geração automatica de cenarios de teste a partir de modelos da especificação de sistemas." [s.n.], 2008. http://repositorio.unicamp.br/jspui/handle/REPOSIP/276180.

Full text
Abstract:
Orientador: Eliane Martins
Dissertação (mestrado) - Universidade Estadual de Campinas, Instituto de Computação
Made available in DSpace on 2018-08-13T10:23:49Z (GMT). No. of bitstreams: 1 Perez_IvanRodolfoDuranCruz_M.pdf: 1633844 bytes, checksum: e823f99de0cc740109404e263028fac7 (MD5) Previous issue date: 2008
Resumo: As crescentes exigências em relação à melhoria de qualidade e a redução de custos e prazos têm tornado comum à busca por soluções mais eficientes para desenvolvimento e testes de sistemas. Com relação aos testes, uma recomendação é a de começá-los mais cedo, e, de preferência, automatizar o que for possível para evitar enganos cometidos pelos testadores. Assim, uma área de pesquisa que está em evidência atualmente é a de testes baseados em modelos (MBT), onde muitos estudos têm sido realizados visando o desenvolvimento de soluções para automação de testes a partir de modelos criados durante o ciclo de desenvolvimento. Nesta dissertação é proposto um método para geração automática de cenários de teste a partir de modelos da especificação de sistemas, baseando-se em um trabalho prévio para geração de testes de componentes de software. Os modelos utilizados para geração dos testes são os Diagramas de Atividades UML, criados a partir da descrição dos casos de uso, para Testes de Sistemas. A partir deles são gerados cenários de teste que descrevem as interações do sistema, tais como, as ações dos atores e as situações esperadas, incluindo também os cenários de exceção. A aplicação deste método na prática foi feita com êxito por uma equipe de testadores em sistemas reais. De forma geral, os modelos especificados para derivação dos testes têm facilitado o entendimento do sistema pelos testadores envolvidos e as informações presentes nos cenários de teste têm apoiado a realização dos testes.
Abstract: The increasing requirements for quality improvement, reduction of costs and deadlines have promoted the search for more efficient solutions for systems development and testing. In the case of the tests, the recommendation is to start them earlier and, preferably, automatize what is possible to prevent the testers mistakes. Thus, a research area that is in evidence currently is the Model-Based Testing (MBT), in which many studies have been carried out with the aim of development solutions for test automation from the models created during the software development cycle. In this dissertation is proposed a method for automatic generation of test scenarios from the models of systems specification, it is based on a previous work for tests generation of software components. The models used for tests generation are the UML Activities Diagrams, generated from the description of the use cases for System Testing. From them, test scenarios are generated that describe the interactions of the system, such as, the actors actions and the expected situations, including also the exception scenarios. The application of this method in practice was successfully made by a team of testers in real systems. In general, the models specified for tests derivation have facilitated the agreement of the system by the involved testers and, the generated test scenarios contain information that have supported the test execution.
Mestrado
Mestre em Ciência da Computação
APA, Harvard, Vancouver, ISO, and other styles
50

Christersson, Frend Paul. "Unit testing the User Interface : Automatic tests of web UI's in React." Thesis, Mittuniversitetet, Avdelningen för data- och systemvetenskap, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:miun:diva-29938.

Full text
APA, Harvard, Vancouver, ISO, and other styles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography