To see the other types of publications on this topic, follow the link: Test automation.
Dissertations / Theses on the topic 'Test automation'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'Test automation.'
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
Lindholm, David. "Economics of Test Automation : Test case selection for automation." Thesis, Linköpings universitet, Programvara och system, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-154941.
Full textAbstract:
In this thesis a method for selecting test cases for test automation is developed and evaluated. Existing methods from the literature has been reviewed and modified resulting in the proposed method, a decision tree containing 23 factors grouped into 8 decision points. The decision tree has been used and evaluated in an industrial setting. The economic benefits were calculated with return on investment and the organisational benefits were measured in a survey at a software producing company. The result was that automated tests, selected with the decision tree, provided economic benefits after 0.5 to 4 years, these tests were also found leading to 3 organisational benefits: less human effort when testing, reduction in cost and allowing for shorter release cycles.
2
Andersson, Viveka. "Test Platform for Automation System." Thesis, KTH, Reglerteknik, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-107496.
Full textAbstract:
There are different automation systems to control processes in industry. One of them is DeltaV, which is a product from Emerson Process Management. Recently, Sandvik Coromant, bought the DeltaV automation system for using it in production. To increase the knowledge about DeltaV at Sandvik Coromant a project was initiated with the aim to create a test platform and a course compendium for self learning. This thesis describes how the test platform was developed and its functionality.För att styra processer i industrin finns det olika styrsystem. Ett av dessa är DeltaV, som är en produkt från Emerson Process Management. Nyligen köpte Sandvik Coromant styrsystemet DeltaV för att använda det i sin produktion. För att öka kunskapen om DeltaV på Sandvik Coromant initierades ett projekt: Att utforma en test plattform och ett kurskompendium för självlärning. Denna uppsats beskriver hur tesplattformen har utvecklats och dess funktionalitet.
3
Ahmed, Abdifatah, and Magnus Lindhe. "Efficient And Maintainable Test Automation." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4513.
Full textAbstract:
More and more companies experience problems with maintainability and time-consuming development of automated testing tools. The MPC department at Ericsson Software Technology AB use methods and tools often developed during time pressure that results in time-consuming testing and requires more effort and resources than planned. The tools are also such nature that they are hard to expand, maintain and in some cases they have been thrown out between releases. For this reason, we could identify two major objectives that MPC want to achieve; efficient and maintainable test automation. Efficient test automation is related to mainly how to perform tests with less effort, or in a shorter time. Maintainable test automation aims to keep tests up to date with the software. In order to decide how to achieve these objectives, we decided to investigate which test to automate, what should be improved in the testing process, what techniques to use, and finally whether or not the use of automated testing can reduce the cost of testing. These issues will be discussed in this paper.
4
Petrenko, V. "Test automation for web applications." Thesis, Видавництво СумДУ, 2012. http://essuir.sumdu.edu.ua/handle/123456789/26056.
Full textAbstract:
Most software applications today are written as web-based applications to be run in Internet browser. The effectiveness of these applications testing varies widely among companies and organiza-tions. In the era of highly interactive and responsible software processes when a lot of organizations use some forms of Agile methodology, test automation is becoming a current requirement for software projects. Test automation often gives the answer. This process means using a software tool to run repeatable tests against the application to be tested. It provides quality of regression testing.
When you are citing the document, use the following link http://essuir.sumdu.edu.ua/handle/123456789/26056
5
Strålfors, Annika. "Making test automation sharable: The design of a generic test automation framework for web based applications." Thesis, KTH, Skolan för datavetenskap och kommunikation (CSC), 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-240981.
Full textAbstract:
The validation approach for assuring quality of software does often include the conduction of tests. Software testing includes a wide range of methodology depending on the system level and the component under test. Graphical user interface (GUI) testing consists of high level tests that assert that functions and design element in user interfaces work as expected. The research conducted in this paper focused on GUI testing of web based applications and the movement towards automated testing within the software industry. The question which formed the basis for the study was the following: How should a generic test automation framework be designed in order to allow maintenance between developers and non-developers? The study was conducted on a Swedish consultant company that provides e-commerce web solutions. A work strategy approach for automated testing was identified and an automation framework prototype was produced. The framework was evaluated through a pilot study where testers participated through the creation of a test suite for a specific GUI testing area. Time estimations were collected as well as qualitative measurements through a follow up survey. This paper presents a work strategy proposal for automated tests together with description of the framework system design. The results are presented with a subsequent discussion about the benefits and complexity of creating and introducing automated tests within large scale systems. Future work suggestions are also addressed together with accountancy of the frameworks usefulness for other testing areas besides GUI testing.
6
Wang, Lei. "GUI test automation for Qt application." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-121719.
Full textAbstract:
GUI test automation is a popular and interesting subject in the testing industry. Many companies plan to start test automation projects in order to implement efficient, less expensive software testing. However, there are challenges for the testing team who lack experience performing GUI tests automation. Many GUI test automation projects have ended in failure due to mistakes made during the early stages of the project. The major work of this thesis is to find a solution to the challenges of establishing new test automation projects and determine an appropriate method to build GUI tests automation. Due to the particularity of GUI tests automation, keyword driven test approach is introduced in this thesis. The advantages and disadvantages are shown by undertaking comparison with the Record and replay testing method and the data driven testing method. The research also includes a feasibility study of GUI tests automation. The analysis report points out which kinds of test projects should be automated and which kinds should not be automated. Test automation tool selection is a critical step for an test automation project. This thesis shows the correct procedure for selecting a testing tool and explains the strategies of testing tool selection. It also summaries the mistakes made during the tool selection process. Several classical types of testing tools which support Qt software testing are compared and evaluated. Based on the in-depth analysis and comparison of testing tools, the thesis explains how the different tools fit with the different test projects. The implementation procedure of a test automation is demonstrated in this thesis. The procedure includes test case design and testing framework implementation. The test script is created based on the structure of a keyword driven test framework. The thesis also discusses several interesting topics related to GUI tests automation for future research.
7
Cruz, Alfredo. "Evolutionary Algorithms for VLSI Test Automation." NSUWorks, 2002. http://nsuworks.nova.edu/gscis_etd/472.
Full textAbstract:
The generation of binary test patterns for VLSI devices belongs to the class of NP complete problems. As the complexity of VLSI circuits increases, the time to generate test vectors becomes computationally expensive. This dissertation focuses on an evolutionary algorithm (EA) approach for the generation of effective test vectors for single and multiple fault detection in VLSI circuits. EAs provide significant speedup while retaining good quality solutions through heuristic procedures. Although not guaranteed to find optimal solution, EAs are able to find very good solutions for a wide range of problems. Three basic steps are performed during the generation of the test vectors: selection, crossover, and mutation. In the selection step, a bias roulette-wheel and the steady state are used as the reproduction operators. The new candidate test vectors with the highest fitness function replace the old ones, once crossover and mutation occur. Using this scheme, population members steadily improve their fitness level with each generation. A new mutation operator is introduced that increases the Hamming distance among the candidate solutions for shrinkage faults in Programmable Logic Arrays (PLAs). The genetic operators (selection, crossover, and mutation) are applied to the CNF-satisfiability problem for the generation of test vectors for growth faults in PLAs. The CNF constraints satisfaction problem has several advantages over other approaches used for PLA testing. The method proposed eliminates the possibility of intersecting a redundant growth term with a valid candidate test vector. The genetic operator, unlike previous operators used in PLA test generation, does not use lookups or backtracking. That is, the CNF technique eliminates operations (such as backtracking and sharp (#) operation) that can become intractable with increasing PLA size. The proposed evolutionary algorithms based solution aims to address the shortcoming of the existing methods for VLSI testing. Deterministic procedures were used to allow the identification of untestable faults and to improve the fault coverage. This hybrid deterministic/genetic test generator helps improve fault effectiveness and reduce CPU time run. Experimental results have confirmed that the number of untestable faults identified contributed to test generation effectiveness .
8
August, Tynong. "Automated test process." Thesis, Uppsala universitet, Signaler och System, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-396275.
Full textAbstract:
This thesis investigates solutions to automate a lab process and give the customer basis for investment. An analysis of the current lab process and interviews with the staff were performed to set requirements for an automated solution. The customer wants to perform an analysis on a large number of combinations between antibiotics and bacteria. The issues that an automated solution is not able to handle were identified for the customer. A market analysis of existing solutions was preformed and contact was established with different suppliers. The suggested products were evaluated by performance and if they would be able to adapt to the process. The evaluation shows that with the same number of working hours the customer can increase the productivity with 6.7 times using a semi-automated system and a fully-automated system will result in an increase of 18.3 times. A guidance of how the customer will implement the system is described in the report. The report shows that an automated solution will make their process more efficient.
9
Eiderbrant, Tobias. "Automating a test method for a hybrid test environment." Thesis, Linköping University, Department of Computer and Information Science, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-57646.
Full textAbstract:
Ericsson has a very big and expensive test environment with a lot of GSM AXE equipment. In order to decrease the cost of testing Ericsson has developed a combination of simulated and real hardware, the Hybrid Test Environment (HTE). There is no formal supervision and testing of the HTE system today and this has left the HTE system unstable and the testers have been avoiding using HTE. It is important for Ericsson that the confidence for HTE will increase. The goal of this thesis is to produce a method for testing the HTE system. An automated test tool has been implemented in order to monitor and test the HTE system. During the two weeks that the test tool has been operational it has discovered 4 servers in 3 different HTE rigs that malfunctioned. These servers were fixed and were operational before the end-users could discover any problem.
10
Liu, Yike. "WCDMA Test Automation Workflow Analysis and Implementation." Thesis, KTH, Kommunikationssystem, CoS, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-91528.
Full textAbstract:
In the modern wireless communication industry, radio communication equipment vendors not only produce communication hardware, but also produce software. In fact, software revenue is now a large part of the total revenue. As technology has developed and traffic demands increase, more and more functions required to implement the radio system are implemented via software rather than hardware. Today, many hardware functions are actually implemented with reconfigurable and programmable hardware. Therefore, it is often possible to perform an upgrade by loading new software (a software upgrade) rather than needing to change the physical hardware with every technology advance. However, introducing new elements and features in existing (often mature) software may cause unexpected problems. These problems may include new parts malfunctioning and failure or degradation of old functions. To avoid these problems, each version of software has to be thoroughly tested, not only to test the new parts, but also to verify that the old functions still work properly. Testing all the old functions is time and human resource consuming. Thus, there is an increasing demand for automated testing. This thesis will focus on why automated regression testing is necessary and how to implement automated testing in a specific environment. The thesis results show that automated testing can improve the test coverage by at least 40% for one of Ericsson’s WCDMA software releases. This coupled with a reduction in testing time enables more rapid development by significantly reducing the test time without compromising quality. All of these results lead to improved profitability and increased customer satisfaction.I den moderna trådlösa kommunikationen industrin, radioutrustning leverantörerna inte bara producera kommunikation hårdvara, utan också producera mjukvara. Faktum är programvara inkomster är nu en stor del av de totala inkomsterna. Eftersom tekniken har utvecklat och trafik krav ökar, fler och fler funktioner som krävs att genomföra radiosystem genomförs via mjukvara istället för maskinvara. Många hårdvara fungerar faktiskt genomförs med omkonfigurerbara och programmerbar hårdvara. Därför är det ofta möjligt att utföra en uppgradering av lastning ny programvara (en mjukvaruversionen) snarare än behöver för att ändra den fysiska hårdvaran med varje teknik förväg. Men att införa nya element och funktioner i befintliga (ofta äldre) programvara kan orsaka oväntade problem. Dessa problem kan innehålla nya delar brister och fel eller försämring av gamla funktioner. För att undvika dessa problem, varje version av programvaran måste testas, inte bara att testa de nya delarna, men även för att kontrollera att de gamla funktionerna fortfarande arbete ordentligt. Testa alla gamla funktioner konsumera tid och personal. Således finns det en ökad efterfrågan på automatiserade tester. Den här avhandlingen kommer att fokusera på varför automatiserad regression testning krävs och hur man genomföra automatiserade tester i en viss miljö. Avhandlingen visar att automatiserade tester kan förbättra testbunt täckning med minst 40% för ett av Ericssons WCDMA programversionerna. Detta i kombination med en minskning av provning tid möjliggör en snabbare utveckling av avsevärt minska test tid utan att kompromissa med kvaliteten. Alla dessa resultat leda till bättre lönsamhet och ökat kundvärde belåtenhet.
11
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
12
Tuovinen, J. (Jarno). "Mobile game test automation with image recognition." Master's thesis, University of Oulu, 2018. http://urn.fi/URN:NBN:fi:oulu-201802131231.
Full textAbstract:
In the sequel of mobile game industry, testing is recognized as a key factor that can either boost or halt the game development. Indeed, the growth speed of mobile industry has led to decreasing quality in the apps and the employed testing tools. The wide spectrum of device hardware and software, so called fragmentation, makes it a lot slower to test the application on devices. Besides, there are more inherent technical issues to test games as compared to other mobile applications. The lack of efficient tools for testing robustness, quality and computational efficiency has been acknowledged by the game industry. This unmet need has motivated the work highlighted in this thesis which aims to explore easy and efficient approaches to generate test automation code for mobile games. First, to identify difficulties, challenges and good practices that mobile game developers face, a questionnaire-based analysis has been conducted and evaluated. Second, a new Android mobile game testing tool, called MAuto, has been developed and deployed. MAuto is developed to be compatible with Appium, open source test automation framework. MAuto is a tool that utilizes its user’s input to generate Appium test automation code which can be run on the same or any other Android device. The system consists of three elements: the user, the browser, and the mobile device. Once the user has launched MAuto, all the interaction between the user and the tool happens with the browser. During the rerun, MAuto utilizes AKAZE algorithm to recognize the location of the object and repeats the user input with Appium. Consequently, MAuto has been used in developing test automation code to play the tutorial scene of the mobile game Clash of Clans. MAuto is designed to be a friendly mobile test creator that, with minimal amendments, can be exported to other testing applications in alternative platforms, e.g. iOS. Nevertheless, the thesis also acknowledges the limitations in the image-recognition based test automation methods where the negative impact of change of configuration, lack of luminosity, and non-exhaustive list of models cannot be ignored. On the other hand, the thesis also reviews the existing tools and current practices in mobile game testing, providing a comparable analysis for both researchers and developer communitiesMobiilipeliteollisuudessa testauksen on havaittu olevan avaintekijä, joka voi nopeuttaa tai hidastaa pelinkehitystä. Mobiiliteollisuuden kasvunopeus on johtanut applikaatioiden ja testaustyökalujen laadun heikkenemiseen. Laitteistojen ja ohjelmistojen laaja kirjo, niin kutsuttu fragmentaatio, hidastaa applikaatioiden testausta laitteilla. Lisäksi peleissä on enemmän niille ominaisia teknisiä ongelmia verrattuna muihin mobiiliapplikaatioihin. Peliteollisuudessa on huomattu, ettei ole olemassa riittävän tehokkaita työkaluja pelien vakauden, laadun ja tehokkuuden testaamiseen. Tämä diplomityö pyrkii vastaamaan tähän tarpeeseen. Työn tarkoitus on löytää helppoja ja tehokkaita lähestymistapoja testiautomaatiokoodin kehittämiseksi mobiilipeleille. Ensimmäiseksi on toteutettu kyselypohjainen analyysi, jotta voitaisiin selvittää mobiilikehittäjien kohtaamat vaikeudet ja haasteet sekä löytää heille parhaat käytänteet. Toiseksi on kehitetty uusi Android-pelien testaustyökalu, MAuto, joka on tarkoitettu erityisesti helpottamaan pelien testausta mutta joka toimii myös muilla applikaatioilla. MAuto on yhteensopiva Appiumin kanssa, joka on avoimen lähdekoodin testiautomaatioviitekehys. MAuto on työkalu, jolla voi luoda testaajan syötteistä Appium-testiautomaatiokoodia. Testikoodia voidaan ajaa uudelleen millä tahansa Android-laitteella. Järjestelmä koostuu kolmesta osasta: käyttäjästä, selaimesta ja mobiililaitteesta. Kun käyttäjä on käynnistänyt MAuton, interaktio käyttäjän ja työkalun välillä tapahtuu selaimessa. Kun testi ajetaan uudelleen, MAuto toistaa käyttäjän syötteen tunnistetussa sijainnissa hyödyntämällä AKAZE-algoritmia ja Appiumia. MAutoa on käytetty esimerkiksi luomaan testiautomaatiokoodi, joka pelaa Clash of Clans -peliä. MAuto on suunniteltu käyttäjäystävälliseksi, ja pienellä vaivalla sitä voidaan laajentaa kattamaan useampia käyttöjärjestelmiä, kuten iOS. Diplomityö käsittelee myös kuvantunnistukseen perustuvien työkalujen heikkouksia, kuten kuvantunnistuksen tunnistustehokkuutta verrattuna natiiviin objektintunnistukseen ja muuttuvien grafiikoiden aiheuttamia ongelmia testauksessa. Myös MAuton heikkouksia on käsitelty liittyen erityisesti sen nopeuteen ja toimintavarmuuteen peleissä, joissa grafiikan valaistus muuttuu tai peli on nopeatempoinen. Lisäksi työ arvioi olemassa olevia tekniikoita ja työkaluja ja tarjoaa vertailukelpoisen analyysin niin tutkijoille kuin kehittäjillekin
13
Petersson, Karl. "Test automation in a CI/CD workflow." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-96253.
Full textAbstract:
The procedure of testing the implemented software is important and should be an essential and integrated part of the development process. In order for the testing to be meaningful it is important that the testing procedure ensures that the developed software meet certain requirements. The testing procure is often controlled by some sort of test specification. For many companies it is desirable to automate this procure. The focus of this thesis has been to automate a small subpart of the manual tests today performed related to SAAB:s air traffic management system. The automation has been achieved by studying the existing test specification which involves a lot of manual operations and to write software that mimics a few of these test cases. The thesis has resulted in a test framework which automates a small subset of the manual tests performed today. The framework has been designed to be scalable and to easily allow more test cases to be added by the personnel when time permits. The test framework has also been integrated with SAAB:s existing CI/CD workflow.
14
Almeida, Cardoso F. J. "A distributed system for laboratory process automation." Thesis, University of Manchester, 1988. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.329584.
Full text
15
Hussain, Ambreen. "Use of domain-specific language in test automation." Thesis, Cranfield University, 2013. http://dspace.lib.cranfield.ac.uk/handle/1826/8050.
Full textAbstract:
The primary aim of this research project was to investigate techniques to replace the complicated process of testing embedded systems in automotive domain. The multi-component domain was composed of different hardware to be used in testing procedure which increased the level of difficulty in testing for an operator. As a result, an existing semi-automated testing procedure was replaced by more simpler and efficient framework (ViBATA). A key step taken in this scenario was the replacement of manual GUI interface with the scriptable one to enhance the automation. This was achieved by building a Domain-specific language which allowed test definition in the form of human readable scripts which could be stored for later use.
A DSL is a scripting language defined for a particular domain with compact expressiveness. In this case the domain is testing embedded systems in general and automotive systems in particular. The final product was a test case specification document in the form of XML as an output of generated code from this DSL which will be input to ViBATA to make test specification component automated.
In this research a comparative analysis of existing DSLs for alternative domains and investigation of their applicability to the presented domain was also performed. The technologies used in this project are Xtext to define the DSL grammar, Xtend to generate code in Java and Simple framework to generate output in XML. The stages involved in DSL development and how these stages were implemented is covered in this thesis.
The developed DSL for this domain is tested for automotive and calculator systems in this thesis which proved that this is more general and flexible. The DSL is consistent, efficient and automated test specification component of testing framework in embedded systems.
16
Sousa, Lucas Benedito dos Reis, Nelson Paiva Oliveira Leite, Fernando Walter, and Wagner Chiepa Cunha. "AUTOMATION SYSTEM FOR THE FLIGHT TEST LABORATORY (SALEV)." International Foundation for Telemetering, 2006. http://hdl.handle.net/10150/603934.
Full textAbstract:
ITC/USA 2006 Conference Proceedings / The Forty-Second Annual International Telemetering Conference and Technical Exhibition / October 23-26, 2006 / Town and Country Resort & Convention Center, San Diego, CaliforniaA novel Automation System for the Flight Test Laboratory (SALEV) is developed in full compliance with EA-4/02 Standard (i.e. Expression of the Uncertainty of Measurement in Calibration) to compute the uncertainty of the measurement at the calibration laboratory of the Flight Tests Group (GEEV). The GEEV performs flight test campaigns to certificate and/or develop aircrafts and its systems. Then, flight tests instrumentation (FTI) systems are developed and installed in the test bed. The FTI data acquisition complies with IRIG Standard. The FTI is composed by a data acquisition system, which performs signal conditioning, sampling and quantization of all measurements provided by a set of transducers. All parameters are coded in a PCM format and represented in a non-dimensional numerical form (i.e. counts).To allow the establishment of a relation between the non-dimensional form and the physical quantity, a calibration process is carried out to provide the coefficients of a calibration curve. This process is also used to determine the systematic and random errors (i.e. the uncertainty). The accuracy and reliability of calibration process should comply with the requirements, which are customized for each flight test campaign. The satisfactory performance of the SALEV calibration process is achieved by automation in all steps. The SALEV development is presented, which includes the following steps: · Database definition; · Study of all steps and parts that forms the calibration process (i.e. from transducer to final uncertainty determination) to determine its associated uncertainties; · Automation of the entire calibration process (including the process itself up to the effective control of standard and instruments); · Development of algorithms to compute the uncertainty compliant with EA 4/02; and · System validation in compliance with ISO/IEC 17025. As result of the SALEV operation, it could be verified that measurement quality was improved, and the required time for calibration was substantially reduced. Also the standardization of this process allows failures forecast due to aging of systems parameters (i.e. bias).
17
Daag, Jonas. "A strategy development for test automation of Intasma®." Thesis, Linköpings universitet, Institutionen för teknik och naturvetenskap, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-94411.
Full textAbstract:
Ipendo Systems is a software development company that provides a web-based system for managing Intellectual Properties, Intasma™. The testing process of Intasma™ so far has been done manually and not to the desired extent. An evaluation of two different test automation tools was carried out and a number of difficulties arose when a small implementation was done and that contributed to the conclusion of focusing on how to generate more significant test cases.
18
Lo, Chi Lik Eric. "Test automation for database management systems and database applications /." Zürich : ETH, 2007. http://e-collection.ethbib.ethz.ch/show?type=diss&nr=17271.
Full text
19
Laurén, Rebecka. "Investigating GUI test automation ROI : An industrial case study." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-28314.
Full textAbstract:
This report is the proof of concept that shows how Coded UI can be used for the automation of GUI tests. For this thesis-work, an industrial case study is done on 26 different test cases provided at the company Basalt AB. The problem they had was that testing was very time consuming and was therefore not done as often as needed to keep the level of quality required for the system developed. The method that has been used are called the validation method and the work was according to that divided into five steps: choosing test cases, a learning process, implementation, compare the results and then draw conclusions. Test automation has benefits of time savings and the fact that tests will be reused. Testing will take minutes instead of hours and the tests can be executed over and over again as many times as needed. So by changing from manual testing to automated testing, tests can be run faster and therefore more often. The investment of automated testing will be repaid before the end of the fourth test round. So conclusions can be drawn from the results of this thesis and it shows that it absolutely is worth the investment of automating the testing process.
20
REZENDE, BRUNO LOUREIRO. "A FRAMEWORK FOR TEST AUTOMATION WITH CONFIGURABLE SPECIFICATION LANGUAGES." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2009. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=14997@1.
Full textAbstract:
Nesse trabalho foi criado um framework para a realização de testes
automatizados de acordo com as práticas de desenvolvimento dirigido por testes,
o qual pode ser estendido com novas linguagens de especificação, utilizando
idéias de desenvolvimento dirigido por comportamentos. Espera-se que, ao
utilizar esse framework, equipes de projetos de software possam especificar testes
em uma linguagem mais adequada para o domínio de sua aplicação, através do
suporte de uma ferramenta que permita tal nível de personalização. O framework
foi instanciado com a criação de uma linguagem baseada em máquinas de estado,
utilizada para a aplicação da ferramenta em um projeto real. O objetivo deste
trabalho é avaliar os impactos da aplicação dessas técnicas, através da experiência
de utilização da ferramenta no projeto. A motivação para esse trabalho surgiu da
experiência no desenvolvimento de sistemas de controle, usualmente reativos e
com requisitos de tempo real, nos quais muitas vezes a descrição de seus
comportamentos é feita através de máquinas de estado, que possivelmente é a
melhor linguagem para este domínio.In this work we create a framework for automated testing according to test driven development practices that can be extended to support new specification languages, following ideas from behavior driven development. We expect that, by using this framework, software development teams will be able to specify tests in more proper languages for the application domain, with the support of a tool that allows such level of customization. The framework was instantiated with the creation of a language based on state machines, and used on a real-life project. The goal of this work is that software project teams become able to specify tests in the most fitting language for their application domain, through the support of a tool that makes possible such level of customization. The motivation for this work comes from the experience with the development of control systems, usually with real-time requirements, which often have their behaviors described by state machines, possibly the best language for this domain.
21
Imamovic, Nermin. "TEST ORACLE AUTOMATION WITH MACHINE LEARNING : A FEASIBILITY STUDY." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-49280.
Full textAbstract:
The train represents a complex system, where every sub-system has an important role. If a subsystem doesn’t work how it should, the correctness of whole the train can be uncertain. To ensure that system works properly, we should test each sub-system individually and integrate them together in the whole system. Each of these subsystems consists of the different modules with different functionalities what should be tested. Testing of different functionalities often requires a different approach. For some functionalities, it is necessary domain knowledge from the human expert, such as classification of signals in different use cases in Propulsion and Controls (PPC) in Bombardier Transportation. Due to this reason, we need to simulate of using experts knowledge in the certain domain. We are investigating the use of machine learning techniques for solving this cases and creating system what will automatically classify different signals using the previous human knowledge. This case study is conducted in Bombardier Transportation (BT), Västerås in departments Train Control Management System (TCMS) and Propulsion and Controls (PPC), where data is collected, analyzed and evaluated. We proposed a method for solving the oracle problem based on machine learning approach for different for certain use case. Also, we explained different steps what can be used for solving the test oracle problem where signals are part of verdict process
22
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 textAbstract:
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.
23
Jones, Charles H. "TOWARDS FULLY AUTOMATED INSTRUMENTATION TEST SUPPORT." International Foundation for Telemetering, 2007. http://hdl.handle.net/10150/604521.
Full textAbstract:
ITC/USA 2007 Conference Proceedings / The Forty-Third Annual International Telemetering Conference and Technical Exhibition / October 22-25, 2007 / Riviera Hotel & Convention Center, Las Vegas, NevadaImagine that a test vehicle has just arrived at your test facility and that it is fully instrumented with sensors and a data acquisition system (DAS). Imagine that a test engineer logs onto the vehicle’s DAS, submits a list of data requirements, and the DAS automatically configures itself to meet those data requirements. Imagine that the control room then contacts the DAS, downloads the configuration, and coordinates its own configuration with the vehicle’s setup. Imagine all of this done with no more human interaction than the original test engineer’s request. How close to this imaginary scenario is the instrumentation community? We’re not there yet, but through a variety of efforts, we are headed towards this fully automated scenario. This paper outlines the current status, current projects, and some missing pieces in the journey towards this end. This journey includes standards development in the Range Commander’s Council (RCC), smart sensor standards development through the Institute of Electrical and Electronics Engineers (IEEE), Small Business Innovation Research (SBIR) contracts, efforts by the integrated Network Enhanced Telemetry (iNET) project, and other projects involved in reaching this goal.
24
Engdahl, Daniel. "Development of a Test Platform for the Automation System DeltaV." Thesis, KTH, Reglerteknik, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-106254.
Full textAbstract:
This report describes the development of a test platform and a self study course for the process automation system DeltaV. Sandvik started using this process automation system in 2004. In order to educate personnel in the system without having to disrupt any production lines an educational test platform was needed. The test platform that was developed in this project made use of the same production instruments as the actual production process. The test platform consisted of a physical process automated with a control database developed with DeltaV control software. One important aspect to the development was that the platform was designed to be portable. This is still a part that could be improved.
25
Schinner, Charles Edward 1957. "Electronic manufacturing test cell automation and configuration using AI techniques." Thesis, The University of Arizona, 1990. http://hdl.handle.net/10150/278327.
Full textAbstract:
This thesis utilizes artificial intelligence techniques and problem specific knowledge to assist in the design of an manufacturing test cell for electronic products. The electronic printed circuit board (PCB) is subjected to one or more functional evaluation(s) during the manufacturing process. The purpose of these evaluations is to assure product quality. This thesis is focused on, with historical knowledge, the configuration of this testing environment and associated fault isolation processes. By using such knowledge, an improvement in the testing efficiency will be realized which will allow the overall product cost to be minimized.
26
COSTA, ANDREW DINIZ DA. "AUTOMATION OF THE MANAGEMENT PROCESS OF THE TEST OF SOFTWARE." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2012. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=21177@1.
Full textAbstract:
PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIROCONSELHO NACIONAL DE DESENVOLVIMENTO CIENTÍFICO E TECNOLÓGICO
Teste de software é uma atividade crítica no processo de desenvolvimento de sistemas, principalmente devido ao aumento da complexidade das aplicações atuais e pelo impacto que tais aplicações podem gerar. Relacionado a essa complexidade, o paradigma de sistemas multiagentes tem sido utilizado especialmente quando entidades pró-ativas, autônomas, autoadaptáveis e distribuídas precisam ser desenvolvidas. Para acompanhar a criação, manutenção e execução dos testes nesses sistemas, torna-se necessária a adoção de um processo de gerência, pois prevê a realização das atividades de planejamento, projeto, execução e acompanhamento dos testes. Visando ajudar nessa gerência, a tese apresenta o Java self-Adaptive Agent Framework for Self- Test (JAAF mais T), framework que permite a criação de agentes autoadaptativos capazes de realizar autoteste, isto é, coordenar a execução dos testes necessários para validar suas autoadaptações. Como diversas informações são usadas para ajudar na gerência desses testes, documentá-las ajuda a entender como evoluir e executá-los. Baseada nessa preocupação, a tese oferece uma nova linguagem de modelagem chamada de UML Testing Profile for Coordination (UTP-C), perfil (profile) da UML que permite a modelagem dessas informações. Por fim, para automatizar o processo de gerência dos testes executados por agentes autoadaptativos, a tese apresenta ferramentas capazes de gerar de forma automática artefatos usados pelo JAAF mais T baseados em modelos UTP-C.
Testing software systems has become a critical activity of software development over time. Especially when the development of complex systems, which are able to self-adapt theirs behaviors when necessary, is becoming extremely common. In this context, the multi-agent system (MAS) paradigm has been used especially when distributed, autonomous and pro-active entities are represented. Aiming to control the creation, maintenance and execution of tests on these systems, it is necessary to adopt a management process that considers the activities of planning, design, execution and monitoring of the tests. In order to help this management, the thesis presents the Java self-Adaptive Agent Framework for Self-Test (JAAF more T), that aims to allow the creation of selfadaptive agents that perform self-tests. Since several data are used to help the management of the tests, documenting them helps to understand how to evolve and execute them. Based on this concern, the thesis offers a new modeling language called UML Testing Profile for Coordination (UTP-C), profile of the UML that allows the modeling of these data. At last, but not least important, tools, which were created to automate the management of the tests executed for selfadaptive agents, are presented to generate useful artifacts used for instances of the JAAF more T based on UTP-C models.
27
Juréen, Tim, and Sigrid Karlsson. "Automation of powder level reading in a tap density test." Thesis, KTH, Materialvetenskap, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-298426.
Full textAbstract:
When using metal powder in any form of production, it needs to be stored, handled and transported. To do this effectively, it is of importance to know how the powders flow and this is governed by a behaviour called flowability. One method of assessing powder flowability is by comparing changes in powder density. The different types of densities are obtained from a tap density test, in which the reading of the powder volume is done through eye measurements. This report aimed to automate the volume reading of the test through image analysis, in order to increase the consistency and reliability of the test. The automation was done using the software ImageJ, where a macro was written to which a videorecording of a tap density test could be uploaded and automatically analysed. The result was a fully functioning macro, capable of analysing the entire test. Placing a strip of electrical tape around the cylinder enabled the powder volume to be tracked continuously. The automated readings were concluded able to provide additional information on how the powder behaved during the test itself and with a higher accuracy than using eye measurements. The method was also deemed less dependent on the person performing the test, despite a manually calibrated volume-scale. The macro achieved optimal results through some prerequisites, involving altering the lighting, background colour and camera placement.När metallpulver används inom någon form av produktion måste det lagras, hanteras och transporteras. För att göra detta effektivt är det viktigt att veta hur ett pulver flödar och detta styrs av en egenskap som kallas flytbarhet (eng. flowability). En metod för att bedöma ett pulvers flytbarhet är genom att observera förändringar i pulvrets densitet, i ett så kallat tappdensitetstest, där avläsningen av pulvervolymen görs med ögonmått. Denna rapport ämnade att automatisera testets avläsning genom bildanalys för att öka testets tillförlitlighet och göra avläsningen mer konsekvent. Automatiseringen gjordes med hjälp av programvaran ImageJ, där ett makro skrevs, till vilket en videoinspelning av ett tappdensitetstest kunde laddas upp och automatiskt analyseras. Resultatet var ett fullt fungerande makro som kunde studera hela testet, och genom att placera en remsa eltejp runt cylindern kunde pulvervolymen analyseras kontinuerligt. De automatiska avläsningarna ansågs kunna ge ytterligare information om hur pulvret betedde sig under själva testet med en högre noggrannhet än genom ögonmått. Testet ansågs också vara mindre beroende av den som genomförde experimentet, trots att volymskalan kalibrerats manuellt. Makron uppnådde optimala resultat genom att ändra vissa parametrar i experimentets uppställning som ljussättning, bakgrundsfärg och kamerans position.
28
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 textAbstract:
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.
29
Bhonsle, Dhruvjit Vilas. "Development of an Automation Test Setup for Navigation Data Processing." Master's thesis, Universitätsbibliothek Chemnitz, 2016. http://nbn-resolving.de/urn:nbn:de:bsz:ch1-qucosa-199331.
Full textAbstract:
With the development of Advanced Driving Assistance Systems (ADAS) vehicles have undergone better experience in field of safety, better driving and enhanced vehicle systems. Today these systems are one of the fastest growing in automotive domain. Physical parameters like map data, vehicle position and speed are crucial for the advancement of functionalities implemented for ADAS.
All the navigation map databases are stored in proprietary format. So for the ADAS application to access this data an appropriate interface has to be defined. This is the main aim of Advance Driver Assistant Systems Interface Specifications (ADASIS) consortium. This new specification allows a coordinated effort of more than one industry to improve comfort and fuel efficiency.
My research during the entire duration of my master thesis mainly focuses on two stages namely XML Comparator and CAN stream generation stages from ADASIS Test Environment that was developed in our company. In this test environment ADASIS Reconstructor of our company is tested against the parameters of Reference Reconstructor provided by ADASIS consortium. The main aim of this environment is to develop a Reconstructor which will adhere to all the specifications given in ADASIS Reconstructor.
My implementation in this master thesis focuses on two stages of test environment setup which are XML Comparison and CAN Stream Generation Tool respectively. Prior to my working, these stages lacked in-depth research and usability features for further working.
30
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 textAbstract:
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
31
Challa, Dinesh Kumar. "Vehicle highway automation." Thesis, Manhattan, Kan. : Kansas State University, 2009. http://hdl.handle.net/2097/2338.
Full text
32
Brammer, Niklas. "Investigation of Automated Terminal Interoperability Test." Thesis, Linköping University, Department of Computer and Information Science, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-10139.
Full textAbstract:
In order to develop and secure the functionality of its cellular communications systems, Ericsson deals with numerous R&D and I&V activities. One important aspect is interoperability with mobile terminals from different vendors on the world market. Therefore Ericsson co-operates with mobile platform and user equipment manufacturers. These companies visit the interoperability developmental testing (IoDT) laboratories in Linköping to test their developmental products and prototypes in order to certify compliance with Ericsson's products. The knowledge exchange is mutual, Ericsson as well as the user equipment manufacturers benefit from the co-operation.
The goal of this master's thesis performed at Ericsson AB is to suggest areas in which the IoDT testing can be automated in order to minimize time consuming and tedious work tasks. Primarily the search should be aimed at replacing manual tasks in use today.
The thesis suggests a number of IoDT tasks that might be subject for automation. Among these one is chosen for implementation. The thesis also includes an implementation part. The task that has been chosen for implementation is the network verification after base station controller software upgrade procedure. This is not a core IoDT function but it implies a lot of work, and is often performed.
The automation project is also supposed to act as a springboard for future automation within IoDT. The forthcoming LTE standard will require a lot of IoDT testing, and therefore the automation capabilities should be investigated. The thesis shows that automation work is possible, and that the startup process is straightforward. Existing tools are easy to use, and well supported. The network verification automated test scope has been successful.
33
Durairaj, Selva Ganesh. "Parallelize Automated Tests in a Build and Test Environment." Thesis, Linköpings universitet, Programvara och system, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-131807.
Full textAbstract:
This thesis investigates the possibilities of finding solutions, in order to reduce the total time spent for testing and waiting times for running multiple automated test cases in a test framework. The “Automated Test Framework”, developed by Axis Communications AB, is used to write the functional tests to test both hardware and software of a resource. The functional tests that tests the software is considered in this thesis work. In the current infrastructure, tests are executed sequentially and resources are allocated using First In First Out scheduling algorithm. From the user’s point of view, it is inefficient to wait for many hours to run their tests that take few minutes to execute. The thesis consists of two main parts: (1) identify a plugin that suits the framework and executes the tests in parallel, which reduces the overall execution time of tests and (2) analyze various scheduling algorithms in order to address the resource allocation problem, which arose due to limited resource availability, while the tests were run in parallel. By distributing multiple tests across several resources and executing them in parallel, help in improving the test strategy, thereby reducing the overall execution times of test suites. The case studies were created to emulate the problematic scenarios in the company and sample tests were written that reflect the real tests in the framework. Due to the complexity of the current architecture and the limited resources available for running the test in parallel, a simulator was developed with the identified plugin in a multi-core computer, with each core simulating a resource. Multiple tests were run using the simulator in order to explore, check and assess if the overall execution time of the tests can be reduced. While achieving parallelism in running the automated tests, resource allocation became a problem, since limited resources are available to run parallel tests. In order to address this problem, scheduling algorithms were considered. A prototype was developed to mimic the behaviour of a scheduling plugin and the scheduling algorithms were implemented in the prototype. The set of values were given as input to the prototype and tested with scenarios described under case studies. The results from the prototype are used to analyze the impact caused by various scheduling algorithms on reducing the waiting times of the tests. The combined usage of simulator along with scheduler prototype helped in understanding how to minimize the total time spent for testing and improving the resource allocation process.
34
Johansson, Henrik. "Automating a test strategy for a protocoldecoder tool." Thesis, Linköping University, Department of Computer and Information Science, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-12432.
Full textAbstract:
Within Ericsson AB, integration and verification activities is done on the network level in order to secure the functionality of the network. Protocol analysers are used to capture the traffic in the network. This results in many log files, which needs to be analysed. To do this, a protocol decoder tool called Scapy/LHC is used. Scapy/LHC is a framework that allows the users to write their own script to retrieve the data they need from the log files. The Scapy/LHC framework is incrementally developed as open source within Ericsson when there are needs for more functionality. This is often done by the users, outside normal working tasks. Because of this, there is almost no testing done to verify that old and new functionality works as expected, and there is no formal test strategy in use today.
The goal of this master’s thesis is to evaluate test strategies that are possible to use on the Scapy/LHC framework. To make the time needed for the testing process as short as possible, the test strategy needs to be automated. Therefore, possible test automation tools shall also be evaluated.
Two possible test strategies and two possible test automation tools are evaluated in this thesis. A test strategy, where the scripts that are written by the users are used, is then selected for implementation. The two test automation tools are also implemented. The evaluation of the implemented test strategy shows that it is possible to find defects in the Scapy/LHC framework in a time efficient way with help of the implemented test strategy and any of the implemented test automation tools.
35
Eldh, Sigrid. "On Test Design." Doctoral thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-13040.
Full textAbstract:
Testing is the dominating method for quality assurance of industrial software. Despite its importance and the vast amount of resources invested, there are surprisingly limited efforts spent on testing research, and the few industrially applicable results that emerge are rarely adopted by industry. At the same time, the software industry is in dire need of better support for testing its software within the limited time available. Our aim is to provide a better understanding of how test cases are created and applied, and what factors really impact the quality of the actual test. The plethora of test design techniques (TDTs) available makes decisions on how to test a difficult choice. Which techniques should be chosen and where in the software should they be applied? Are there any particular benefits of using a specific TDT? Which techniques are effective? Which can you automate? What is the most beneficial way to do a systematic test of a system? This thesis attempts to answer some of these questions by providing a set of guidelines for test design, including concrete suggestions for how to improve testing of industrial software systems, thereby contributing to an improved overall system quality. The guidelines are based on ten studies on the understanding and use of TDTs. The studies have been performed in a variety of system domains and consider several different aspects of software test. For example, we have investigated some of the common mistakes in creating test cases that can lead to poor and costly testing. We have also compared the effectiveness of different TDTs for different types of systems. One of the key factors for these comparisons is a profound understanding of faults and their propagation in different systems. Furthermore, we introduce a taxonomy for TDTs based on their effectiveness (fault finding ability), efficiency (fault finding rate), and applicability. Our goal is to provide an improved basis for making well-founded decisions regarding software testing, together with a better understanding of the complex process of test design and test case writing. Our guidelines are expected to lead to improvements in testing of complex industrial software, as well as to higher product quality and shorter time to market.
36
Blixt, Fanny. "Real-time auto-test monitoring system." Thesis, Luleå tekniska universitet, Institutionen för system- och rymdteknik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:ltu:diva-85824.
Full textAbstract:
At Marginalen Bank, there are several microservices containing endpoints that are covered bytest automation. The documentation of which microservices and endpoints that are covered byautomated tests is currently done manually and is proven to contain mistakes. In the documentation, the test coverage for all microservices together and for every individual microserviceis presented. Marginalen Bank needs a way to automate this process with a system that cantake care of test coverage documentation and present the calculated data. Therefore, the purpose of this research is to find a way to create a real-time auto-test monitoring system thatautomatically detects and monitors microservices, endpoints, and test automation to documentand present test automation coverage on a website. The system is required to daily detect andupdate the documentation to be accurate and regularly find eventual changes. The implemented system that detects and documents the test automation coverage is calledTest Autobahn. For the system to detect all microservices, a custom hosted service was implemented that registers microservices. All microservices with the custom hosted service installedand extended to registers to Test Autobahn when deployed on a server. For the system todetect all endpoints of each microservice, a custom middleware was implemented that exposesall endpoints of a microservice with it installed. For the microservices to be able to install theseand get registered, a NuGet package containing the custom hosted service and the custom middleware, was created. To detect test automations, custom attributes models were created thatare supposed to be inserted into each test automation project. The custom attributes are placedin every test class and method within a project, to mark which microservice and endpoint thatis being tested within every automated test. The attributes of a project can be read throughthe assembly. To read the custom attributes within every test automation project, a consoleapplication, called Test Autobahn Automation Detector (TAAD), was implemented. TAADreads the assembly to detect the test automations and sends them to Test Autobahn. Test Autobahn couples the found test automation to the corresponding microservices and endpoints.TAAD is installed and ran on the build pipeline in Azure DevOps for each test automationproject to register the test automations. To daily detect and update the documentation of the test coverage, Quartz.NET hosted serviceis used. With Quartz.NET implemented, Test Autobahn can execute a specified job on a schedule. Within the job, Test Autobahn detects microservices and endpoints and calculates the testautomation coverage for the detection. The calculation of the test coverage from the latestdetection is presented on the webpage, containing both the test coverage for all microservicestogether and the test coverage for each microservice. According to the evaluations, the systemseems to function as anticipated, and the documentation is displaying the expected data.
37
Pradhan, Ligaj. "User Interface Test Automation and its Challenges in an Industrial Scenario." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-14126.
Full textAbstract:
The growing demand for UI test automation has triggered the development of many tools. Researchers and developers have been continuously working to further improvise the existing approaches. If we look at GUI test evolution we can observe a clear progress from manual testing towards complete automation. Numerous approaches have been made to automate the GUI testing process. Record and playback tools, key-word driven methodologies, event flow exploration strategies, model based approaches are continuously evolving with higher level of automation. Similarly, new ideas and strategies to make these tests efficient are also emerging. Optimization of this resource consuming activity is another very important aspect in this area. Dependencies between different tests can create deadlock scenarios, while running larger test suites. A concept of Ordered Test Suite can be used to cope with such dependencies. Following the Model Driven Architecture initiative by Object Management Group, a new global trend of Model Driven Engineering is creating a big sensation in the field of model based software development. Using the same principle, studies have also been made to automatically generate tests from models. Behavioral models can be made using the model driven approaches and these models can be analyzed to generate tests automatically. This master thesis addresses different approaches made for Graphical User Interface test automation, some optimization issues and solutions, a case study done at a software company to automate User Interface testing and a model driven approach for automatic test case generation.
38
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 textAbstract:
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.
39
Polepalle, Chahna, and Ravi Shankar Kondoju. "Evidence and perceptions on GUI test automation : An explorative Multi-Case study." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-15455.
Full textAbstract:
Context. GUI-based automation testing is a costly and tedious activity in practice. As GUIs are well-known for being modified and redesigned throughout the development process, the corresponding test scripts are not valid anymore thereby being a hindrance to automation. Hence, substantial effort is invested in maintaining GUI test scripts which often leads to rework or waste due to improper decisions. As a result, practitioners have identified the need for decision support regarding when should GUI automation testing begin and how to make it easier and also identify what are the factors leading to waste in GUI-based automation testing. The current literature provides solutions relating to automation in general and few answers for GUI based-automation testing. Such generic answers might not be applicable to GUI test automation and also industries new to GUI development and testing. Thus, it is necessary to validate if the general solutions are applicable to GUI test automation and find additional answers that are not identified previously from practitioners opinions in an industrial context. Objectives. Capture relevant information regarding the current approach for GUI test automation within the subsystems from a case company. Next, identify the criteria for when to begin automation, testability requirements and factors associated with waste from literature and practice. Methods. We conducted a multiple-case study to explore opinions of practitioners in two subsystems at a Swedish telecommunication industry implementing GUI-automation testing. We conducted a literature review to identify answers from scientific literature prior to performing a case study.A two-phased interview was performed with different employees to collect their subjective opinions and also gather their opinions on the evidence collected from the literature. Later, Bayesian synthesis method was used to combine subjective opinions of practitioners with research-based evidence to produce context-specific results. Results. We identified 12 criteria for when to begin automation, 16 testability requirements and 15 factors associated with waste in GUI test automation.Each of them is classified into categories namely SUT-related,test-process related, test-tool related, human and organizational, environment and cross-cutting. New answers which were not present in the existing literature in the domain of the research are found. Conclusions. On validating the answers found in literature, it was revealed that the answers applicable for software test automation, in general, are valid for GUI automation testing as well. Since we incorporated subjective opinions to produce context specific results, we gained an understanding that every practitioner has their own way of working. Hence, this study aids in developing a common understanding to support informed subjective decisions based on evidence.
40
Söderlund, Jesper, and Thomas Sörensen. "Test Process Improvement & Test/Build Tool Evaluation." Thesis, Mälardalen University, School of Innovation, Design and Engineering, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-9523.
Full textAbstract:
The products The Company manufactures are used in an area of the industry where errors leading to a stop in production can be quite expensive. Therefore are testing of the products important and the tests can also give indications about the quality of the products.
The Company is in a phase where they are developing a new product line to support all existing and future products. In this phase, it was decided that all products will use a common framework for unit testing and a common build system for all products. One part of the thesis was to investigate and evaluate different frameworks for unit testing and tools for a build system. The unit test framework that were evaluated are Cppunit, cfix, NUnit, Boost test library, Unit Testing++ and CxxTest. The result of the evaluation was that CppUnit were recommended. For the build system MSBuild, NAnt, Automated Build Studio and Cruise Control .NET were evaluated. The recommended tools for a build system is MSBuild in combination with Cruise Control .Net if The Company is interested in the functionality Cruise Control .Net has to offer.
The Company also has an interest in evaluating the current test processes and identify improvements as a part of The Company’ s objective were all products should follow a common test process. In order to identify these improvements a literature study of four test process improvement frameworks (Test Process Improvement, Test Maturity Model Integrated, Minimal Test Practice Framework and Test Improvement Model) were carried out. Out of these four frameworks Test Process Improvement (TPI) were chosen to assist when identifying improvements. With the help of TPI a limited assessment took place to give indications about the test maturity for three of The Company’s products where two of the products had low maturity. Results of the improvement measures can be summed up with the need to harmonize the documents, standardize and document the various processes.
As a last part of the thesis the possibility to automate testing of two of the products graphical user interfaces with the program Test Complete were investigated. For one of the products the result was that it worked satisfactorily and for the other product it did not work at all. This resulted in recommendations for how The Company should proceed with automated testing of the graphical user interface.
De produkter som företaget tillverkar används i huvudsak inom ett område av branschen där fel som leder till stopp i produktionen kan vara ganska dyrt. Detta gör testning av produkterna viktiga och tester kan också ge indikationer om kvaliteten på produkterna.
Företaget är i en fas där man utvecklar en ny produktlinje som ska stödja alla befintliga och framtida produkter. I denna fas har man beslutat att alla produkterna ska använda ett gemensant ramverk för enhetstestning och även använda ett gemensamt byggsystem för samtliga produkter. En del av examensarbetet var att undersöka och utvärdera olika ramverk för enhets testning och verktyg för byggsystem. De ramverk som utvärderades var CppUnit, cfix, NUnit, Boost test library, unitTest++ och CxxTest. Utvärderingen ledde fram till att CppUnit rekommenderades till företaget. Verktyg som utvärderades för byggsystem var MSBuild, NAnt, Automated Build Studio och Cruise Control .Net. För byggsystem rekommenderas MSBuild i kombination med Cruise Control .Net ifall företaget är intresserade av den extra funktionalitet som Cruise Control .Net har att erbjuda.
Företaget har även ett intresse av att utvärdera den nuvarande testprocessen och identifiera förbättringar som ett led i att befintliga produkter skall följa en gemensam testprocess. För att kunna identifiera dessa förbättringar utfördes en litteraturstudie över fyra stycken test process förbättrings ramverk (Test Process Improvent, Test Maturity Model integrated, Minimal Test Practice Framework och Test Improvement Model). Utav dessa fyra ramverk så valdes Test Process Improvement (TPI) ut som en hjälp för att identifiera förbättringar. Med hjälp av TPI utfördes en begränsad bedömning av företagets mogenhetsgrad på tre produkter, där två av produkterna har en låg mogenhetsgrad. Resultat av förbättringsåtgärderna kan sammanfattas med att man bör harmonisera dokument, standardisera och dokumentera olika processer.
Som en sista del i examensarbetet så utvärderades möjligheten att automatisera testning på två av produkternas grafiska användargränssnitt med programmet TestComplete. För en av produkterna blev resultatet att det fungerade tillfredställande och för den andra produkten så fungerade det inte alls. Resultatet blev rekommendationer för hur företaget borde gå vidare med automatisering av testnig på det grafiska användargränssnittet.
41
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 textAbstract:
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.
42
Caruana, Henrik. "Tachograph Software Test Tool : Development and evaluation of test automation regardingthe user interface component of the SE5000 tachograph." Thesis, KTH, Skolan för informations- och kommunikationsteknik (ICT), 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-107775.
Full textAbstract:
Det här kandidatexamensarbetet beskriver utvecklingen av ett program som testar en mjukvarukomponent i SE5000 färdskrivaren och utreder om det är värt att vidareutveckla den här testmetodiken. En av produkterna Stoneridge Electronics utvecklar är färdskrivaren SE5000. En digital färdskrivare är ett elektroniskt system för att spela in kör‐ och vilotid för förare som kör kommersiella fordon. Fordonshastighet, körsträcka och andra systemrelaterade parametrar loggas också. Data sparas i ett minne inuti enheten och på förarspecifika smartkort. Mjukvaran i enheten, SE5000, består av flera separata komponenter och man vill testa varje komponent för sig på mjukvarunivå. Genom att testa på mjukvarunivå förkortas återkopplingstiden för utvecklarna och eventuella buggar upptäcks tidigare. Hög testtäckning är ett tydligt kvalitetstecken och är en trygghet för Stoneridge Electronics när enheten ska bli testad och funktionscertifierad av Transportstyrelsen. Användargränssnittskomponenten ansvarar för att producera rätt utdata som svarar på förarindata och fordonsrelaterade parametrar. Tidigare har testning av användargränssnittskomponenten genomförts på systemnivå, dvs. mjukvaran har integrerats med hårdvaran och hela systemet testas genom ett extern gränssnitt. Tidsåtgången för att genomföra tester på det här sättet är väldigt stor och det är ett problem då man vill ha hög testteckning. Stoneridge Electronics Justusprojekt vill kunna genomföra tillförlitliga, automatiserade tester på mjukvarunivå regelbundet eller vid mjukvaruförändringar. Det är också önskvart att etablera ett stort testfallsbibliotek som kan köras utan den stora tidsåtgången associerad med manuella tester. Dessa testfall bör vara enkla och snabba att implementera.This thesis work describes the development of a program that tests a software component in the SE5000 tachograph and investigates if this test methodology and setup is worth further investigation. One of the products Stoneridge Electronics develop is the tachograph SE5000. A digital tachograph is an electronic system for recording driving and rest times for drivers and co-drivers of commercial vehicles. Vehicle speed, distance travelled and other system‐related parameters are also logged. Data is stored in a memory inside the unit and on driver ‐specific smart cards. The software of the SE5000 tachograph consists of several separate components that SE wishes to test separately on software level. By testing on software level the feedback loop is shortened and allows developers to catch possible bugs much earlier in the process. High test coverage is a clear sign of quality and is a reassuring for Stoneridge Electronics when the unit is tested and a function certificate is issued by the Swedish Transport Agency. The user interface component is responsible for delivering data in response to driver and vehicle input and stimulation. Previously the user interface testing has been performed on system level, i.e. software has been integrated with the hardware and the system has been put under test by using external interfaces of the target. The test execution time consumption is a problem when performing user interface tests on system level. It is the projects wish to be able to perform reliable automated testes at a software level in order to run the test on a regularly basis or at software change. It is also desirable to establish a great variety of tests that can be executed without huge time consumption. These test cases should be easy and quick to implement.
43
Ruiz, Yuncosa Jose Luis. "Test Automation for HVDC System Protection A Proof of Concept for ABB." Thesis, Uppsala universitet, Institutionen för informationsteknologi, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-425400.
Full textAbstract:
When a software is designed, one of the most critical aspects of the process is the verification. In most cases, this operation can betime consuming, which is why it is always needed to speed up the process by the use of automated tools to perform the task. ABB Power Grids Division uses a large software for monitoring the HVDC system, which is one of the high voltage power transmission systems they offer. This control and protection software is called MACH3, and it is created in a graphical programming development environment called HiDraw, which is proprietary to the company. HiDraw allows to design the code by using graphical blocks, which receive data as inputs, processes it and produces results at their outputs. Some critical functions of the software are presented in the form of individual graphical blocks, and during the software development they may need to be verified. Since some of these blocks can have a quite large amount of inputs and outputs, the verification process is lengthy, and hence, the company is looking for ways to automate it. This project shows the design details of two tester modules created in the HiDraw graphical programming environment to perform the verification of two blocks used inside the MACH3 control and protection software. It is initially presented the characterization made for the logical behaviour of the two blocks to be verified, which was done by using Signal Temporal Logic (STL) language.Following, it is presented the two tester modules created in the HiDraw environment, which assess all the requirements previously defined in STL for the two blocks under test. This assessment is done by means of a predefined set of inputs that the testers feed to the blocks under test, and by verifying whether their outputs satisfy the requirements or not. The testers automatically run the set of test inputs in sequence, and produce outputs indicating if the tests have been passed or not. The implementation of this kind of testers can reduce the time invested by the ABB personnel on performing regression tests that are usually done manually. The proposed testersare incorporated as part of the MACH3 system, and run on its embedded computers. It is also presented the alternatives that were considered for automating the verification and the decision process that took place to choose the presented alternative.
44
Liljequist, Viktor. "Development of a Bioreactor Simulator for supporting automation software test and verification." Thesis, Uppsala universitet, Avdelningen för systemteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-325959.
Full textAbstract:
The GE Healthcare Life sciences organization develop and manufacture bioreactors, mixers, filtration skids and chromatography systems used together in a biomanufacturing platform. The platform is monitored and controlled by a distributed control system through a Programmable Logic Controller (PLC). The automation software controlling the platform is today tested and verified together with the physical units. The software use PROFIBUS, an industry standard for industrial automation, for communication and control of the units. Limited access to the physical units is usually a bottleneck and it's difficult to test abnormal situations to make sure the correct alarms are triggered. To reduce the hardware dependency and to provide support during test and verification, a virtual environment is developed to simulate the behavior of a bioreactor during execution. A .NET application has been developed together with a mathematical framework to simulate a cell culture and to return relevant process parameters such as pH, dissolved oxygen, temperature and weight. The results show that it's possible to simulate a bioreactor and to communicate with the control system. The software can be a valuable tool when developing and testing automation software but should not be used for process optimization or tuning of control parameters.
45
Charfi, Leila. "Formal modeling and test generation automation with Use Case Maps and LOTOS." Thesis, University of Ottawa (Canada), 2001. http://hdl.handle.net/10393/9138.
Full textAbstract:
This thesis addresses the problem of formal modelling and test generation, from system requirements represented in the form of Use Case Maps. In the first part of our thesis, we present an existent development methodology based on Use Case Maps for the design of the requirements and on LOTOS and SDL for the formal modeling of telecommunication systems. We follow this methodology for the formal specification and validation of a telephony system using LOTOS. In the second part of the thesis, we develop a method for the automatic generation of LOTOS scenarios from Use Case Maps called Ucm2LotosTests. The obtained scenarios can be used for the verification of the LOTOS specification built from the same Use Case Maps and for conformance testing purposes at the implementation stage. Finally, we propose a development methodology based on Use Case Maps for the design of the requirements and on LOTOS for the formal modeling of the system. In addition, this methodology offers a fast test generation process; it proposes the use of Ucm2LotosTests for the automatic generation of LOTOS scenarios from requirements in UCM and of TGV for the automatic generation of TTCN test suites from LOTOS. The methodology is illustrated with a case study which is a telephony system providing the basic call feature.
46
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 textAbstract:
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.
47
Hoaglund, Catharine M., Lee S. Gardner, and Victor W. Bender. "THE CHALLENGE OF AUTOMATING TEST DATA MANAGEMENT." International Foundation for Telemetering, 1993. http://hdl.handle.net/10150/608866.
Full textAbstract:
International Telemetering Conference Proceedings / October 25-28, 1993 / Riviera Hotel and Convention Center, Las Vegas, NevadaThe increasing complexity and volume of the information needed to support flight test missions has led to a need to expand the capability of current test data management systems. While the abilities currently exist to collect and manage calibration and telemetry information in an automated fashion, new requirements have emerged to link this data with other systems and to expand the functions and devices supported. Coordinating and directing the overall flow of information required for a successful flight test is a very big task. It calls for a view into flight test planning and scheduling activities, test objectives and methods, and the requirements for viewing and processing the test data in real-time and postflight. To meet this challenge, the Automated Test Data Management System (ATDMS) is being developed at the Air Force Flight Test Center (AFFTC), Edwards AFB, California. This paper describes the critical information and interfaces that the ATDMS will manage to bring cohesion to the management of flight test support data.
48
Feller, Nadjia Jandt. "Geração de testes de aceitação a partir de modelos U2TP para sistemas web." reponame:Biblioteca Digital de Teses e Dissertações da UFRGS, 2015. http://hdl.handle.net/10183/115214.
Full textAbstract:
A utilização desta abordagem no ciclo de desenvolvimento de uma aplicação web traz algumas vantagens, como ser necessário gerar manualmente apenas o modelo de comportamento de cada funcionalidade da aplicação, (pois os demais artefatos são gerados automaticamente), consumindo menos tempo e estando menos sujeitos a erros, além de prevenir diferentes interpretações dos requisitos pelos stakeholders, desenvolvedores e testadores. O tempo despendido na especificação dos modelos é compensado pelo tempo economizado com a geração dos cenários e do código de testes.The testing activity throughout software development is fundamental to the pursuit of software quality and reliability, finding faults to be removed. However, despite its importance, software testing is often an underutilized phase in software development. Moreover, tests are proved to be expensive, difficult and problematic when not done in the appropriate way. A new paradigm for software testing is model-driven testing (MDT), which can be defined as software testing where test cases are derived from a model that describes some aspects of the system being tested, such as behavior, for example. This description, often using UML diagrams and/or its profiles, can be processed to produce a set of test cases. Software specifications based on usage scenarios expressed by appropriate UML diagrams are considered significant and effective, because they describe the system’s requirements from an intuitive and visual perspective. Thus, they can be used for the description of acceptance tests, which validate that the system meets user requirements. These specifications also facilitate the automation of this kind of test. Test automation can decrease time spent on testing, thereby reducing the cost of this activity. Thus, this work proposes an approach for automated generation of acceptance tests from U2TP (the UML 2.0 test profile) diagrams for web applications, based on behavior driven development (BDD) paradigm, obtaining acceptance scenarios and executable test code supported by an acceptance testing automation framework. This approach was applied on an actual development environment, by means of an experiment. Using this approach in an web application development cycle has some advantages, such as being required only to manually generate the model of behavior of each application functionality (because other artifacts are generated automatically), thus being less time consuming and less prone to errors, and preventing different interpretations of requirements by stakeholders, developers and testers. The time spent at the models’ specification is compensated by the time saved with the generation of scenarios and test code.
49
Hamber, Henrik, and Apell Linus Skjutar. "The effects of test process automation on fault frequency for a spreader system." Thesis, KTH, Maskinkonstruktion (Inst.), 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-190139.
Full textAbstract:
Det här examensarbetet utfördes på R&D avdelningen på Bromma Conquip, den tekniskt ledande tillverkaren av kontainerlyftok. I linje med den allmänna utvecklingen har oken kommit avinkludera mer avancerad elektronik och mjukvara. Detta har gjort dem svårare att utveckla med nuvarande metoder och ökat vikten av mjukvarutestning. I dagsläget används modeller av systemet men dem representerar inte dess dynamik. Testprocessen för mjukvaran är fullständigt manuell vilket gör den tidkrävande och känslig för mänskliga fel. Uppgiften består i att undersöka hur komplex modellen behöver vara för att vara användbar och hur mjukvarutestningen bäst ska automatiseras. Dessutom skulle ytterligare eventuell nytta av modellen och automationen undersökas. En litteraturstudie genomfördes for att bilda den teoretiska grunden för arbetet. Denna komplimenterades med intervjuer med personal på företaget för att samla specifik information om deras produkter, utvecklingsprocess och företagskultur. Ett systemtekniskt tillvägagångssätt användes genomgående i arbetet. För att hitta den lämpliga nivån av komplexitet tillämpades en modellbaserad utvecklingsprocess på det teleskopiska lyftoket Bromma STS45. Processen bestod utav en systemanalys, kravhantering, modellering och simulering vilket följdes av verifiering och validering. För att undersöka hur mjukvarutestningen bäst ska automatiseras användes en trestegsprocess. Först analyserades den nuvarande testprocessen. Sedan definierades best practice inom industrin baserat på standarder för säkerhetskritiska system. Slutligen relaterades denna best practice till företagets behov för att bestämma vilka delar av denna som var relevanta. För att hitta eventuell ytterligare nytta av modellen och automationen analyserades resultaten och komplimenterades med en genomgång med företaget. Resultatet för denna examensarbete visade att det var tillräckligt för modellen att representera mekaniken hos den teleskopiska balken för att uppnå en passande nivå av komplexitet. En samling av föreslagna practices for testautomation baserat på de viktigaste best practices presenterades. Dessa föreslagna practices kan minska frekvensen av mjukvarufel för systemet. Flera andra avdelningar på företaget kunde dra nytta av modellen och automationen. Den främsta av dessa var möjligheten att övergå till en modellbaserad utvecklingsprocess för R&D avdelningen.This master thesis was performed at the R&D department of Bromma Conquip, the technical leader in the business of cargo container spreaders. In line with the general turn in the industry the design of the spreaders has come to include more advanced electronics and embedded software. This has made the system more dificult to develop and increased the importance of software testing. Currently, models of the system are used in the testing but they do not represent its dynamics. The test process for the embedded software is currently completely manual, making it time consuming and susceptible to human error. The task consisted of finding how complex a simulation model needed to be in order to be useful and to investigate how to best automate the test process. A third task consisted of finding additional benefits of the model and the automation. A literature survey was conduced to form the theoretical foundation of the thesis. This was complemented by interviews with personnel at the company to gather specic information about their products, development process and company culture. A Systems Engineering approach was used throughout the thesis work. To find the suitable level of dynamics a Model-Based Development process was applied to the Bromma STS45 telescoping spreader. The process consisted of a system analysis, requirements engineering, modelling and simulation followed by verification and validation. To find how to best automate the testing a three stage process was used. First, the current manual process was analysed. Second, best practice in the industry as defined by standards for safety-critical systems was defined. Third, best practice was related to the needs of the company to find which of them that was relevant. To find the additional benefits of the model and the automation the results was analysed and complemented with a review wit the company. The results of the this master thesis is that it is sucient for the model of represent the mechanics of the telescopic beam of the spreader to achieve a suitable level of dynamics. A set of purposed practices for test automation based on the most important best practices was presented. These purposed practices will reduce the frequency of software related faults in the system. Several additional benets for other departments was also presented. The main benet consists of the ability to transition to a Model-Based Development process for the R&D department.
50
ARRUDA, Filipe Marques Chaves de. "Test automation from natural language with reusable capture & replay and consistency analysis." Universidade Federal de Pernambuco, 2017. https://repositorio.ufpe.br/handle/123456789/25354.
Full textAbstract:
Submitted by Pedro Barros (pedro.silvabarros@ufpe.br) on 2018-08-01T20:03:01Z
No. of bitstreams: 2
license_rdf: 811 bytes, checksum: e39d27027a6cc9cb039ad269a5db8e34 (MD5)
DISSERTAÇÃO Filipe Marques Chaves Arruda.pdf: 2317425 bytes, checksum: 0739c60d4cc06fe57fcf2d3611f976cc (MD5)Approved for entry into archive by Alice Araujo (alice.caraujo@ufpe.br) on 2018-08-02T20:13:13Z (GMT) No. of bitstreams: 2 license_rdf: 811 bytes, checksum: e39d27027a6cc9cb039ad269a5db8e34 (MD5) DISSERTAÇÃO Filipe Marques Chaves Arruda.pdf: 2317425 bytes, checksum: 0739c60d4cc06fe57fcf2d3611f976cc (MD5)
Made available in DSpace on 2018-08-02T20:13:13Z (GMT). No. of bitstreams: 2 license_rdf: 811 bytes, checksum: e39d27027a6cc9cb039ad269a5db8e34 (MD5) DISSERTAÇÃO Filipe Marques Chaves Arruda.pdf: 2317425 bytes, checksum: 0739c60d4cc06fe57fcf2d3611f976cc (MD5) Previous issue date: 2017-03-31
CNPq
A common scenario when automating tests begins with a test engineer writing test cases with no formal specification or software supervision. Then, there is a developer that tries to understand what an ambiguous test means in order to transform it into code. Finally, there is an experienced tester that is responsible to supervise the execution and to verify whether the failures are indeed bugs, or a mistake from the developer or test engineer, or just a matter of change in the requirements or user interface. To reduce these recurring problems in test automation, we propose a unified process, to write test cases using a controlled natural language to check consistency and dependencies automatically or search for similar test descriptions written in free natural language. The proposed process is applied to a reusable capture & replay strategy, so anyone can automate tests even without previous knowledge about coding, besides mitigating scalability/maintainability issues by reusing actions with granularity ranging from simple commands, such as open an application, to entire test cases or even test suites. The actions are represented by an abstract, framework-free notation. Besides, the implementation covers plugins, including voice recording and image processing; and a proactive traceability for elements in the user interface. The strategy was consolidated through its implementation in a tool, in the context of a partnership with Motorola Mobility. It has been adopted in practice for different test suites, achieving a reuse ratio up to 71% for test cases written with no standard whatsoever, yet presenting time gains similar to traditional C&R approaches when compared to coding. Furthermore, through standardization, it was possible to define a consistency notion and to capture an association graph (whose edges represent dependency and cancellation relations) among test actions. From these associations, it was possible to establish a mechanism to ensure that each test action is preceded by actions on which it depends to be granted to execute. An editor (Kaki) was implemented to mechanize both adherence to the CNL and the dependencies between tests. From the associations informed within the user interface, Kaki generates an Alloy model automatically and uses Alloy Analyzer to verify consistency, besides possibly suggesting the insertion of test actions to satisfy the dependencies, automatically.
Um cenário comum na automação de testes inicia-se a partir da escrita dos casos de testes por um engenheiro de testes, sem alguma especificação formal ou supervisão por software. Então, um desenvolvedor tenta interpretar o que o teste potencialmente ambíguo significa antes de transformá-lo em código executável. Finalmente, um testador é responsável por verificar se as falhas são realmente bugs, ou erros cometidos pelo desenvolvedor, pelo engenheiro de teste ou apenas uma mudança nos requisitos ou na interface de usuário. Para reduzir estes problemas recorrentes na automação de testes, nós propomos um processo unificado de escrita de casos de testes usando linguagem natural controlada que permite a verificação automática de consistência e dependências na escrita de ações de teste, ou usando uma busca por descrições similares de ações quando escritas em linguagem natural livre. O processo proposto é aplicado em uma estratégia de capture & replay reusável, assim permitindo a automação por pessoas sem background em programação, além de mitigar problemas intrínsecos de escalabilidade e manutenabilidade através do reuso de ações de teste com granularidade que pode variar desde comandos simples, como abrir um aplicativo, um caso de teste inteiro, ou mesmo uma suite de testes. As ações são representadas através de uma notação abstrata e framework-agnóstica. Além disso, a implementação ainda abrange plugins que incluem captura de voz e processamento de imagem; e rastreabilidade proativa para os artefatos. A estratégia foi concretizada através de sua implementação em uma ferramenta (Zygon) e avaliada no contexto de uma parceria com a Motorola Mobility, tendo sido adotada na prática em diferentes suítes de testes usando a linguagem natural livre, atingindo um reuso de até 71% com ganho de tempo similar a abordagens de capture & replay quando comparadas à programação. Além disso, através da padronização da linguagem natural controlada, foi possível definir uma noção de consistência e capturar um grafo de associações (dependências e cancelamentos) entre ações de teste. A partir destas associações, foi possível estabelecer mecanismos para garantir que cada ação de um teste devesse ser precedida por ações das quais a mesma depende para ser executada. Um editor (Kaki) foi implementado para mecanizar tanto aderência à CNL, como a dependência entre ações de teste. A partir das associações informadas na interface gráfica, Kaki cria automaticamente um modelo Alloy e usa o Alloy Analyzer para fazer a verificação de consistência, além de possivelmente sugerir a inserção de ações de teste para satisfazer as relações de dependências, automaticamente.