To see the other types of publications on this topic, follow the link: Automated integration testing.
Dissertations / Theses on the topic 'Automated integration testing'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 24 dissertations / theses for your research on the topic 'Automated integration 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
Borg, Daniel, and Anders Elfström. "Automatiserad testning av användargränssnitt i SharePoint : Automated UI Testing in SharePoint." Thesis, KTH, Skolan för informations- och kommunikationsteknik (ICT), 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-177132.
Full textAbstract:
Företag arbetar ofta efter hårda krav från kunder där lösningar måste levereras på ett tidseffektivt sätt och samtidigt hålla en hög kvalitet. Detta i form av felfria och robusta system vilket delvis kan åstadkommas med hjälp av testning. Kraven på snabb leverans och hög kvalitet är däremot motpoler till varandra; snabb leverans genomförs ofta på bekostnad av kvalitet och tvärtom. Agila arbetsmetoder med tidiga och frekventa leveranser har ändrat på detta, men kräver samtidigt en ständig kvalitetsförsäkring under arbetets löptid. Under utveckling av mjukvara enligt dessa metoder förekommer därför en kontinuerlig kvalitetssäkringsprocess för att säkerställa att produkten dels uppfyller vad kravspecifikationen avser samt att levererad produkt håller en hög tekniskt kvalitet i form av buggfri och robust kod som innehar stor pålitlighet för framtiden. Då manuell testning är en kostnad- och resurskrävande metod har automatiserad testning blivit ett aktuellt alternativ för ökad effektivitet och hållbar utveckling. Målet med det här arbetet har varit att för Precio Systemutveckling AB utreda möjligheterna för en implementation av automatiserad testning av användargränssnitt, i en hos företaget redan existerande och etablerad utvecklingsprocess. Arbetet har genomförts med en inledande förstudie om testning med fokus på varför det är en extra viktig faktor i dagsläget. Detta följs av ett avsnitt där existerande teori och teknik för testning i generell mening avhandlats, följt av en närmare studie på hur automatiserad testning är rekommenderad att utföras ur ett perspektiv från utveckling av produkter inom Microsoft-teknologi.Software companies work under a strict pressure from customers where solutions must be delivered in a timely manner as well as providing high quality and value. The products should be robust and without errors, which partially can be accomplished by testing during the development process. The requirement for an early delivery and a high quality does not always come hand in hand, but with the increased use of agile software development methods, this can be achieved. During agile development of software, there is a continuous process to ensure the quality of what is being developed, both to make sure that all the functional requirements are fulfilled, but also that the code behind is robust and dependable for the future. Since manual testing can be both time and resource consuming, automated testing has become a modern alternative to increase productivity and to maintain a sustainable development process. The goal of this thesis work has been to investigate the possibilities of implementing a solution for automated UI testing in an already existing development process at the company Precio Systemutveckling AB. The work has been conducted in three steps, starting with a literature study about testing in general, followed by an extensive research into suitable tools and technology for testing that exists today. After this, a deeper look was made at what the recommended solutions for implementing automated testing in a Microsoft-oriented enviroment were. The work was concluded with an actual implementation of automated testing on premise at Precio.
2
MADHUKAR, ENUGURTHI. "GENERATE TEST SELECTION STATISTICS WITH AUTOMATED MUTATION TESTING." Thesis, Blekinge Tekniska Högskola, Institutionen för datalogi och datorsystemteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-16836.
Full textAbstract:
Context: The goal of this research is to form a correlation between code packages and test cases which is done by using automated weak mutation. The correlations formed is used as the statistical test data for selecting relevant tests from the test suite which decreases the size of the test suite and speed up the process. Objectives: In this study, we have done an investigation of existing methods for reducing the computational cost of automatic mutation testing. After the investigation, we build an open source automatic mutation tool that mutates the source code to run on the test cases of the mutated code that maps the failed test to the part of the code that was changed. The failed test cases give the correlation between the test and the source code which is collected as data for future use of the test selection. Methods: Literature review and Experimentation is chosen for this research. It was a controlled experiment done at the Swedish ICT company to mutate the camera codes and test them using the regression test suite. The camera codes provided are from the continuous integration of historical data. We have chosen experimentation as our research because as this method of research is more focused on analyzing the data and implementing a tool using historical data. A literature review is done to know what kind of mutation testing reduces the computational cost of the testing process. The implementation of this process is done by using experimentation Results: The comparative results obtained after mutating the source code with regular mutants and weak mutants we have found that regular mutants and weak mutants are compared with their correlation accuracy and we found that on regular mutation operators we got 62.1% correlation accuracy and coming to weak mutation operators we got 85% of the correlation accuracy. Conclusions: This research on experimentation to form the correlations in generating test selection statistics using automated mutation testing in the continuous integration environment for improving test cases selection in regression testing
3
Palmieri, Manuel. "System Testing in a Simulated Environment." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-18701.
Full textAbstract:
System Testing in a Simulated Environment is becoming one of the bigger challenges moved by companies with the purpose to improve the quality and increase the dependability of artefacts. Moreover, another big challenge faced by them is the achievement of the independent development of software and hardware systems, with the purpose to speed up and reduce costs of development. Besides, software testing remains today a tricky activity that attracts the interest of many researchers and companies with the purpose to refine or invent new techniques and methods to perform the optimal testing on different case studies and conditions. Nowadays, the execution of testing on some real environments is not adequate because of the impossibility to perform particular kinds of tests that could be destructive for hardware and dangerous for testers. One of the areas that are affected by this issue is certainly the one regarding the production of vehicles that work in critical environments. In this respect, companies in such applicative domain trying to move towards the revolutionary approach to replace real environments with simulated environments. This thesis presents a survey of existing state–of–the–art and state–of–the–practice testing techniques and methods, a simulated environment derived from a vehicle, and how and in what way it is possible to perform testing on a simulated environment. Furthermore, with the purpose to provide a better understanding of how a real environment could be represented with a simulated environment, an overview of replacement is presented. Besides, according to CrossControl and customers’ environments, limits and needs, a case study has been realized to demonstrate how is possible to design, implement and test a simulated environment.
4
Thulin, Pontus. "Evaluation of the applicability of security testing techniques in continuous integration environments." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-113753.
Full textAbstract:
Agile development methodologies are becoming increasingly popular, especially in projects that develop web applications. However, incorporation of software security in lightweight approaches can be difficult. Using security testing techniques throughout a complete agile development process by running automated tests in continuous integration environments is one approach that strives to improve security in agile projects. Instead of performing security testing at the end of the development cycle, such methods enables early and continuous detection of security risks and vulnerabilities. The purpose of this thesis is to study how existing security testing techniques operate in continuous integration environments and what level of security they can help assure. The work is a qualitative analysis of dierent security testing techniques and evaluates how they technically fit into a continuous integration environment as well as how they adhere to agile principles. These techniques are also analyzed with the use of OWASP Top Ten to determine which security requirements they can verify. The outcome of the analysis is that no existing security testing technique is a perfect fit for usage in continuous integration testing. Each technique has its distinct advantages and drawbacks that should be taken into consideration when choosing a technique to work with in continuous integration environments.
5
Sigfast, Martin, and Fredrik Olsson. "Benefits of continuous delivery for Sigma IT Consulting." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-74995.
Full textAbstract:
Manual deploys and testing of code can be both time-consuming and error-prone. Many repetitive manual steps can lead to critical tests or necessary configuration being forgotten or being skipped due time-constraints resulting in software that doesn’t work as intended when deployed to production. The purpose of this report is to examine whether continuous delivery(CD) could lead to any positive effects and if there are any obstacles for CD in an Episerver project at Sigma ITC. The study was done by implementing a CD pipeline for a project similar to a real project at Sigma then letting the developers work with it and interviewing them about their current workflow, their attitude towards the different steps involved and if they saw any problems with CD for their project. Even if the developers, in general, where positive to CD they had some reservations about it in their current projects. The main obstacle the developers saw where the time/cost which would affect the customer and also some uncertainty around the complexity in testing Episerver. The results show that there could be positive effects of CD even if the project type is not optimal for reaping all the CD benefits, it all depends on people involved seeing a value in testing and the questions around testing in Episerver are straightened out.
6
Munzarová, Helena. "Návrh a implementace integrovaného testovacího nástroje." Master's thesis, Vysoká škola ekonomická v Praze, 2014. http://www.nusl.cz/ntk/nusl-193805.
Full textAbstract:
The purpose of this thesis is to design and implement integration interface, which represents the core of the Integrated testing tool. Integrated testing tool provides support in the whole process of software testing. This support involves requirement specification and management of the corresponding tests, bug management and creation and execution of automated testing scripts. Integrated testing tool uses existing open-source tools to provide this functionality. The communication of these tools is provided by the integration interface, implementation of which is the purpose of this thesis. Currently there is no so complex open-source solution in the testing area, Integrated testing tool endeavours to fill this gap. The tool is being developed within the activity of the competence centre Software Quality Assurance at the University of Economics in Prague. The analytical phase of the development is described in the diploma thesis written by Bc. Jan Ženíšek Project of the development of Integrated testing tool.
7
Odrobinová, Lucia. "Návrh nástroje pro automatizované integrační testování." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2021. http://www.nusl.cz/ntk/nusl-444621.
Full textAbstract:
The diploma thesis focuses on the development of an automated integration testing tool for a company. The tool is employed to detect and report data changes that may have been caused by the modification of a database schema during the development of a software. This automation of recognizing data changes brings many advantages to the company. The tool has been developed using the C# programming language, which supports object-oriented programming, using the Microsoft Visual Studio Community 2019 software. Since the tool works with the Microsoft SQL Server database, Entity Framework, an object-relational mapping framework, has been used during the implementation of the tool.
8
Strand, Anton. "Continuous Integration Pipelines to Assess Programming Assignments : Test Like a Professional." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-96713.
Full textAbstract:
Examiners of programming assignments in higher education and people in the software industry both need to test and review code. However, the assessing techniques used are often quite different. The IT industry often uses agile work methods like continuous integration and automated tests, while examiners either do manual assessments or rely on code grading tools. The students will most likely become developers and work using agile processes. Therefore, there are possible benefits of universities trying to imitate the work processes of the software industry. The purpose of this study was to develop a workflow for programming assignments inspired by continuous integration, Scrum, and GitLab flow. The workflow was developed based on the requirements of Linnaeus University and tested on one of their programming assignments. It showed that a simplified agile work process is suitable for programming assignments since the demonstration fulfilled all of the predefined requirements. However, examiners might miss some of the workflow’s benefits if the programming assignment can not be tested automatically since it will require more manual work while grading.
9
Kristensson, Dennis. "Comparative study of the testing tools Ghost Inspector and Selenium." Thesis, Malmö högskola, Fakulteten för teknik och samhälle (TS), 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:mau:diva-20826.
Full textAbstract:
Studien undersöker de automatiserade testverktygen: Ghost Inspector och Selenium. En limiterad litteraturstudie och två fallstudier görs, för att undersöka och utvärdera testverktygen. Detta för att kunna tillgodose riktlinjer som är användbara, vid val av ett verktyg för att utföra regressionstestning på webbapplikationer.IStone använder Ghost Inspector som verktyg vid regressionstest på webb applikationer, eftersom det ger dem en effektiv konfigurering och underhålls- process. Selenium kräver mer ansträngning för konfigurering och underhåll, eftersom verktygen inte är en tjänst. Miljön i Ghost Inspector underlättar för iStone att exekvera test kontinuerligt och förser projektteamet med det senaste testresultatet.The study evaluates the automatic testing tools: Ghost Inspector and Selenium. and focuses on comparing them in terms of the set up and maintenance processes. The study includes a limited literature study and two case studies. The purpose is to evaluate the tools and provide guidelines for choosing a regression testing tool when testing the functionality of web applications.IStone use Ghost Inspector as regressions testing tool on web applications, since it offers an effective set up and maintenance process. Selenium requires more effort to set up and maintain, since Selenium is not a service. The Ghost Inspector environment comforts iStone with the ability of executing test continuously and supplies the latest test results to the project team.
10
Kyloušek, Josef. "Inovace systému pro automatizované integrační testy elektronických jednotek vozidel." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2017. http://www.nusl.cz/ntk/nusl-363771.
Full textAbstract:
This master's thesis deals with the issue of software tools for automated integrational ECU testing. It is specifically focused on TestAut 2 tool, which is developed by e4t company and used for testing of Skoda cars. Goal of this thesis is comparison of TestAut 2 against similar tools used in automotive industry. This work contains analysis of TestAut 2 tooland description of principles and features of EXAM, MODENA and PROVEtech tools. Set of principles considerd as advantageous is chosen from collected information. Next part of this thesis describes implementation of chosen principles to TestAut 2 tool, verification ofit's functionality and evaluation of it's benefits. In the conclusion author suggests another improvements that can be done.
11
Souza, Higor Amario de. "Depuração de programas baseada em cobertura de integração." Universidade de São Paulo, 2012. http://www.teses.usp.br/teses/disponiveis/100/100131/tde-08032013-162246/.
Full textAbstract:
Depuração é a atividade responsável pela localização e correção de defeitos gerados durante o desenvolvimento de programas. A depuração ocorre devido à atividade de teste bem-sucedida, na qual falhas no comportamento do programa são reveladas, indicando a existência de defeitos. Diversas técnicas têm sido propostas para automatizar a tarefa de depuração de programas. Algumas delas utilizam heurísticas baseadas em informações de cobertura obtidas da execução de testes. O objetivo é indicar trechos de código do programa mais suspeitos de conter defeitos. As informações de cobertura mais usadas em depuração automatizada são baseadas no teste estrutural de unidade. A cobertura de integração, obtida por meio da comunicação entre as unidades de um programa, pode trazer novas informações sobre o código executado, possibilitando a criação de novas estratégias para a tarefa de localização de defeitos. Este trabalho apresenta uma nova técnica de localização de defeitos chamada Depuração de programas baseada em Cobertura de Integração (DCI). São apresentadas duas coberturas de integração baseadas nas chamadas de métodos de um programa. Essas coberturas são usadas para a proposição de roteiros de busca dos defeitos a partir dos métodos considerados mais suspeitos. As informações de cobertura de unidade são então utilizadas para a localização dos defeitos dentro dos métodos. A DCI também utiliza uma nova heurística para atribuição de valores de suspeição a entidades de integração estática dos programas como pacotes, classes e métodos, fornecendo também um roteiro para a procura dos defeitos. Os experimentos realizados em programas reais mostram que a DCI permite realizar a localização de defeitos de forma mais eficaz do que o uso de informações de cobertura de unidade isoladamente.Debugging is the activity responsible for localizing and fixing faults generated during software development. Debugging occurs due to a successful testing activity, in which failures in the behavior of the program are revealed, indicating the existence of faults. Several techniques have been proposed to automate the debugging tasks, especially the fault localization task. Some techniques use heuristics based on coverage data obtained from the execution of tests. The goal is to indicate program code excerpts more likely to contain faults. The coverage data mostly used in automated debugging is based on white-box unit testing. Integration coverage data, obtained from the communication between the units of a program, can bring about new information with respect to the executed code, which allows new strategies to the fault localization task to be devised. This work presents a new fault localization technique called Debugging based on Integration Coverage (DIC). Two integration coverages based on method invocations are presented. These coverages are used to propose two search strategies that provides a roadmap to locate faults by investigating the more suspicious methods. The unit coverage information are used to search the faulty statement inside the suspicious methods. The DIC technique also proposes a heuristic that assigns suspiciousness values to static integration entities of the programs, namely, packages, classes, and methods. This heuristic also provides a roadmap to search for the faults. Experiments using real programs show that DIC is more effective to locate faults than solely using unit coverage information.
12
Šmerda, Jakub. "Zdokonalení procesu automatického testování softwarových aplikací." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2014. http://www.nusl.cz/ntk/nusl-236078.
Full textAbstract:
The dissertation covers the process of automatic software testing. It describes fundamental principles of tests creation and presents common tools for concurrent integration. The main objective of the dissertation is improvement of the automatic testing process in the Department Corporate Technology Development Center of the Company Siemens Ltd., which was realized through the plug-in module for the TeamCity tool that makes reporting of test results more transparent. At the end of the dissertation, there are designed extensions of the plug-in module that could have a further benefit for automatic testing process by means of the TeamCity tool. The dissertation also includes the manual for easy installation of the implemented solution.
13
Nečas, Radek. "Systém pro kontinuální integraci projektu k-Wave." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2016. http://www.nusl.cz/ntk/nusl-255473.
Full textAbstract:
The main goal of this thesis is to describe the implementation of continuous integration into the k-Wave project. The thesis focuses primarily on the version written in the C/C++ language with the usage of the OpenMP library which typically runs on supercomputers. Accordingly, many of popular workflows and approaches ought to be adapted, a few more created. The outcome of the thesis is a complete solution with real and practical usage. The author provides design, tools selection, runtime environment administration and configuration for each one of the used services. Software implementation of the basic framework is used in order to utilize running tests on the supercomputers. Furthermore, the implementation of chosen types of regression and unit tests are performed. Realisation is based on Gitlab and Jenkis services that are running on separated Docker containers.
14
Broström, Andreas. "Integrating Automated Security Testing in the Agile Development Process : Earlier Vulnerability Detection in an Environment with High Security Demands." Thesis, KTH, Skolan för datavetenskap och kommunikation (CSC), 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-170834.
Full textAbstract:
The number of vulnerabilities discovered in software has been growing fast the last few years. At the same time the Agile method has quickly become one of the most popular methods for software development. However, it contains no mention of security, and since security is not traditionally agile it is hard to develop secure software using the Agile method. To make software secure, security testing must be included in the development process. The aim of this thesis is to investigate how and where security can be integrated in the Agile development process when developing web applications. In the thesis some possible approaches for this are presented, one of which is to use a web application security scanner. The crawling and detection abilities of four scanners are compared, on scanner evaluation applications and on applications made by Nordnet.An example implementation of one of those scanners is made in the testing phase of the development process. Finally, a guide is created that explains how to use the implementation. I reach the conclusion that it is possible to integrate security in the Agile development process by using a web application security scanner during testing. This approach requires a minimal effort to set up, is highly automated and it makes the Agile development process secure and more effective.Antalet upptäckta sårbarheter i mjukvara har ökat fort under de senaste åren. Den agila metoden har samtidigt blivit en av de mest populära metoderna för mjukvaruutveckling. Den berör dock inte säkerhet, och eftersom säkerhet, traditionellt sett, inte är agilt så blir det svårt att utveckla säker mjukvara med den agila metoden. För att kunna göra mjukvaran säker så måste säkerhetstestning infogas i utvecklingsfasen. Syftet med det här arbetet är att undersöka hur och var säkerhet kan integreras i den agila utvecklingsprocessen vid utveckling av webbapplikationer. Några sätt att göra detta på beskrivs i arbetet, varav ett är att använda ett verktyg för säkerhetstestning. En jämförelse av hur bra fyra sådana verktyg är på att genomsöka och hitta sårbarheter utförs på applikationer designade för att utvärdera verktyg för säkerhetstestning, samt hos Nordnets egna applikationer. Sedan beskrivs en exempelimplementation av ett av dessa verktyg i testfasen av utvecklingsprocessen. Slutligen, tas en guide fram som beskriver hur implementationen kan användas. Jag kommer fram till att det är möjligt att inkludera säkerhet i den agila utvecklingsprocessen genom att använda ett verktyg för säkerhetstestning i testfasen av utvecklingsprocessen. Detta tillvägagångssätt innebär en minimal ansträngning att införa, är automatiserat i hög grad och det gör den agila utvecklingsprocessen säker och mer effektiv.
15
Ferrari, Daniele. "Testing automatico di applicazioni web." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2018. http://amslaurea.unibo.it/15162/.
Full textAbstract:
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.
16
Forni, Federico. "Controllo ottico automatizzato di circuiti fotonici integrati: Progettazione, realizzazione e valutazione." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2014. http://amslaurea.unibo.it/6473/.
Full textAbstract:
In this report a new automated optical test for next generation of photonic integrated circuits (PICs) is provided by the test-bed design and assessment. After a briefly analysis of critical problems of actual optical tests, the main test features are defined: automation and flexibility, relaxed alignment procedure, speed up of entire test and data reliability. After studying varied solutions, the test-bed components are defined to be lens array, photo-detector array, and software controller. Each device is studied and calibrated, the spatial resolution, and reliability against interference at the photo-detector array are studied. The software is programmed in order to manage both PIC input, and photo-detector array output as well as data analysis. The test is validated by analysing state-of-art 16 ports PIC: the waveguide location, current versus power, and time-spatial power distribution are measured as well as the optical continuity of an entire path of PIC. Complexity, alignment tolerance, time of measurement are also discussed.
17
Wolfert, Richard. "Automatické testování systému BeeeOn." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2018. http://www.nusl.cz/ntk/nusl-385957.
Full textAbstract:
This Master's thesis is about analysis of Internet of Things project BeeeOn, design and production of unit, integration and system tests and their automation by utilization of Continuous integration system Jenkins CI. The theoretical part is devoted to software testing fundamentals and Continuous integration systems. The main point of this thesis is about specification and description of BeeeOn system, its requirements for automatic testing and its implementation. In conclusion, the results of this work and expansion possibilities are discussed.
18
Mjörnman, Jesper, and Daniel Mastell. "Randomness as a Cause of Test Flakiness." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-177303.
Full textAbstract:
With today’s focus on Continuous Integration, test cases are used to ensure the software’s reliability when integrating and developing code. Test cases that behave in an undeterministic manner are known as flaky tests, which threatens the software’s reliability. Because of flaky test’s undeterministic nature, they can be troublesome to detect and correct. This is causing companies to spend great amount of resources on flaky tests since they can reduce the quality of their products and services. The aim of this thesis was to develop a usable tool that can automatically detect flakiness in the Randomness category. This was done by initially locating and rerunning flaky tests found in public Git repositories. By scanning the resulting pytest logs from the tests that manifested flaky behaviour, noting indicators of how flakiness manifests in the Randomness category. From these findings we determined tracing to be a viable option of detecting Randomness as a cause of flakiness. The findings were implemented into our proposed tool FlakyReporter, which reruns flaky tests to determine if they pertain to the Randomness category. Our FlakyReporter tool was found to accurately categorise flaky tests into the Randomness category when tested against 25 different flaky tests. This indicates the viability of utilizing tracing as a method of categorizing flakiness.
19
Bednář, Martin. "Automatické testování projektu JavaScript Restrictor." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2020. http://www.nusl.cz/ntk/nusl-432879.
Full textAbstract:
The aim of the thesis was to design, implement and evaluate the results of automatic tests for the JavaScript Restrictor project, which is being developed as a web browser extension. The tests are divided into three levels - unit, integration, and system. The Unit Tests verify the behavior of individual features, the Integration Tests verify the correct wrapping of browser API endpoints, and the System Tests check that the extension does not suppress the desired functionality of web pages. The System Tests are implemented for parallel execution in a distributed environment which has succeeded in achieving an almost directly proportional reduction in time with respect to the number of the tested nodes. The benefit of this work is detection of previously unknown errors in the JavaScript Restrictor extension and provision of the necessary information that allowed to fix some of the detected bugs.
20
Mendes, David Jorge Garcia. "Automated Testing for Provisioning Systems of Complex Cloud Products." Master's thesis, 2019. http://hdl.handle.net/10362/92293.
Full textAbstract:
Context: The proliferation of cloud computing enabled companies to shift their approach
regarding infrastructure provisioning. The uprising of cloud provisioning enabled
by virtualisation technologies sprouted the rise of the Infrastructure as a Service
(IaaS) model. OutSystems takes advantage of the IaaS model to spin-up infrastructure
on-demand while abstracting the infrastructure management from the end-users.
Problem: OutSystems’ orchestrator system handles the automated orchestration of the
clients’ infrastructure, and it must be thoroughly tested. Problems arise because infrastructure
provisioning takes considerable amounts of time, which dramatically increases
the feedback loop for the developers. Currently, the duration of the orchestrator tests
hinder the ability to develop and deliver new features at a desirable pace.
Objectives: The goals of this work include designing an efficient testing strategy that
considers a microservices architecture with infrastructure provisioning capabilities while
integrating it in a Continuous Integration (CI)/Continuous Deployment (CD) pipeline.
Methods: The solution applies multiple testing techniques that target different portions
of the system and follow a pre-determined test distribution to guarantee a balanced
test suite. The strategy was tested against a set of prototypes to evaluate its adequacy and
efficiency. The strategy definition focuses on mapping the type of errors that each test
level should tackle and is, therefore, independent of the employed technologies.
Results: The devised strategy is integrated in a CI/CD pipeline and is capable of
comprehensively test the created prototypes while maintaining a short feedback loop. It
also provides support for testing against commonly found errors in distributed systems
in a deterministic way.
Conclusions: The work developed in this dissertation met the outlined objectives, as
the developed strategy proved its adequacy against the developed prototypes. Moreover,
this work provides a solid starting point for the migration of the orchestrator system to a
microservices architecture.
21
Huang, Ya-Ting, and 黃雅亭. "Establishment of Automated Dual-Probing Wafer Testing System Based on Integration of Visual Identification and Laser Sensor." Thesis, 2018. http://ndltd.ncl.edu.tw/handle/b45s85.
Full text
22
Lan, Yi-Hung, and 藍義宏. "The Integrating System of Automatic Testing and Shock Response Spectrum Analysis for Transformer Inrush Current." Thesis, 2008. http://ndltd.ncl.edu.tw/handle/34b64h.
Full textAbstract:
碩士國立虎尾科技大學
電機工程研究所
96
Integration of automatic test of transformer inrush current and shock response spectrum analysis using LabVIEW software is discussed in this thesis. The LabVIEW is a software language with emphasis on computer automation flow chart type. It has strong data acquisition and instrument control ability. It can be applied to analyze and judge data immediately. In this thesis, the LabVIEW is used to measure and analyze inrush current. The experimenttal results are presented by virtual instruments. The purpose of automatic testing and spectrum analysis can be reached. The developed automatic testing system is mainly based on the Programmable System on Chip (PSoC). It is used to design control circuit for function of the automatic testing. Besides, the shock response spectrum analysis method is applied to distinguish transient inrush current from fault current. The developed man-machine interface of the integrating system has good humanistic design. Finally, the integrating system is examined by experimental results with Photon II vibration spectrum analysis instrument. The good accuracy and practicality of the proposed integrating system is uerified from the measured results.
23
Hou, Chao-Jen, and 侯昭仁. "Integrating Kepner–Tregoe Method and theories of TRIZ to Improve Performance by Using an Automatic Testing Equipment System." Thesis, 2013. http://ndltd.ncl.edu.tw/handle/11008796729924514279.
Full textAbstract:
碩士龍華科技大學
商學與管理研究所
101
The purpose of this research is to find out detectable gaps with optical sensors by integrating Kepner–Tregoe Method and TRIZ theory. To verify this approach, an automatic system with testing equipment for detecting the mother board’s position of a smart phone is used. Kepner–Tregoe Method composes of four major parts: 1) Situation appraisal, 2) Problem analysis, 3) Decision analysis, and 4) Potential problem (Opportunity) analysis.Prior to come up with a final soultion, one has to use TRIZ Contradiction Matrix and Inventive Principles to generate lot of possible decisions. “MUST Objectives“of Kepner–Tregoe Method is used to filter out the infeasible decisions and WANT Objectives “ is used to find out the optimal decision. In addition, TRIZ “Substance-Field analysis” was used as an authentication tool to check out its effectiveness of the final decision. Find out the possible risks and disadvantages when the decision is in execution via “Potential Problem (Opportunity) Analysis”. Some errorous behavior of the robot might activate micro switches in automatic detection systems. The problem of the defective product originates from a robotic arms’ positioning accuracy when the device locates the substrate. Our research proposes the use of infrared transmitter and sensor to replace the original micro switch inductive components after the applying the integrating TRIZ theory and Kepner–Tregoe Method. To show the differences before and after the improving process, researchers used paired-compared tests for the mean in statistics.The result of the hypothesis test indicates that the average number of occurrences of the error is significantly different. It ensures that the yield rate of products was greatly improved. Numerically speaking, the defect rates drop from 56Dppm down to 4 Dppm. This achievement the company directly applies a patent for the infra-red detection gap system.
24
Considine, Breandan. "Programming tools for intelligent systems." Thesis, 2020. http://hdl.handle.net/1866/24310.
Full textAbstract:
Les outils de programmation sont des programmes informatiques qui aident les humains à programmer des ordinateurs. Les outils sont de toutes formes et tailles, par exemple les éditeurs, les compilateurs, les débogueurs et les profileurs. Chacun de ces outils facilite une tâche principale dans le flux de travail de programmation qui consomme des ressources cognitives lorsqu’il est effectué manuellement. Dans cette thèse, nous explorons plusieurs outils qui facilitent le processus de construction de systèmes intelligents et qui réduisent l’effort cognitif requis pour concevoir, développer, tester et déployer des systèmes logiciels intelligents. Tout d’abord, nous introduisons un environnement de développement intégré (EDI) pour la programmation d’applications Robot Operating System (ROS), appelé Hatchery (Chapter 2). Deuxièmement, nous décrivons Kotlin∇, un système de langage et de type pour la programmation différenciable, un paradigme émergent dans l’apprentissage automatique (Chapter 3). Troisièmement, nous proposons un nouvel algorithme pour tester automatiquement les programmes différenciables, en nous inspirant des techniques de tests contradictoires et métamorphiques (Chapter 4), et démontrons son efficacité empirique dans le cadre de la régression. Quatrièmement, nous explorons une infrastructure de conteneurs basée sur Docker, qui permet un déploiement reproductible des applications ROS sur la plateforme Duckietown (Chapter 5). Enfin, nous réfléchissons à l’état actuel des outils de programmation pour ces applications et spéculons à quoi pourrait ressembler la programmation de systèmes intelligents à l’avenir (Chapter 6).Programming tools are computer programs which help humans program computers. Tools come in all shapes and forms, from editors and compilers to debuggers and profilers. Each of these tools facilitates a core task in the programming workflow which consumes cognitive resources when performed manually. In this thesis, we explore several tools that facilitate the process of building intelligent systems, and which reduce the cognitive effort required to design, develop, test and deploy intelligent software systems. First, we introduce an integrated development environment (IDE) for programming Robot Operating System (ROS) applications, called Hatchery (Chapter 2). Second, we describe Kotlin∇, a language and type system for differentiable programming, an emerging paradigm in machine learning (Chapter 3). Third, we propose a new algorithm for automatically testing differentiable programs, drawing inspiration from techniques in adversarial and metamorphic testing (Chapter 4), and demonstrate its empirical efficiency in the regression setting. Fourth, we explore a container infrastructure based on Docker, which enables reproducible deployment of ROS applications on the Duckietown platform (Chapter 5). Finally, we reflect on the current state of programming tools for these applications and speculate what intelligent systems programming might look like in the future (Chapter 6).