As Web services grow in maturity and use, so do the methods which are being used to test and maintain them. Regression Testing is a major component of most major testing systems but has only begun to be applied to Web services. The majority of the tools and techniques applying regression test to Web services are focused on test-case generation, thus ignoring the potential savings of regression test selection. Regression test selection optimizes the regression testing process by selecting a subset of all tests, while still maintaining some level of confidence about the system performing no worse than the unmodified system. A safe regression test selection technique implies that after selection, the level of confidence is as high as it would be if no tests were removed. Since safe regression test selection techniques generally involve code-based (white-box) testing, they cannot be directly applied to Web services due to their loosely-coupled, standards-based, and distributed nature. A framework which automates both the regression test selection and regression testing processes for Web services in a decentralized, end-to-end manner is proposed. As part of this approach, special consideration is given to the concurrency issues which may occur in an autonomous and decentralized system. The resulting synchronization method will be presented along with a set of algorithms which manage the regression testing and regression test selection processes throughout the system. A set of empirical results demonstrate the feasibility and benefit of the approach.

Inom programvaruutveckling är testning en viktig aktivitet där regressionstest är centralt. Regressionstestning innebär att exekvera om testfall för att säkerställa att de förändringarna som har gjorts i programmet inte har infört nya fel i systemet. Detta görs också med syfte till att kontrollera att systemets befintliga funktioner inte har påverkats negativt av dessa förändringar. Att genomföra regressionstester manuellt är resurskrävande i form av tid och pengar. Därför rekommenderas det att utföra denna aktivitet på ett automatiserat sätt. Ett problem som finns idag med exekvering av automatiserad regressionstest är att testare blir specialiserade på specifika testmiljöer på grund av det används många olika testmiljöer. Därför skulle de inte kunna stödja förbättringen av andra testares arbetsflöde. Således fokuserar denna studie på att beskriva de aktuella arbetssätt inom området exekvering av automatiserade regressionstester samt hur dessa kan utvecklas. Det har varit nödvändigt att genomföra personliga intervjuer samt litteraturstudie för att kunna besvara studiens forskningsfrågor. I detta arbete har det kommits fram till skapandet av en allmän ram för testare att arbeta mer effektivt med genomförandet av automatiserade regressionstestning oavsett testmiljön. Ramverket innehåller 7 faser: (1) Val av testfall, (2) Utföring/Exekvering av tester, (3) Kontroll/Analysera av resultat, (4) Skrivandet av rapport för testresultat, (5) Arkivering av testresultat rapporter, (6) Värdering och tilldelning av uppkommande problem samt (7) Hantering av testcykeln. / Software testing is an important activity within the software development area, where regression testing is essential. Regression testing implies re-running test cases in order to ensure that changes made to the software do not introduce new errors and to guarantee that the system’s functionalities have not been affected by those changes. To execute regression testing in manual mode involves valuable resources, specifically time and money. Therefore it is recommended to carry out this activity in an automated manner. A problem that faces the execution of automated regression testing is that testers are becoming specialized in specific test environments due to the existing diversity of tools used. Therefore testers would not be able improve test processes related to different environments. Thus, this paper focuses on identifying the current working manner within the domain of execution of automated regression testing and to improve it. Then, it has been necessary to conduct personal interviews (7) and a literature study in order to answer the study’s questions. This work provides a general framework for testers to work more effectively with execution of automated regression testing regardless of the test environment. The framework includes 7 stages: (1) Select test cases, (2) Execute/Run tests, (3) Monitoring/Analyzing results, (4) Write a report of the test results, (5) Archive the reports of the test results, (6) Estimate and assign the raised problems, and (7) Manage the test cycle.

<p>Regression testing plays an important role during the software development life-cycle,especially during maintenance, it provides confidence that the modified parts of softwarebehave as intended and the unchanged parts have no affect by the modification. Regressiontest selection is used to select test cases from the test suites which have been used to test theprevious version of the software. In this thesis, we extend the traditional definition of a testcase with a log file, containing information of which events that occurred when the test casewas last executed. Based on the contents of this log file, we propose a method of regressiontest selection for multi-tasking real-time systems, able to determine which parts of softwarethat have not been affected by the modification. Therefore, the test cases designed for theunchanged parts do not need to be re-tested.</p>

Regression testing is important but time consuming. Automating the testing have many benefits. It will save money for companies because they will not have to pay testers to manually test their applications. It will produce better software with less bugs as testing can be done more frequently so bugs will be found faster. This thesis has compared two techniques used to automate regression testing. The more traditional component level record and replay tools and Visual GUI testing tools that uses image recognition. Eight tools in total was tested and compared, four from each technique. The system under test for this project was a fat client application used by Trafikverket. After automating a test suite using all tools, it could be concluded that the component level record and replay had some advantages over visual GUI testing tools, especially when it comes to verifying the state of the system under test. The benefits of visual GUI testing tools comes from their independence from the system under test and that the technique more correctly mimics how a real user interacts with the GUI. / Regressionstestning är en viktig men tidskrävande del av mjukvaruutveckling. Att automatisera testningen har flera fördelar. Det sparar pengar för företag eftersom de inte behöver betala testare för att manuellt utföra testerna. Det resulterar i bättre mjukvara med färre buggar eftersom man kan testa oftare och därmed hitta buggar tidigare. Det här projektet har undersökt och jämfört två tekniker som kan användas för att automatisera regressionstestning och verktyg som använder dessa tekniker. Dels de traditionella verktygen som identifierar objekt på komponentnivå samt verktyg som istället använder sig av bildigenkänning för att identifiera objekt. Totalt testades och utvärderades åtta verktyg, fyra av varje tekniktyp. Systemet som testades under projektet är en skrivbordsapplikation som används av Trafikverket. Efter att ha automatiserat en testsekvens med varje verktyg kunde konstateras att verktygen som identifierar objekt på komponentnivå har flera fördelar över verktyg som enbart använder bildigenkänning. Detta gäller främst när det kommer till verifiering av systemets tillstånd. Den största fördelen med bildigenkänningsverktygen visade sig vara dess oberoende från systemet, samt att tekniken mer efterliknar en verklig användare.

Regression testing is important but time consuming. Automating the testing have many benefits. It will save money for companies because they will not have to pay testers to manually test their applications. It will produce better software with less bugs as testing can be done more frequently so bugs will be found faster. This thesis has compared two techniques used to automate regression testing. The more traditional component level record and replay tools and Visual GUI testing tools that uses image recognition. Eight tools in total was tested and compared, four from each technique. The system under test for this project was a fat client application used by Trafikverket. After automating a test suite using all tools, it could be concluded that the component level record and replay had some advantages over visual GUI testing tools, especially when it comes to verifying the state of the system under test. The benefits of visual GUI testing tools comes from their independence from the system under test and that the technique more correctly mimics how a real user interacts with the GUI. / Regressionstestning är en viktig men tidskrävande del av mjukvaruutveckling. Att automatisera testningen har flera fördelar. Det sparar pengar för företag eftersom de inte behöver betala testare för att manuellt utföra testerna. Det resulterar i bättre mjukvara med färre buggar eftersom man kan testa oftare och därmed hitta buggar tidigare. Det här projektet har undersökt och jämfört två tekniker som kan användas för att automatisera regressionstestning och verktyg som använder dessa tekniker. Dels de traditionella verktygen som identifierar objekt på komponentnivå samt verktyg som istället använder sig av bildigenkänningför att identifiera objekt. Totalt testades och uvärderades åtta verktyg, fyra av varje tekniktyp. Systemet som testades under projektet är en skrivbordsapplikation som används av Trafikverket. After att ha automatiserat en testsekvens med varje verktyg kunde konstateras att verktygen som identifierar objekt på komponentnivå har flera fördelar över verktyg som enbart använder bildigenkänning. Detta gäller främst när det kommer till verifiering av systemets tillstånd. Den största fördelen med bildigenkänningsverktygen visade sig vara dess oberoende från systemet, samt att tekniken mer efterliknar en verklig användare.

No description available.

Understanding the impact of changes made daily by development teams working on large-scale software products is a challenge faced by many organizations nowadays. Development efficiency can be severely affected by the increase in fragility that can creep in as products evolve and become more complex. Processes, such as gated check-in mechanisms, can be put in place to detect problematic changes before submission, but are usually limited in effectiveness due to their reliance on statically-defined sets of tests. Traditional change-impact analysis techniques can be combined with information gathered at run-time in order to create a system that can select tests for change verification. This report provides the high-level architecture of a system, named Ratchet, that combines static analysis of C++ programs, enabled by the reuse of the Clang compiler frontend, and code-coverage information gathered from automated test runs, in order to automatically select and schedule tests that exercise functions and methods possibly affected by the change. Prototype implementations of the static-analysis components of the system are provided, along with a basic evaluation of their capabilities through synthetic examples. / text

Submitted by Lucienne Costa (lucienneferreira@ufcg.edu.br) on 2018-08-30T18:41:36Z No. of bitstreams: 1 INDY PAULA SOARES CORDEIRO E SILVA – DISSERTAÇÃO (PPGCC) 2018.pdf: 1399246 bytes, checksum: ca2d8bfa9c9492d9d2d97a1485afad82 (MD5) / Made available in DSpace on 2018-08-30T18:41:36Z (GMT). No. of bitstreams: 1 INDY PAULA SOARES CORDEIRO E SILVA – DISSERTAÇÃO (PPGCC) 2018.pdf: 1399246 bytes, checksum: ca2d8bfa9c9492d9d2d97a1485afad82 (MD5) Previous issue date: 2018-02-22 / Capes / Refatoramentos normalmente exigem testes de regress˜ao para verificar se as mudanc¸as aplicadas ao c´odigo, preservaram o comportamento original do mesmo. Geralmente, ´e dif´ıcil definir um conjunto de testes que seja efetivo para esta tarefa, uma vez que o refatoramento n˜ao ´e frequentemente aplicado em etapas isoladas. Al´em disso, as edic¸ ˜oes de refatoramento podem ser combinadas com outras edic¸ ˜oes no c´odigo. Nesse sentido, a gerac¸ ˜ao de casos de teste pode contribuir para essa tarefa, analisando sistematicamente o c´odigo e fornecendo uma ampla gama de casos de teste que abordam diferentes construc¸ ˜oes. No entanto, uma s´erie de estudos apresentados na literatura mostram que as ferramentas atuais ainda n˜ao s˜ao eficazes com relac¸ ˜ao `a detecc¸ ˜ao de faltas, particularmente faltas de refatoramento. Com base nisto, apresentamos dois estudos emp´ıricos que aplicaram as ferramentas Randoop e Evosuite para gerar suites de testes de regress˜ao, com foco na edic¸ ˜ao de refatoramento do tipo extract method. Com base nos resultados dos estudos, identificamos fatores que podem influenciar o desempenho das ferramentas para efetivamente testar a edic¸ ˜ao. Para validar nossos achados, apresentamos um conjunto de modelos de regress˜ao que associam a presenc¸a desses fatores `a capacidade do conjunto de testes, de detectar faltas relacionadas `a edic¸ ˜ao de refatoramento. E por fim, apresentamos a REFANALYZER, que ´e uma ferramenta que objetiva ajudar os desenvolvedores a decidir quando confiar em suites geradas automaticamente, para validar refatoramento do tipo extract method. / Refactoring typically require regression testers to verify that the changes applied to the code have preserved the original behavior of the code. Generally, it is difficult to define a set of tests that is effective for this task, since refactoring is not the weight applied in isolated steps. Also, since refactoring issues can be combined with other issues, without code. In this sense, a generation of test cases can contribute to this task by systematically analyzing the code and defining a wide range of test cases that address different constructs. However, a number of studies are not available but are not very effective in detecting faults, particularly refactorings. Based on this, we present two empirical studies that have applied as Randoop and Evosuite tools to generate regression test suites, focusing on the edition of refactoring of the extract method type. Based on the results of the studies, we identified factors that can influence the performance of the tools to effectively test the edition. To validate our findings, we present a set of control models that associate a solution with the ability of the set of tests, of spoken faults related to the refactoring edition. And finally, we present a REFANALYZER, which is a tool that is a solution to what needs to be solved when it is automatically managed, to validate refactoring of the extract method type.

Regression testing plays an important role during the software development life-cycle,especially during maintenance, it provides confidence that the modified parts of softwarebehave as intended and the unchanged parts have no affect by the modification. Regressiontest selection is used to select test cases from the test suites which have been used to test theprevious version of the software. In this thesis, we extend the traditional definition of a testcase with a log file, containing information of which events that occurred when the test casewas last executed. Based on the contents of this log file, we propose a method of regressiontest selection for multi-tasking real-time systems, able to determine which parts of softwarethat have not been affected by the modification. Therefore, the test cases designed for theunchanged parts do not need to be re-tested.

The aim of this study was to evaluate a battery of tests to be used as part of the process of selecting bursary students for engineering at tertiary institutions. Due to the problems in the schooling system it is not conclusive that all students who have obtained their senior certificates are prepared and able to meet the demands and challenges of tertiary education. The purpose of this study was to determine the criterion related validity of a mathematic proficiency test, Learning Potential Computerised Adaptive Test (LPCAT) and English Literacy Skills Assessment (ELSA) as predictors of academic performance. A quantitative approach was used for the purpose of this study. More specifically the Ex post facto analyses/design is used in this study. The relationships between the dependent and independent variables were determined. Correlation analyses, Kruskal-Wallis test and regression analysis were used for the purpose of this study. The results indicated that the Mathematical proficiency test was the best predictor of academic success, followed by LPCAT and ELSA. The results of this study indicates that the use of academic literacy and learning potential contribute in selecting the best students. Companies and Universities have long been looking for a predictor or predictors of success for students as they enter tertiary studies. This information has the potential to save companies and universities millions of Rands annually by helping them make better investment decisions. / Dissertation (MCom)--University of Pretoria, 2010. / Human Resource Management / Unrestricted