To see the other types of publications on this topic, follow the link: Software testing.
Dissertations / Theses on the topic 'Software testing'
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 'Software testing.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
Дядечко, Алла Миколаївна, Алла Николаевна Дядечко, Alla Mykolaivna Diadechko, and V. V. Kontchevich. "Software testing and software bugs." Thesis, Видавництво СумДУ, 2011. http://essuir.sumdu.edu.ua/handle/123456789/13487.
Full text
2
Henderson, Lehman Edwin Jr. "Testing eigenvalue software." Diss., The University of Arizona, 1991. http://hdl.handle.net/10150/185744.
Full textAbstract:
This dissertation describes a significant advance in automated testing of eigenvalue software. Several programs are described that assist the researcher in verifying that a new program is stable. Using backwards error techniques popularized by Wilkinson, a maximizer or "hill climber" systematically searches for instabilities in the program being tested. This work builds on software first reported by Miller and removes the restriction of not being able to work on iterative methods. Testing eigenvalue solver programs with sets of small random input data can often find instabilities, but the described hill climbing technique is more efficient. Using only ten sets of starting points, the maximizer will often find the instability, if it exists, in only a few tries.
3
Медведєва, С. О., and О. А. Абдуллаєв. "Testing. Basic concepts of testing software." Thesis, ВНТУ, 2019. http://ir.lib.vntu.edu.ua//handle/123456789/24789.
Full textAbstract:
У даній доповіді розглянуто основні концепції та види тестування програмного забезпечення, а також окреслено важливість приділення йому великої уваги у інших сферах.This paper examines the basic concepts and methods of software testing, and highlights the importance of paying attention to testing in other areas
4
Noller, Yannic. "Hybrid Differential Software Testing." Doctoral thesis, Humboldt-Universität zu Berlin, 2020. http://dx.doi.org/10.18452/21968.
Full textAbstract:
Differentielles Testen ist ein wichtiger Bestandteil der Qualitätssicherung von Software, mit dem Ziel Testeingaben zu generieren, die Unterschiede im Verhalten der Software deutlich machen. Solche Unterschiede können zwischen zwei Ausführungspfaden (1) in unterschiedlichen Programmversionen, aber auch (2) im selben Programm auftreten. In dem ersten Fall werden unterschiedliche Programmversionen mit der gleichen Eingabe untersucht, während bei dem zweiten Fall das gleiche Programm mit unterschiedlichen Eingaben analysiert wird. Die Regressionsanalyse, die Side-Channel Analyse, das Maximieren der Ausführungskosten eines Programms und die Robustheitsanalyse von Neuralen Netzwerken sind typische Beispiele für differentielle Softwareanalysen.
Eine besondere Herausforderung liegt in der effizienten Analyse von mehreren Programmpfaden (auch über mehrere Programmvarianten hinweg). Die existierenden Ansätze sind dabei meist nicht (spezifisch) dafür konstruiert, unterschiedliches Verhalten präzise hervorzurufen oder sind auf einen Teil des Suchraums limitiert.
Diese Arbeit führt das Konzept des hybriden differentiellen Software Testens (HyDiff) ein: eine hybride Analysetechnik für die Generierung von Eingaben zur Erkennung von semantischen Unterschieden in Software. HyDiff besteht aus zwei parallel laufenden Komponenten: (1) einem such-basierten Ansatz, der effizient Eingaben generiert und (2) einer systematischen Analyse, die auch komplexes Programmverhalten erreichen kann. Die such-basierte Komponente verwendet Fuzzing geleitet durch differentielle Heuristiken. Die systematische Analyse basiert auf Dynamic Symbolic Execution, das konkrete Eingaben bei der Analyse integrieren kann.
HyDiff wird anhand mehrerer Experimente evaluiert, die in spezifischen Anwendungen im Bereich des differentiellen Testens ausgeführt werden. Die Resultate zeigen eine effektive Generierung von Testeingaben durch HyDiff, wobei es sich signifikant besser als die einzelnen Komponenten verhält.Differential software testing is important for software quality assurance as it aims to automatically generate test inputs that reveal behavioral differences in software. The concrete analysis procedure depends on the targeted result: differential testing can reveal divergences between two execution paths (1) of different program versions or (2) within the same program. The first analysis type would execute different program versions with the same input, while the second type would execute the same program with different inputs. Therefore, detecting regression bugs in software evolution, analyzing side-channels in programs, maximizing the execution cost of a program over multiple executions, and evaluating the robustness of neural networks are instances of differential software analysis with the goal to generate diverging executions of program paths. The key challenge of differential software testing is to simultaneously reason about multiple program paths, often across program variants, in an efficient way. Existing work in differential testing is often not (specifically) directed to reveal a different behavior or is limited to a subset of the search space. This PhD thesis proposes the concept of Hybrid Differential Software Testing (HyDiff) as a hybrid analysis technique to generate difference revealing inputs. HyDiff consists of two components that operate in a parallel setup: (1) a search-based technique that inexpensively generates inputs and (2) a systematic exploration technique to also exercise deeper program behaviors. HyDiff’s search-based component uses differential fuzzing directed by differential heuristics. HyDiff’s systematic exploration component is based on differential dynamic symbolic execution that allows to incorporate concrete inputs in its analysis. HyDiff is evaluated experimentally with applications specific for differential testing. The results show that HyDiff is effective in all considered categories and outperforms its components in isolation.
5
Miller, Timothy. "Using specification animation to support specification testing and software testing /." [St. Lucia, Qld.], 2005. http://www.library.uq.edu.au/pdfserve.php?image=thesisabs/absthe.pdf.
Full text
6
Radnoci, Ramon. "Methods for Testing Concurrent Software." Thesis, University of Skövde, School of Humanities and Informatics, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:his:diva-3173.
Full textAbstract:
Most software today is concurrent and are used in everything from cell-
phones, washing machines, cars to aircraft control systems. The reliability
of the concurrent software may be more or less critical, depending on which
a.o. domain it is functioning in. Irrespective of domain, the concurrent
software must be sufficiently reliable.
It is therefore interesting to study how adaptable test methods for sequential
software are to test concurrent software. Novel test methods for concurrent
software can be developed by adapting test methods for sequential software.
In this dissertation, adaptability factors have been identified by conducting
a literature survey over state-of-the-art test methods. Directions taken in
the research of concurrent software testing is described by the survey. The
survey also demonstrates differences and similarities between test methods.
Three research contributions has been achieved by this dissertation. First,
this dissertation presents a survey over state-of-the-art-test methods. The
second contribution is the identified adaptability factors that should be
added to a test method for sequential software, that will be adapted to test
concurrent software. Finally, the third contribution to the field of concurrent
software testing is the identified future work in areas where test methods for
concurrent software has not been researched much or at all.
7
Garrepalli, Thrinay. "Knowledge Management in Software Testing." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-10974.
Full textAbstract:
Context: Software testing is a knowledge intensive process and the use of Knowledge Management (KM) methods and principles makes software testing even more beneficial. Thus there is a need of adapting KM into software testing core process and attain the benefits that it provides in terms of cost, quality etc. There has been an extensive literature published in the context of KM in software testing. But it is still unclear about the importance of KM with respect to testing techniques as well as testing aspects i.e. each activity that takes part during testing and the outcomes that they result such as test artifacts is considered as testing aspect. Thus there is a requisite for studies to focus on identifying the challenges faced due to lack of KM along with the importance of KM with respect to testing aspects, testing techniques and thus can provide recommendations to apply Knowledge Management to those that get benefited from it. Objectives: In this thesis, we investigate the usage and implementation of KM in Software testing. The major objectives of current thesis include, To identify various software testing aspects that receive more attention while applying KM. To analyze the software testing techniques i.e. test design, test execution and test result analysis and evaluate them and highlight which of these have more involvement of KM. To identify the software testing techniques where tacit or explicit knowledge is currently used. To gather challenges faced by industry due to lack of KM initiatives in software testing. Methods: We conducted a Systematic Literature Review (SLR) through a snowballing method based on the guidelines from Wohlin in order to identify various software testing aspects and testing techniques that have more involvement of KM and challenges that are faced due to lack of KM. A questionnaire intended for web-based survey was prepared from the gathered literature results to complement and further supplement them and to categorize the testing techniques based on the type of knowledge they utilize. The studies were analyzed in relation to their rigor and relevance to assess the quality of the results. The data obtained from survey were statistically analyzed using descriptive statistics and Chi-square test of significance. Results: We identified 35 peer reviewed papers among which 31 were primary and 4 were secondary studies. The literature review results indicated 9 testing aspects being in focus when applying KM within various adaptation contexts. In addition, few testing techniques were found to get benefited from the application of KM. Several challenges were identified from the literature review such as improper selection and application of better suited techniques, low reuse rate of Software Testing knowledge, barriers in Software testing knowledge transfer, impossible to quickly achieve the most optimum distribution of human resources during testing etc. 54 full answers were received to the survey. The survey showed that Knowledge Management was being applied in software testing in most of the industries. It was observed that test result analysis, test case design, test planning and testing techniques stood out as the most important testing aspects being focused while KM is applied. Regarding software testing techniques, 17 test design techniques, 5 test execution techniques and 5 test result analysis techniques gain more attention in the context of KM. Moreover, the results suggest that tacit knowledge was utilized for most of these techniques. Several new challenges are obtained from the survey such as lacking quality in terms of testing results or outcomes, difficulties in finding relevant information and resources during testing, applying more effort than required during testing, having a huge loss of know-how by neglecting explicit and tacit knowledge during test design etc. Conclusions. To conclude, various challenges are being faced due to the lack of KM. Our study also brings supporting evidence that applying KM in Software Testing is necessary i.e. to increase test effectiveness, selection and application of better suited techniques and so on. It was also observed that perceptions vary between the literature and the survey results obtained from the practitioners regarding testing aspects and testing techniques, as few aspects and techniques which are being categorized as the most important in the literature are not given the same priority by the respondents. Thus the final list of testing aspects and testing techniques is provided and empirical findings can likewise help practitioners to specifically apply KM more for those that are very much in need of it. Besides, it was found that most of the techniques require and utilize tacit knowledge to apply them and techniques such as shadowing, observing, training and recording sessions can help to store tacit knowledge for those that are in need of it. Thus researchers can recognize the advantages from this thesis and can further extend to various software life cycle models.
8
Odia, Osaretin Edwin. "Testing in Software Product Lines." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3853.
Full textAbstract:
This thesis presents research aimed at investigating different activities involved in software product lines testing process and possible improvements towards achieving developing high quality software product lines at reduced cost and time. The research was performed using systematic review procedures of Kitchenham. The reviews carried out in this research covers several areas relating to software product lines testing. The reasons for performing a systematic review in this research are to; summarize the existing evidence covering testing in software product line context, to identify gaps in current research and to suggest areas for further research. The contribution of this thesis is research aimed at revealing the different activities, issues and challenges in software product lines testing. The research into the different activities in software product lines lead to the proposed SPLIT Model for software product lines testing. The model helps to clarify the steps and activities involved in the software product line testing process. It provides and easy to follow map for testers and managers in software product line development organizations. The results were mainly on how testing in software product lines can be improved upon, towards achieving software product line goals. The basic contribution is the proposed model for product line testing, investigation into, and possible improvement in, issues related to software product line testing activities.The main purpose of the research as presented in this thesis is to present a clear picture of testing in the context of software product lines, which is quite different from testing in single product. The focus of this thesis is specifically the different steps and activities involved in software product lines testing and possible improvements in software product lines testing activities and issues towards achieving the goals of developing high quality software product lines at reduced cost and time. But, for software product lines to achieve its goals, there should be a comprehensive set of testing activities in software product lines development. The development activities from performing analyses and creating designs to integrating programs in software product line context, component testing and tools support for software product lines testing should be taken into consideration.
0046762913149 eddy_odia2002@yahoo.co.uk
9
Moschoglou, Georgios Moschos. "Software testing tools and productivity." Virtual Press, 1996. http://liblink.bsu.edu/uhtbin/catkey/1014862.
Full textAbstract:
Testing statistics state that testing consumes more than half of a programmer's professional life, although few programmers like testing, fewer like test design and only 5% of their education will be devoted to testing. The main goal of this research is to test the efficiency of two software testing tools. Two experiments were conducted in the Computer Science Department at Ball State University. The first experiment compares two conditions - testing software using no tool and testing software using a command-line based testing tool - to the length of time and number of test cases needed to achieve an 80% statement coverage for 22 graduate students in the Computer Science Department. The second experiment compares three conditions - testing software using no tool, testing software using a command-line based testing tool, and testing software using a GUI interactive tool with added functionality - to the length of time and number of test cases needed to achieve 95% statement coverage for 39 graduate and undergraduate students in the same department.Department of Computer Science
10
Nguyen, Duy Cu. "Testing Techniques for Software Agents." Doctoral thesis, Università degli studi di Trento, 2009. https://hdl.handle.net/11572/368032.
Full textAbstract:
Software agents and multiagent systems are a promising technology for today's complex, distributed systems. Methodologies and techniques that address testing and reliability of these systems are increasingly demanded, in particular to support systematic verification/validation and automated test generation and execution.
This work deals with two major research problems: the lack of a structured testing process in engineering software agents and the need of adequate testing techniques to tackle the nature of software agents, e.g., being autonomous, decentralized, collaborative.
To address the first problem, we proposed a goal-oriented testing methodology, aiming at defining a systematic and comprehensive testing process for engineering software agents. It encompasses the development process from the early requirements analysis until the deployment. We investigated how to derive test artefacts, i.e. inputs, scenarios, and so on, from agent requirements specification and design, and use these artefacts to refine the analysis and design in order to detect problems early. More importantly, they are executed afterwards to find defects in the implementation and build confidence in the operation of the agents under development.
Concerning the second problem, the peculiar properties of software agents make testing them troublesome. We developed a number of techniques to generate test cases, automatically or semi-automatically. These include goal-oriented, ontology-based, random, and evolutionary generation techniques. Our experiments have shown that each technique has different strength. For instance, while the random technique is effective in revealing crashes or exceptions, the ontology-based one is strong in detecting communication faults. The combination of these techniques can help to detect different types of fault, making software agents more reliable.
All together, the generation, evaluation, and monitoring techniques form a bigger picture: our novel continuous testing method. In this method, test execution can proceed unattendedly and independently of any other human-intensive activity; test cases are generated or evolved continuously using the proposed generation techniques; test results are observed and evaluated by our monitoring and evaluation approaches to give feedbacks to the generation step. The aim of continuous testing is to exercise and stress the agents under test as much as possible, the final goal being the possibility to reveal yet unknown faults.
We applied a case study to illustrate the proposed methodology and performed three experiments to evaluate the performance of the proposed techniques. The obtained results are promising.
11
Nguyen, Duy Cu. "Testing Techniques for Software Agents." Doctoral thesis, University of Trento, 2009. http://eprints-phd.biblio.unitn.it/68/1/PhD-Thesis-CUDUYNGUYEN.pdf.
Full textAbstract:
Software agents and multiagent systems are a promising technology for today's complex, distributed systems. Methodologies and techniques that address testing and reliability of these systems are increasingly demanded, in particular to support systematic verification/validation and automated test generation and execution.
This work deals with two major research problems: the lack of a structured testing process in engineering software agents and the need of adequate testing techniques to tackle the nature of software agents, e.g., being autonomous, decentralized, collaborative.
To address the first problem, we proposed a goal-oriented testing methodology, aiming at defining a systematic and comprehensive testing process for engineering software agents. It encompasses the development process from the early requirements analysis until the deployment. We investigated how to derive test artefacts, i.e. inputs, scenarios, and so on, from agent requirements specification and design, and use these artefacts to refine the analysis and design in order to detect problems early. More importantly, they are executed afterwards to find defects in the implementation and build confidence in the operation of the agents under development.
Concerning the second problem, the peculiar properties of software agents make testing them troublesome. We developed a number of techniques to generate test cases, automatically or semi-automatically. These include goal-oriented, ontology-based, random, and evolutionary generation techniques. Our experiments have shown that each technique has different strength. For instance, while the random technique is effective in revealing crashes or exceptions, the ontology-based one is strong in detecting communication faults. The combination of these techniques can help to detect different types of fault, making software agents more reliable.
All together, the generation, evaluation, and monitoring techniques form a bigger picture: our novel continuous testing method. In this method, test execution can proceed unattendedly and independently of any other human-intensive activity; test cases are generated or evolved continuously using the proposed generation techniques; test results are observed and evaluated by our monitoring and evaluation approaches to give feedbacks to the generation step. The aim of continuous testing is to exercise and stress the agents under test as much as possible, the final goal being the possibility to reveal yet unknown faults.
We applied a case study to illustrate the proposed methodology and performed three experiments to evaluate the performance of the proposed techniques. The obtained results are promising.
12
GAZZOLA, LUCA. "Field Testing of Software Applications." Doctoral thesis, Università degli Studi di Milano-Bicocca, 2019. http://hdl.handle.net/10281/241221.
Full textAbstract:
Quando interagiscono con sistemi software, gli utenti potrebbero dover affrontare problemi come crash, fallimenti e instabilità del programma. Il software difettoso in esecuzione sul campo non è solo la conseguenza di tecniche di verifica inefficaci, ma è anche dovuto alla complessità e alla diversità delle interazioni tra un'applicazione e il suo ambiente. Molte di queste interazioni sono difficilmente previste al momento del test, e anche quando potrebbero essere previste, spesso ci sono così tanti casi da testare che non possono essere affrontati in modo fattibile prima che il software sia rilasciato.
Il testing sul campo si propone di affrontare il problema dei fallimenti delle applicazioni sul campo spostando la fase di test direttamente nell'ambiente di produzione. Ciò rende possibile sfruttare diversi scenari che altrimenti sarebbero difficili da catturare con test tradizionali.
In questa tesi esploriamo l'area del testing sul campo del software, presentiamo uno studio che caratterizza il problema delle applicazioni che falliscono sul campo, un'architettura client-server che può essere sfruttata per organizzare e controllare il processo di test sul campo e un approccio di test che sfrutta l’ambiente di produzione come banco di prova per l'esecuzione dei test case. L'approccio presentato viene valutato empiricamente su un dataset di errori del software, dimostrando che il 35% dei guasti non rilevati internamente potrebbe essere stato rivelato con test sul campo.When interacting with their software systems, users may have to deal with problems like crashes, failures, and program instability. Faulty software running in the field is not only the consequence of ineffective in-house verification and validation techniques, but it is also due to the complexity and diversity of the interactions between an application and its environment. Many of these interactions can be hardly predicted at testing time, and even when they could be predicted, often there are so many cases to be tested that they cannot be all feasibly addressed before the software is released. Field testing aims to tackle the problem of applications failing in the field by moving the testing phase directly in the field environment. This makes it possible to exploit different scenarios that would otherwise be difficult to capture with in-house testing. In this Ph.D. thesis we explore the area of software field testing, we present a study that characterizes the problem of applications failing in the field, a client-server architecture that can be exploited to organize and control the field testing process and a testing approach that exploits the field itself as testbed for running the test cases. The presented approach is empirically evaluated on a popular dataset of software faults demonstrating that 35% of the faults that were not discovered in-house could have been revealed with field testing.
13
Andersson, Martin. "Software Security Testing : A Flexible Architecture for Security Testing." Thesis, Växjö University, School of Mathematics and Systems Engineering, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:vxu:diva-2388.
Full textAbstract:
Abstract: This thesis begins with briefly describing a few vulnerability classes that exist in today’s software. We then continue by describing how these vulnerabilities could be discovered through dynamic testing. Both general testing techniques and existent tools are mentioned.
The second half of this thesis present and evaluates a new flexible architecture. This new architecture has the ability to combine different approaches and create a more flexible environment from where the testing can be conducted. This new flexible architecture aims towards reducing maintenance and/or adaptation time for existing tools or frameworks. The architecture consists of a given set of plug-ins that can be easily replaced to adapt test as needed. We evaluate this architecture by implementing test plug-ins. We also use this architecture and a set of test plug-ins to generate a fuzzer targeted to test a known vulnerable server.
14
Baerisch, Stefan. "Domain-specific model-driven testing." Wiesbaden : Vieweg+Teubner Research, 2010. http://site.ebrary.com/id/10382671.
Full text
15
Polamreddy, Rakesh Reddy, and Syed Ail Irtaza. "Software Testing : A Comparative Study Model Based Testing VS Test Case Based Testing." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3498.
Full textAbstract:
Software testing is considered as one of the key phases in the software-development life cycle (SDLC). The main objective of software testing is to detect the faults either through manual testing or with automated testing approach. The most commonly adopted software testing approach in industries is test case based testing (TCBT) which is usually done manually. TCBT is mainly used by the software testers to formalize and guide their testing activities and set theoretical principals for testing. On the other hand, model based testing (MBT) is widely used automation software testing technique to generate and execute the tests. Both techniques are showing their prominence in real time with some pros and cons. However, there is no formal comparison available between these two techniques. The main objective of this thesis work is to find out the difference in test cases in TCBT and MBT in terms of providing better test coverage ( Statement, Branch and Path), requirement traceability, cost and time. To fulfill the aims of the research we have conducted interviews for static validation, and later we did an experiment for validating those results dynamically. The analysis of experiment results showed that the requirement traceability in MBT generated test cases are very hard to make the test cases traceable to the requirements, particularly with the open-source tool Model J-Unit. However, this can be done by using other commercial tools like Microsoft Spec Explorer or Conformiq Qtronic. Furthermore, we found by conducting experiment, that MBT consumes less time thus it is cost-effective as compared to TCBT and also MBT show better test coverage than TCBT. Moreover, we found that, in our case, requirement traceability is better in traditional TCBT approach as compared to MBT.+4746851975
16
Chodoriwsky, Jacob N. "Error Locating Arrays, Adaptive Software Testing, and Combinatorial Group Testing." Thèse, Université d'Ottawa / University of Ottawa, 2012. http://hdl.handle.net/10393/23083.
Full textAbstract:
Combinatorial Group Testing (CGT) is a process of identifying faulty interactions (“errors”) within a particular set of items. Error Locating Arrays (ELAs) are combinatorial designs that can be built from Covering Arrays (CAs) to not only cover all errors in a system (each involving up to a certain number of items), but to locate and identify the errors as well. In this thesis, we survey known results for CGT, as well as CAs, ELAs, and some other types of related arrays. More importantly, we give several new results. First, we give a new algorithm that can be used to test a system in which each component (factor) has two options (values), and at most two errors are present. We show that, for systems with at most two errors, our algorithm improves upon a related algorithm by Mart´ınez et al. in terms of both robustness and efficiency. Second, we give the first adaptive CGT algorithm that can identify, among a given set of k items, all faulty interactions involving up to three items. We then compare it, performance-wise, to current-best nonadaptive method that can identify faulty interactions involving up to three items. We also give the first adaptive ELA-building algorithm that can identify all faulty interactions involving up to three items when safe values are known. Both of our new algorithms are generalizations of ones previously given by Mart´ınez et al. for identifying all faulty interactions involving up to two items.
17
Afzal, Wasif. "Search-based approaches to software fault prediction and software testing." Licentiate thesis, Karlskrona : Department of Systems and Software Engineering, School of Engineering, Blekinge Institute of Technology, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00439.
Full text
18
Turner, Mitchell K. R. "Software testing toolkit for distributed simulations." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 1994. http://handle.dtic.mil/100.2/ADA291867.
Full textAbstract:
Thesis (M.S. in Systems Technology (Space Systems Operations)) Naval Postgraduate School, September 1994."September 1994." Thesis advisor(s): Gary R. Porter, Michael R. Macedonia. Bibliography: p. 73. Also available online.
19
Apiwattanapong, Taweesup. "Identifying Testing Requirements for Modified Software." Diss., Georgia Institute of Technology, 2007. http://hdl.handle.net/1853/16148.
Full textAbstract:
Throughout its lifetime, software must be changed for many reasons, such as bug fixing, performance tuning, and code restructuring. Testing modified software is the main activity performed to gain confidence that changes behave as they are intended and do not have adverse effects on the rest of the software. A fundamental problem of testing evolving software is determining whether test suites adequately exercise changes and, if not, providing suitable guidance for generating new test inputs that target the modified behavior. Existing techniques evaluate the adequacy of test suites based only on control- and data-flow testing criteria. They do not consider the effects of changes on program states and, thus, are not sufficiently strict to guarantee that the modified behavior is exercised. Also, because of the lack of this guarantee, these techniques can provide only limited guidance for generating new test inputs.
This research has developed techniques that will assist testers in testing evolving software and provide confidence in the quality of modified versions. In particular, this research has developed a technique to identify testing requirements that ensure that the test cases satisfying them will result in different program
states at preselected parts of the software. This research has also developed supporting techniques for identifying testing requirements. Such techniques include (1) a differencing technique, which computes differences and correspondences between two software versions and (2) two dynamic-impact-analysis techniques, which identify parts of software that are likely affected by changes with respect to a set of executions.
20
Kamal, Ahmad Waqas. "A Hierarchical Approach to Software Testing." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4889.
Full textAbstract:
To produce high quality software both software developers and testers need continuous improvement in their work methodologies and processes. So, far much work has been done in the effective ways of eliciting and documenting the requirements. However important aspect is to make sure that whatever is documented in specifications actually works correctly in the developed software. Software testing is done to ensure this phenomenon. Aim of this thesis is to develop a software test case work flow strategy that helps in identification and selection of suitable test paths that can be used as an input to acceptance testing and as a pre-requisite to start actual testing of the system. This thesis focuses on organizing system test artifacts by closely specifying them with system requirements and use cases. In this perspective focus of this thesis is on requirement writing by use cases, requirements traceability, test case prioritization and application acceptance criteria. A structured way to design test cases is proposed with the help of use cases. Some work is done to trace user needs to system requirements and use cases and benefits of using use case modeling approach in structuring the relationships among test cases is analyzed. As test cases are subject to changes in future so, challenges imposed due to traceability among requirements, use cases and test cases are main subjects of this work along with the challenges faced by software testers to perform application acceptance testing. A green path scheme is proposed to help testers define application acceptance criteria and weight assignment approach is used to prioritize the test cases and to determine the percentage of application running successfully.
21
Malik, Ahsan Nawaz & Kashif Masood. "Software Testing Process in Agile Development." Thesis, Blekinge Tekniska Högskola, Avdelningen för för interaktion och systemdesign, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4328.
Full textAbstract:
Software testing is the most important process to verify the quality of a product. Software testing in Agile development is very complex and controversial issue in literature and industry. Different people have different views about software testing in Agile methods, because most of Agile methods do not focus much on software testing activities. Agile strongly focus on the close customer collaboration, short iterations and frequent deliveries. But when it comes to software testing, then it is challenging, as Agile do not include many destructive testing practices, which are normally required for a quality product. This thesis covers the area of software testing process in Agile development. Agile development processes could be more beneficial and refined by adding testing practices and for this purpose; we proposed a concept of an independent integrated software testing team. This research also identifies the practices of Agile development in industry and the critical issues in industry while practicing Agile development. The issues of automated and manual testing, good practices in automation, and how to manage independent testing teams in Agile development are also high lightened. This report highlights every aspect of software testing process in Agile development. This research is based on literature reviews and an industrial survey.
22
Zhuang, Deming. "Software testing and reliability growth models." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1998. http://www.collectionscanada.ca/obj/s4/f2/dsk2/ftp01/MQ36545.pdf.
Full text
23
Grindal, Mats. "Handling combinatorial explosion in software testing." Doctoral thesis, Linköping : Department of Computer and Information Science, Linköpings universitet, 2007. http://www.bibl.liu.se/liupubl/disp/disp2007/tek1073s.pdf.
Full text
24
Unterkalmsteiner, Michael. "Coordinating requirements engineering and software testing." Doctoral thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-663.
Full textAbstract:
The development of large, software-intensive systems is a complex undertaking that is generally tackled by a divide and conquer strategy. Organizations face thereby the challenge of coordinating the resources which enable the individual aspects of software development, commonly solved by adopting a particular process model. The alignment between requirements engineering (RE) and software testing (ST) activities is of particular interest as those two aspects are intrinsically connected: requirements are an expression of user/customer needs while testing increases the likelihood that those needs are actually satisfied. The work in this thesis is driven by empirical problem identification, analysis and solution development towards two main objectives. The first is to develop an understanding of RE and ST alignment challenges and characteristics. Building this foundation is a necessary step that facilitates the second objective, the development of solutions relevant and scalable to industry practice that improve REST alignment. The research methods employed to work towards these objectives are primarily empirical. Case study research is used to elicit data from practitioners while technical action research and field experiments are conducted to validate the developed solutions in practice. This thesis contains four main contributions: (1) An in-depth study on REST alignment challenges and practices encountered in industry. (2) A conceptual framework in the form of a taxonomy providing constructs that further our understanding of REST alignment. The taxonomy is operationalized in an assessment framework, REST-bench (3), that was designed to be lightweight and can be applied as a postmortem in closing development projects. (4) An extensive investigation into the potential of information retrieval techniques to improve test coverage, a common REST alignment challenge, resulting in a solution prototype, risk-based testing supported by topic models (RiTTM). REST-bench has been validated in five cases and has shown to be efficient and effective in identifying improvement opportunities in the coordination of RE and ST. Most of the concepts operationalized from the REST taxonomy were found to be useful, validating the conceptual framework. RiTTM, on the other hand, was validated in a single case experiment where it has shown great potential, in particular by identifying test cases that were originally overlooked by expert test engineers, improving effectively test coverage.
25
Kuyumcu, Caglan (Caglan Ozgur) 1977. "Distributed testing in collaborative software development." Thesis, Massachusetts Institute of Technology, 1999. http://hdl.handle.net/1721.1/80171.
Full text
26
Mohamed, Essack. "A knowledge approach to software testing." Thesis, Stellenbosch : University of Stellenbosch, 2004. http://hdl.handle.net/10019.1/16391.
Full textAbstract:
Thesis (MPhil)--University of Stellenbosch, 2004.ENGLISH ABSTRACT: The effort to achieve quality is the largest component of software cost. Software testing is costly - ranging from 50% to 80% of the cost of producing a first working version. It is resource intensive and an intensely time consuming activity in the overall Systems Development Life Cycle (SDLC) and hence could arguably be the most important phase of the process. Software testing is pervasive. It starts at the initiation of a product with nonexecution type testing and continues to the retirement of the product life cycle beyond the post-implementation phase. Software testing is the currency of quality delivery. To understand testing and to improve testing practice, it is essential to see the software testing process in its broadest terms – as the means by which people, methodology, tools, measurement and leadership are integrated to test a software product. A knowledge approach recognises knowledge management (KM) enablers such as leadership, culture, technology and measurements that act in a dynamic relationship with KM processes, namely, creating, identifying, collecting, adapting, organizing, applying, and sharing. Enabling a knowledge approach is a worthy goal to encourage sharing, blending of experiences, discipline and expertise to achieve improvements in quality and adding value to the software testing process. This research was developed to establish whether specific knowledge such as domain subject matter or business expertise, application or technical skills, software testing competency, and whether the interaction of the testing team influences the degree of quality in the delivery of the application under test, or if one is the dominant critical knowledge area within software testing. This research also set out to establish whether there are personal or situational factors that will predispose the test engineer to knowledge sharing, again, with the view of using these factors to increase the quality and success of the ‘testing phase’ of the SDLC. KM, although relatively youthful, is entering its fourth generation with evidence of two paradigms emerging - that of mainstream thinking and that of the complex adaptive system theory. This research uses pertinent and relevant extracts from both paradigms appropriate to gain quality/success in software testing.
AFRIKAANSE OPSOMMING: By verre die grootste komponent van sagte ware koste is dié verwant aan kwaliteitsversekering. Toetsing van sagte ware is koste intensief en verteenwoordig tussen 50% en 80% van die kostes om ‘n beta weergawe vry te stel. Die toetsing van sagte ware is nie alleenlik duursaam nie, maar ook arbeidintensief en ‘n tydrowende aktiwteit in die sagte ware ontwikkelings lewensiklus en kan derhalwe gereken word as die mees belangrike fase. Toetsing is deurdringend – dit begin by die inisiëring van ‘n produk deur middel van nie-uitvoerende tipe toetsing en eindig by die voleinding van die produklewensiklus na die implementeringsfase. Sagte ware toetsing word beskou as die geldwaarde van kwalitatiewe aflewering. Om toetsing ten volle te begryp en die toepassing daarvan te verbeter, is dit noodsaaklik om die toetsproses holisties te beskou – as die medium en mate waartoe mense, metodologie, tegnieke, meting en leierskap integreer om ‘n sagte ware produk te toets. ‘n Benadering gekenmerk deur kennis erken die dinamiese verhouding waarbinne bestuurselemente van kundigheid, soos leierskap, kultuur, tegnologie en maatstawwe reageer en korrespondeer met prosesse van kundigheid, naamlik skep, identifiseer, versamel, aanpas, organiseer, toepas en meedeel. Die fasilitering van ‘n benadering gekenmerk deur kennis is ‘n waardige doelwit om meedeling, vermenging van ervaringe, dissipline en kundigheid aan te moedig ten einde kwaliteit te verbeter en waarde toe te voeg tot die proses van safte ware toetsing. Die doel van hierdie navorsing is om te bepaal of die kennis van ‘n spesifieke onderwerp, besigheidskundigheid, tegniese vaardighede of die toepassing daarvan, kundigheid van sagte ware toetsing, en/of die interaksie van die toetsspan die mate van kwaliteit beïnvloed, of een van voorgenoemde die dominante kritieke area van kennis is binne die konteks van sagte ware toetsing. Die navorsing beoog ook om te bepaal of daar persoonlike of situasiegebonde fakfore bestaan wat die toetstegnikus vooropstel om kennis te deel, weer eens, met die oog om deur middel van hierdie faktore kwaliteit te verbeter en die toetsfase binne die sagte ware ontwikkelingsiklus suksesvol af te lewer. Ten spyte van die relatiewe jeudgigheid van die bestuur van kennis, betree dit die vierde generasie waaruit twee denkwyses na vore kom – dié van hoofstroom denke en dié van ingewikkelde aangepaste stelselsdenke. Hierdie navorsing illustreer belangrike en toepaslike insette van beide denkwyses wat geskik is vir meedeling van kennis en vir die bereiking van verbeterde kwaliteit / sukses in sagte ware toetsing.
27
Shamshiri, Sina. "Automated unit testing of evolving software." Thesis, University of Sheffield, 2016. http://etheses.whiterose.ac.uk/17066/.
Full textAbstract:
As software programs evolve, developers need to ensure that new changes do not affect the originally intended functionality of the program. To increase their confidence, developers commonly write unit tests along with the program, and execute them after a change is made. However, manually writing these unit-tests is difficult and time-consuming, and as their number increases, so does the cost of executing and maintaining them. Automated test generation techniques have been proposed in the literature to assist developers in the endeavour of writing these tests. However, it remains an open question how well these tools can help with fault finding in practice, and maintaining these automatically generated tests may require extra effort compared to human written ones. This thesis evaluates the effectiveness of a number of existing automatic unit test generation techniques at detecting real faults, and explores how these techniques can be improved. In particular, we present a novel multi-objective search-based approach for generating tests that reveal changes across two versions of a program. We then investigate whether these tests can be used such that no maintenance effort is necessary. Our results show that overall, state-of-the-art test generation tools can indeed be effective at detecting real faults: collectively, the tools revealed more than half of the bugs we studied. We also show that our proposed alternative technique that is better suited to the problem of revealing changes, can detect more faults, and does so more frequently. However, we also find that for a majority of object-oriented programs, even a random search can achieve good results. Finally, we show that such change-revealing tests can be generated on demand in practice, without requiring them to be maintained over time.
28
Tulchak, L. V., I. M. Drozd, Л. В. Тульчак, and І. М. Дрозд. "The importance of automated software testing." Thesis, Вінницький національний аграрний університет, 2015. http://ir.lib.vntu.edu.ua/handle/123456789/7679.
Full textAbstract:
With test automation, as well as with many other compartmentalized IT - disciplines, involves a lot of misconceptions. In order to avoid inefficient use of automation should get its drawbacks and maximize the benefits. Next we will list and give a brief description of the basic nuances of automation and give an answer to the main question of this article - when the automation pays to do to apply.
29
Lipkin, Ilya. "Testing Software Development Project Productivity Model." University of Toledo / OhioLINK, 2011. http://rave.ohiolink.edu/etdc/view?acc_num=toledo1321593577.
Full text
30
Burian, Vojtěch. "Software Testing Platform Development and Implementation." Master's thesis, Vysoká škola ekonomická v Praze, 2012. http://www.nusl.cz/ntk/nusl-150008.
Full textAbstract:
The quality is probably the most significant property of a successful software product. As experience with many software projects has already shown, leaving out testing and quality management from software development process can result in vast and critical customer issues, which usually invoke additional expenses for the software production company. In the course of time, software testing as a discipline has therefore seized an important position among other software development activities. And due to the fact that the software, thanks to rising customer demands and growing competing products portfolio, is getting more complex, the more advanced software testing procedures need to be implemented. Test strategy and iteration planning, implementation of multiple test types into the test suite, test automation, evaluation, administration and maintenance: these activities are commonly required within larger software development projects. Formalized software testing is, nevertheless, being introduced also to projects using agile management techniques which, by management decision or target user industry, are supposed to deliver products of highest quality. This initiates the high focus on the software testing discipline. The purpose of this thesis is to design and implement a new system of software testing within a real project in the CertiCon a.s. company, for which software development is the main business activity. Current issues and gaps for possible improvement, gathered both by project management and the author himself, are analyzed in the first major part of this work and transformed into testing system requirements, which should cover both process changes as well as implementation/development of needed software supporting the process. The second part of thesis is covering the design of the new software testing system, focusing mainly on the area of test management and selection of appropriate software management tool. The final part of the thesis is aimed at implementation of the designed solution within a real organization environment and evaluates its benefits against the previously set requirements.
31
Noller, Yannic [Verfasser]. "Hybrid Differential Software Testing / Yannic Noller." Berlin : Humboldt-Universität zu Berlin, 2020. http://d-nb.info/1219903949/34.
Full text
32
Panichella, Annibale. "Search-Based Software Maintenance and Testing." Doctoral thesis, Universita degli studi di Salerno, 2014. http://hdl.handle.net/10556/1467.
Full textAbstract:
2012 - 2013In software engineering there are many expensive tasks that are performed during development and maintenance activities. Therefore, there has been a lot of e ort to try to automate these tasks in order to signi cantly reduce the development and maintenance cost of software, since the automation would require less human resources. One of the most used way to make such an automation is the Search-Based Software Engineering (SBSE), which reformulates traditional software engineering tasks as search problems. In SBSE the set of all candidate solutions to the problem de nes the search space while a tness function di erentiates between candidate solutions providing a guidance to the optimization process. After the reformulation of software engineering tasks as optimization problems, search algorithms are used to solve them. Several search algorithms have been used in literature, such as genetic algorithms, genetic programming, simulated annealing, hill climbing (gradient descent), greedy algorithms, particle swarm and ant colony. This thesis investigates and proposes the usage of search based approaches to reduce the e ort of software maintenance and software testing with particular attention to four main activities: (i) program comprehension; (ii) defect prediction; (iii) test data generation and (iv) test suite optimiza- tion for regression testing. For program comprehension and defect prediction, this thesis provided their rst formulations as optimization problems and then proposed the usage of genetic algorithms to solve them. More precisely, this thesis investigates the peculiarity of source code against textual documents written in natural language and proposes the usage of Genetic Algorithms (GAs) in order to calibrate and assemble IR-techniques for di erent software engineering tasks. This thesis also investigates and proposes the usage of Multi-Objective Genetic Algorithms (MOGAs) in or- der to build multi-objective defect prediction models that allows to identify defect-prone software components by taking into account multiple and practical software engineering criteria. Test data generation and test suite optimization have been extensively investigated as search- based problems in literature . However, despite the huge body of works on search algorithms applied to software testing, both (i) automatic test data generation and (ii) test suite optimization present several limitations and not always produce satisfying results. The success of evolutionary software testing techniques in general, and GAs in particular, depends on several factors. One of these factors is the level of diversity among the individuals in the population, which directly a ects the exploration ability of the search. For example, evolutionary test case generation techniques that employ GAs could be severely a ected by genetic drift, i.e., a loss of diversity between solutions, which lead to a premature convergence of GAs towards some local optima. For these reasons, this thesis investigate the role played by diversity preserving mechanisms on the performance of GAs and proposed a novel diversity mechanism based on Singular Value Decomposition and linear algebra. Then, this mechanism has been integrated within the standard GAs and evaluated for evolutionary test data generation. It has been also integrated within MOGAs and empirically evaluated for regression testing. [edited by author]
XII n.s.
33
RADAVELLI, Marco. "Using Software Testing to Repair Models." Doctoral thesis, Università degli studi di Bergamo, 2020. http://hdl.handle.net/10446/181507.
Full text
34
Li, Xiang. "The Use of Software Faults in Software Reliability Assessment and Software Mutation Testing." The Ohio State University, 2015. http://rave.ohiolink.edu/etdc/view?acc_num=osu1434394783.
Full text
35
Narendra, Koneru. "Quantitative analysis of domain testing effectiveness /." Adobe Acrobat .pdf file, requires Adobe Acrobat Reader software, 2001. http://etd-submit.etsu.edu/etd/theses/available/etd-0404101-011933/unrestricted/koneru0427.pdf.
Full text
36
Sandhu, Harjinder. "Relational specification as a testing oracle." Morgantown, W. Va. : [West Virginia University Libraries], 2001. http://etd.wvu.edu/templates/showETD.cfm?recnum=1849.
Full textAbstract:
Thesis (M.S.)--West Virginia University, 2001.Title from document title page. Document formatted into pages; contains vi, 75 p. : ill. (some col.). Includes abstract. Includes bibliographical references (p. 53-54).
37
Kuo, Fei-Ching. "On adaptive random testing." Australasian Digital Thesis Program, 2006. http://adt.lib.swin.edu.au/public/adt-VSWT20061109.091517.
Full textAbstract:
Thesis (Ph.D) - Swinburne University of Technology, Faculty of Information & Communication Technologies, 2006.A thesis submitted for the degree of PhD, Faculty of Information and Communication Technologies, Swinburne University of Technology, 2006. Typescript. Bibliography: p. 126-133.
38
ahmed, Tanveer, and Madhu Sudhana Raju. "Integrating Exploratory Testing In Software Testing Life Cycle, A Controlled Experiment." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3414.
Full textAbstract:
Context. Software testing is one of the crucial phases in software development life cycle (SDLC). Among the different manual testing methods in software testing, Exploratory testing (ET) uses no predefined test cases to detect defects. Objectives. The main objective of this study is to test the effectiveness of ET in detecting defects at different software test levels. The objective is achieved by formulating hypotheses, which are later tested for acceptance or rejection. Methods. Methods used in this thesis are literature review and experiment. Literature review is conducted to get in-depth knowledge on the topic of ET and to collect data relevant to ET. Experiment was performed to test hypotheses specific to the three different testing levels : unit , integration and system. Results. The experimental results showed that using ET did not find all the seeded defects at the three levels of unit, integration and system testing. The results were analyzed using statistical tests and interpreted with the help of bar graphs. Conclusions. We conclude that more research is required in generalizing the benefits of ET at different test levels. Particularly, a qualitative study to highlight factors responsible for the success and failure of ET is desirable. Also we encourage a replication of this experiment with subjects having a sound technical and domain knowledge.H.no.2-7-644, Mukrumpura, Karimnagar, Pincode:500001, India, Phone number: +91-9908644775
39
Arafeen, Md Junaid. "Adaptive Regression Testing Strategy: An Empirical Study." Thesis, North Dakota State University, 2012. https://hdl.handle.net/10365/26525.
Full textAbstract:
When software systems evolve, different amounts of code modifications can be involved in different versions. These factors can affect the costs and benefits of regression testing techniques, and thus, there may be no single regression testing technique that is the most cost-effective technique to use on every version. To date, many regression testing techniques have been proposed, but no research has been done on the problem of helping practitioners systematically choose appropriate techniques on new versions as systems evolve. To address this problem, we propose adaptive regression testing (ART) strategies that attempt to identify the regression testing techniques that will be the most cost-effective for each regression testing session considering organization?s situations and testing environment. To assess our approach, we conducted an experiment focusing on test case prioritization techniques. Our results show that prioritization techniques selected by our approach can be more cost-effective than those used by the control approaches.
40
Duncan, Ishbel M. M. "Strong mutation testing strategies." Thesis, Durham University, 1993. http://etheses.dur.ac.uk/5771/.
Full textAbstract:
Mutation Testing (or Mutation Analysis) is a source code testing technique which analyses code by altering code components. The output from the altered code is compared with output from the original code. If they are identical then Mutation Testing has been successful in discerning a weakness in either the test code or the test data. A mutation test therefore helps the tester to develop a program devoid of simple faults with a well developed test data set. The confidence in both program and data set is then increased. Mutation Analysis is resource intensive. It requires program copies, with one altered component, to be created and executed. Consequently, it has been used mainly by academics analysing small programs. This thesis describes an experiment to apply Mutation Analysis to larger, multi-function test programs. Mutations, alterations to the code, are induced using a sequence derived from the code control flow graph. The detection rate of live mutants, programs whose output match the original, was plotted and compared against data generated from the standard technique of mutating in statement order. This experiment was repeated for different code components such as relational operators, conditional statement or pointer references. A test was considered efficient if the majority of live mutants was detected early in the test sequence. The investigations demonstrated that control flow driven mutation could improve the efficiency of a test. However, the experiments also indicated that concentrations of live mutants of a few functions or statements could effect the efficiency of a test. This conclusion lead to the proposal that mutation testing should be directed towards functions or statements containing groupings of the code component that give rise to the live mutants. This effectively forms a test focused onto particular functions or statements.
41
Jørgensen, Lars Kristoffer Ulstein. "A software tool for risk-based testing." Thesis, Norwegian University of Science and Technology, Department of Computer and Information Science, 2005. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-9222.
Full textAbstract:
There are several approaches to risk-based testing. They have in common that risk is the focus when the tester chooses what to test. In this thesis we will combine some of these approaches and present our method for risk-based testing. The method analyses the risk for each part of the system and use a hazard analysis to indicate what can go wrong. The test efficiency and risk determine the tests priority. We have shown how a software tool can support our method and implemented a proof of concept. The implementation is presented and been tried out by an experienced tester.
42
Gustafsson, Kristian. "Improvements For An Embedded Software Testing Method." Thesis, KTH, Maskinkonstruktion (Inst.), 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-99331.
Full textAbstract:
Testing is a widespread subject that usually is divided into hardware testing and software testing. The software testing can be done in many different ways and there exist several standards and guidelines for successful testing. This master thesis has investigated the possibilities for improvement of a software test method used by a large Swedish company. The work has been carried out at the Integration and Verification department at the company. An investigation of the undetected defects during the test execution is carried out to explore those characteristics, which are not covered by the current testing method. The purpose with this master thesis is to evaluate the company’s testing method and to give suggestions for possible improvements in the process during the system integration phase of the development process One part of the work includes a survey by interviewing key personnel’s for getting a better insight of the problem, a thorough literature study and attendance at a course providing an overview of the system. The other part of the work was the examination of a database storing all the data related to the faults from different projects. The result from the examination shows that 4.4 percent of all the faults submitted are found after the testing phase, 79.1 percent of these faults are related to the software in the system. Further investigation showed that 51.2 percent of the total number of faults found after the test phase where related to the systems configuration database and the administrator tool for the system. The conclusion to be drawn from these results is that the testing method being used by the company is good. However, there is room for improvement for some parts of the method. Most of the faults discovered after the testing process are faults related to the system configuration database and the administrator tool for the system. The method for testing these two parts of the system should be reviewed and improved.Testning är ett stort ämne som vanligtvis delas in i hårdvaru- och mjukvarutestning. Mjukvaran i ett system kan testats på många olika sätt och det finns idag flera olika standarder och riktlinjer för hur en lyckad testning skall gå till. Detta examensarbete har utrett möjligheterna att förbättra en testmetod för mjukvara som ett stort svenskt företag använder. Arbetet har utförts på Integrations- och verifieringsavdelningen på företaget. De fel som har förblivit oupptäckta efter den ordinarietestningen har blivit undersökta för att se om dessa har något karaktärsdrag som inte stöds utav den aktuella testmetoden. Syftet med detta arbete är att utvärdera företagets testmetod och komma med förslag till förbättringar av systemintegrationsfasen av utvecklingsprocessen. En del av arbetet har innefattar en undersökning där nyckelpersoner har blivit intervjuade för att få djupare insikt av problemet, men även en litteraturstudie har genomförts samt deltagande i en kurs som gav en överblick över hur systemet fungerade. Den andra delen av arbetet var undersökningen utav en databas som innehåller all information som är relaterad till fel från olika projekt. Resultatet från undersökningen visar att 4,4 procent av alla inrapporterade fel är upptäckta efter avslutad testning och att 79,1 procent av dessa fel är relaterade till mjukvaran i systemet. Vidare undersökning visade att 51,2 procent av det totala antalet fel efter avslutad testning var relaterade till systemets konfigurations databas och administrationsverktyget för systemet. Slutsatserna man kan dra utifrån dessa resultat är att företagets testmetod är bra, men det går att förbättra vissa delar av den. De flesta felen som upptäcktes efter testprocessen var relaterade till systemets konfigurations databas samt till systemets administrativa verktyg. Den testmetod som används för att testa dessa två borde ses över och förbättras.
43
Brännström, Gustaf. "Automated software testing for cross-platform systems." Thesis, Umeå universitet, Institutionen för datavetenskap, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-56327.
Full textAbstract:
SILK is the preferred audio codec to use in a call between Skype clients. Everytime the source code has been changed there is a risk the code is no longer bit-exact between all the dffierent platforms. The main task for this thesis is to make it possible to test bit-exactness between platforms automatically to save resources for the company. During this thesis a literature study about software testing has been carried out to find a good way of testing bit-exactness between different platforms. The advantages and disadvantages with the different testing techniques was examined during this study. The result of the thesis is a framework for testing bit-exactness between several different platforms. Based on the conclusions from the literature study the framework is using a technique called data-driven testing to carry out the bit-exactness tests on SILK.
44
Pulipaka, Avinash Arepaka Sravanthi. "Outsourced Offshore Software Testing Challenges and Mitigations." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3470.
Full textAbstract:
Software development comprises of different phases like requirements, analysis, design coding and testing. In this contemporary world of software development, development of software in globalized scenarios is prevalent and prominent. As part of different globalized scenarios this thesis magnifies the scenario of software product transfer which deals with the testing of software in the offshore location.+919502697610 +919849674412
45
Karshibayev, Bahodir. "Defining Requirements for Vehicular Software Integration Testing." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-33440.
Full textAbstract:
In every software/system development life cycle, requirement representation is one of the crucial phases. The future success of the development process and end product quality very much depends on the quality of the requirements. Often, ambiguous and inconsistent requirements lead to a rework during the later stages of the development process. Furthermore, requirement specifications are used as an important input for testing activities, such as generating test case specifications. This thesis presents a Systematic Literature Review (SLR) of studies related to requirement representation (definition) for software integration testing. The purpose of this research is to improve current knowledge in requirement representation for integration testing in order to identify the state of the art in the area. We are interested in identifying possible suggestions for requirement representation, such as approaches, tools, lesson learned, and techniques that can be used for integration testing. The search strategy primarily retrieved 1060 studies in total, out of which 56 were considered as primarily relevant studies. However, during the data extraction phase of the SLR, 40 papers were found irrelevant according to inclusion/exclusion criteria. These studies were divided into different categories: model-based, executable specifications, natural-textual language, and combinational language. The systematic review aims at identifying probable gaps in research about requirement representation (definition) for software integration testing. The thesis work presents the results of performing data analysis and synthesis regarding all final selected studies. The proposed suggestions for requirement representation and their relation to integration testing are summarized. Although not many studies were found that addressed requirement representation for integration testing, this issue has been an interest of scientists as well as practitioners for many years. The majority of reviewed publications used a model-based approach in order to solve the issue of requirement representation for integration testing. On other hand, one of the most problematic ways of performing requirement representation is using natural-textual language. Expressing requirements in natural-textual language may introduce ambiguity or inconsistency, and these ambiguities/inconsistencies can be noticed in the later stages of the development process. The later they are identified, the higher the cost of eliminating these ambiguities or inconsistencies, which can significantly increase the development costs. Thus, the authors recommend using some support tool or methodology when expressing requirements in natural-textual language. Using a support tool or methodology can help to identify and eliminate ambiguities or inconsistencies in the early phase of the system/software development process. In the other publications, the authors combined two different requirement expressions together in order to improve the requirements' quality and perform virtual integration testing in the early phases of the development process.
46
Levin, Lukas, and Christoffer Stjernlöf. "Automated Testing Toolkit Service : Software Requirements Specification." Thesis, KTH, Skolan för informations- och kommunikationsteknik (ICT), 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-227859.
Full textAbstract:
Frequent automated testing of software services is vital to speed up the development cycle and ensure upgrades do not break existing features. With a centralised testing service, it is also possible to catch errors at customer sites before they become severe enough that the customers (or in the end – regular people) start suffering from them. It also gives the customers an insight into how well their services are working at a predictable cost. When developing a larger software system such as an automated testing service toolkit, a requirements specification can drastically cut development costs at the expense of a larger up-front investment. We discover some of the immediately important requirements for the first version of such an automated testing toolkit.Upprepade automatiserade tester av mjukvarutjänster är mycket viktiga för att öka utvecklingshastigheten och försäkra att uppgraderingar inte påverkar existerande, äldre delar av systemet. Med en centraliserad testningstjänst är det också möjligt att upptäcka fel i kundens miljö innan de blir allvarliga nog att kunden märker av dem. Det ger även kunden en möjlighet att se hur väl deras tjänster fungerar utan att behöva betala oförutsedda driftrelaterade kostnader. När större mjukvarusystem, som en centraliserad tjänst för automatiserade tester, kan en kravspecifikation drastiskt minska utvecklingskostnaden mot en större initial investering. Vi har undersökt vilka några av de omedelbart viktiga kraven är för en första version av denna typ av tjänst.
47
Eatinger, Christopher J. "Testing automation tools for secure software development." Thesis, Monterey, Calif. : Naval Postgraduate School, 2007. http://bosun.nps.edu/uhtbin/hyperion-image.exe/07Jun%5FEatinger.pdf.
Full textAbstract:
Thesis (M.S. in Computer Science)--Naval Postgraduate School, June 2007.Thesis Advisor(s): Mikhail Auguston. "June 2007." Description based on title screen as viewed on August 14, 2007. Includes bibliographical references (p. 61). Also available in print.
48
Olimpiew, Erika Mir. "Model-based testing for software product lines." Fairfax, VA : George Mason University, 2008. http://hdl.handle.net/1920/3039.
Full textAbstract:
Thesis (Ph.D.)--George Mason University, 2008.Vita: p. 276. Thesis director: Hassan Gomaa. Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Information Technology. Title from PDF t.p. (viewed July 3, 2008). Includes bibliographical references (p. 267-275). Also issued in print.
49
奚永忻 and Yung-shing Paul Hsi. "On proportional sampling strategies in software testing." Thesis, The University of Hong Kong (Pokfulam, Hong Kong), 2001. http://hub.hku.hk/bib/B3122443X.
Full text
50
Davis, Edward V. Jr. "Software testing for evolutionary iterative rapid prototyping." Thesis, Monterey, California: Naval Postgraduate School, 1990. http://hdl.handle.net/10945/27570.
Full textAbstract:
Approved for public release; distribution unlimited.Rapid prototyping is emerging as a promising software development paradigm. It provides a systematic and automatable means of developing a software system under circumstances where initial requirements are not well known or where requirements change frequently during development. To provide high software quality assurance requires sufficient software testing. The unique nature of evolutionary iterative prototyping is not well-suited for classical testing methodologies, therefore the need exists for a testing methodology tailored for this prototyping paradigm. This thesis surveys current prototyping and testing practices to provide a foundation for developing a software testing methodology for prototyping. The thesis then describes a testing methodology for rapid prototyping, Spiral Testing, and the Test Goal Tracking System (TGTS), a requirements-based testing tool developed for use with the Computer Aided Prototyping System (CAPS). TGTS provides the first in an anticipated family of testing tools to support the CAPS environment. This thesis shows key prototyping characteristics impinging on testing, the value of Spiral Testing and the feasibility and qualities of complementary testing tools to support evolutionary iterative rapid prototyping.