Dissertations / Theses on the topic 'Computer software testing'
To see the other types of publications on this topic, follow the link: Computer 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 'Computer 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
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.
2
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
3
Bhatia, Sanjay. "Software tools for computer-controlled fatigue testing." Thesis, Virginia Tech, 1986. http://hdl.handle.net/10919/45749.
Full textAbstract:
Past efforts at implementing Load Spectrum Generation and Neuber Control have centered around minicomputers and analog circuits. The use of a personal computer to implement the tasks is presented. On implementation of the load Spectrum Generation software, the response of the Materials Testing System was investigated for distortion and attenuation. In particular, the effect of the resolution of the waveform on the test system response was noted. There was negligible attenuation for full scale frequencies of up to 20 Hz. Greater waveform resolution was required at lower frequencies than at higher frequencies. On implementation of the Neuber Control program, the accuracy obtained at the Neuber hyperbolas was noted. Better accuracy was obtained at ramp frequencies below 0.1 Hz.
Based on the results obtained after implementing the Load Spectrum Generator program and the Neuber Control program, the performance of the personal computer in controlling fatigue tests is evaluated. Cost effectiveness and versatility favor the use of a personal computer for the control of fatigue tests.Master of Science
4
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
5
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
6
Davis, Edward V. "Software testing for evolutionary iterative rapid prototyping." Monterey, California : Naval Postgraduate School, 1990. http://handle.dtic.mil/100.2/ADA232555.
Full textAbstract:
Thesis (M.S. in Computer Science)--Naval Postgraduate School, December 1990.Thesis Advisor(s): Shimeall, Timothy J. Second Reader: Barnes, Patrick D. "December 1990." Description based on title screen as viewed on March 29, 2010. DTIC Identifier(s): Computer Program Verification, Prototypes, Software Engineering, User Manuals. Author(s) subject terms: Software Testing, Software Prototyping, Rapid Prototyping, Reusable Components, Requirements-based Testing, Software Testing Tools. Includes bibliographical references (p. 276-281). Also available in print.
7
Towey, David Peter. "Studies of different variations of Adaptive Random Testing." Thesis, View the Table of Contents & Abstract, 2006. http://sunzi.lib.hku.hk/hkuto/record/B3551212X.
Full text
8
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.
9
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.
10
Baerisch, Stefan. "Domain-specific model-driven testing." Wiesbaden : Vieweg+Teubner Research, 2010. http://site.ebrary.com/id/10382671.
Full text
11
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.
12
Hsi, Yung-shing Paul. "On proportional sampling strategies in software testing." Hong Kong : University of Hong Kong, 2001. http://sunzi.lib.hku.hk/hkuto/record.jsp?B22713293.
Full text
13
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).
14
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.
15
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.
16
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.
17
奚永忻 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
18
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.
19
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
20
Argote, Garcia Gonzalo. "Formal verification and testing of software architectural models." FIU Digital Commons, 2009. http://digitalcommons.fiu.edu/etd/1308.
Full textAbstract:
Ensuring the correctness of software has been the major motivation in software research, constituting a Grand Challenge. Due to its impact in the final implementation, one critical aspect of software is its architectural design. By guaranteeing a correct architectural design, major and costly flaws can be caught early on in the development cycle. Software architecture design has received a lot of attention in the past years, with several methods, techniques and tools developed. However, there is still more to be done, such as providing adequate formal analysis of software architectures. On these regards, a framework to ensure system dependability from design to implementation has been developed at FIU (Florida International University). This framework is based on SAM (Software Architecture Model), an ADL (Architecture Description Language), that allows hierarchical compositions of components and connectors, defines an architectural modeling language for the behavior of components and connectors, and provides a specification language for the behavioral properties. The behavioral model of a SAM model is expressed in the form of Petri nets and the properties in first order linear temporal logic.
This dissertation presents a formal verification and testing approach to guarantee the correctness of Software Architectures. The Software Architectures studied are expressed in SAM. For the formal verification approach, the technique applied was model checking and the model checker of choice was Spin. As part of the approach, a SAM model is formally translated to a model in the input language of Spin and verified for its correctness with respect to temporal properties. In terms of testing, a testing approach for SAM architectures was defined which includes the evaluation of test cases based on Petri net testing theory to be used in the testing process at the design level. Additionally, the information at the design level is used to derive test cases for the implementation level. Finally, a modeling and analysis tool (SAM tool) was implemented to help support the design and analysis of SAM models. The results show the applicability of the approach to testing and verification of SAM models with the aid of the SAM tool.
21
Bortz, Kent. "Coverage testing in a production software development environment." [Denver, Colo.] : Regis University, 2006. http://165.236.235.140/lib/KBortz2006.pdf.
Full text
22
Saff, David 1976. "Automatic continuous testing to speed software development." Thesis, Massachusetts Institute of Technology, 2004. http://hdl.handle.net/1721.1/30096.
Full textAbstract:
Thesis (S.M.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2004.Includes bibliographical references (p. 147-152).
Continuous testing is a new feature for software development environments that uses excess cycles on a developer's workstation to continuously run regression tests in the background, providing rapid feedback about test failures as source code is edited. It is intended to reduce the time and energy required to keep code well-tested, and to prevent regression errors from persisting uncaught for long periods of time. The longer that regression errors are allowed to linger during development, the more time is wasted debugging and fixing them once they are discovered. By monitoring and measuring software projects, we estimate that the wasted time, consisting of this preventable extra fixing cost added to the time spent running tests and waiting for them to complete, accounts for 10-15% of total development time. We present a model of developer behavior that uses data from past projects to infer developer beliefs and predict behavior in new environments -in particular, when changing testing methodologies or tools to reduce wasted time. This model predicts that continuous testing would reduce wasted time by 92-98%, a substantial improvement over other approaches we evaluated, such as automatic test prioritization and changing manual test frequencies. A controlled human experiment indicates that student developers using continuous testing were three times more likely to complete a task before the deadline than those without, with no significant effect on time worked.
(cont.) Most participants found continuous testing to be useful and believed that it helped them write better code faster. 90% would recommend the tool to others. We show the first empirical evidence of a benefit from continuous compilation, a popular related feature. Continuous testing has been integrated into Emacs and Eclipse. We detail the functional and technical design of the Eclipse plug-in, which is publicly beta-released.
by David Saff.
S.M.
23
Liu, Ning Lareina. "A study on improving adaptive random testing." Click to view the E-thesis via HKUTO, 2006. http://sunzi.lib.hku.hk/hkuto/record/B36428061.
Full text
24
Coteli, Mert Burkay. "Testing Effectiveness And Effort In Software Product Lines." Master's thesis, METU, 2013. http://etd.lib.metu.edu.tr/upload/12615345/index.pdf.
Full textAbstract:
Software product lines (SPL) aim to decrease the total software development cost by the help of reusability and variability. However, the increasing number of variations for the delivery types of products would result in increasing cost of the verification and validation process. Total testing cost of development can also be decreased by reusing test cases and scripts. The main objective of this study is to increase testing effectiveness while minimizing testing effort. Four different cases consisting of Aselsan&rsquos SPL projects have been studied. Firstly, FIG Basis path method was applied at the functional testing phase, and an increase on the testing effectiveness value has been observed. FIG basis path method is a test case sequence generation technique using the feature tree of the software component. This method would be preferable to improve testing effectiveness on the functional verification phase. The second study was on testing effort estimation. There are two testing approaches for SPL projects, namely infrastructure based and product focused testing. These two techniques have been compared in terms of testing effort. It was a study that gives an idea to test managers about the selection of the proper testing technique. Thirdly, reusability techniques were evaluated. Reusability of testing artifacts can be used to decrease the total testing effort. Two reusability techniques for testing artifacts were compared in terms of the number of test cases. Proper technique would be chosen to decrease testing effort. Finally, selection of a reference application on platform tests was proposed and software products were grouped according to the redundancy values. Then, testing effectiveness values were evaluated for each test grouping.
25
Turner, Christopher David. "State-based testing : a new method for testing object-oriented programs." Thesis, Durham University, 1994. http://etheses.dur.ac.uk/5087/.
Full textAbstract:
State-based testing is a new method for testing object-oriented programs. The information stored in the state of an object is of two kinds: control-information and data-storage. The control-information transitions are modelled as a finite state automaton. Every operation of the class under test is considered as a mapping from starting states to a finishing states dependent upon the parameters passed. The possible parameter values are analysed for significant values which combined with the invocation of an operation can be used to represent stimuli applied to an object under test. State-based testing validates the expected transformations that can occur within a class. Classes are modelled using physical values assigned to the attributes of the class. The range of physical values is reduced by the use of a technique based on equivalence partitioning. This approach has a number of advantages over the conceptual modelling of a class, in particular the ease of manipulation of physical values and the independence of each operation from the other operations provided by an object. The technique when used in conjunction with other techniques provides an adequate level of validation for object-oriented programs. A suite of prototype tools that automate the generation of state-based test cases are outlined. These tools are used in four case studies that are presented as an evaluation of the technique. The code coverage achieved with each case study is analysed for the factors that affect the effectiveness of the state-based test suite. Additionally, errors have been seeded into 2 of the classes to determine the effectiveness of the technique for detecting errors on paths that are executed by the test suite. 92.5% of the errors seeded were detected by the state-based test-suite.
26
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.
27
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.
28
de, Chauveron Jérôme. "Improving Software Testing in an Agile Environment." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-275913.
Full textAbstract:
Software development has evolved at an ever-increasing pace over the past years, one of the forces behind this acceleration is the move from on-premise application to cloud- based software: Software as a service (SaaS). Cloud computing has changed the way applications are deployed used and tested. Time-to-market for software has decreased from the order of month to the order of day. Furthermore, Source Code Management based on Git (introduced in 2005), changed the way software is developed allowing for collaborative work thanks to automatic merge and versioning. Additionally, continuous integration (CI) tools developed on top of Git facilitate regular testing, build and deployment. Nevertheless, despite of being necessary Integration tools, they require an extensive amount of cloud resources which may stretch the duration of code integration. The goal of this thesis is to optimize the speed of the CI pipeline, improve the software tests while optimizing the load on the cloud resources. As a result of the work of this thesis the completion time of the software test has been decreased by 21%, and the total continuous integration completion time decreased by 18%. Furthermore, new bugs and anomalies were detected thanks to improved soft- ware test and new approaches for the emulation of extreme scenarios. The bugs were corrected making the system more resilient and improving the user experience.Programvaruutveckling har accelererat i en allt snabbare takt under de senaste åren. En av krafterna bakom denna acceleration är övergången från lokal applikation till molnbaserad programvara: Programvara som en tjänst (SaaS). Molntjänster (Cloud computing) har förändrat sättet applikationer distribueras, används och testas. Tiden till att mjukvaran når marknaden har minskat från månader till dagligen. Dessutom har källkodshantering baserad på Git (introducerades 2005), ändrat hur programvaran utvecklas, vilket möjliggör samarbete, detta tack vare automatisk sam- manslagning och versionshantering. Dessutom underlättar integrationsverktyg (CI) utvecklade ovanpå Git, regelbunden testning, byggnad och utveckling. Trots att de är nödvändiga integrationsverktyg, kräver de en omfattande mängd molnresurser som kan tänja på varaktigheten för integration. Målet med denna avhandling är att optimera hastigheten på CI-pipeline, förbättra programvarutester medan belastningen på molnresurserna optimeras. Som ett resultat av arbetet med denna avhandling har mjukvarutesternas slutföringstid reducerats med 21 %, och den totala kompletteringstiden för kontinuerlig integration reducerats med 18 %. Dessutom upptäcktes nya buggar och avvikelser, tack vare förbättrade mjukvarutester och nya tillvägagångssätt för emulering av extrema scenarier. Buggarna korrigerades, vilket gör systemet mer motståndskraftigt med en förbättrad användarupplevelse.
29
Myburgh, W. D. "Development of a tool to test computer protocols." Thesis, Stellenbosch : Stellenbosch University, 2003. http://hdl.handle.net/10019.1/53363.
Full textAbstract:
Thesis (MSc) -- Stellenbosch University, 2003.ENGLISH ABSTRACT: Software testing tools simplify and automate the menial work associated with testing. Moreover, for complex concurrent software such as computer protocols, testing tools allow testing on an abstract level that is independent of specific implementations. Standard conformance testing methodologies and a number of testing tools are commercially available, but detailed descriptions of the implementation of such testing tools are not widely available. This thesis investigates the development of a tool for automated protocol testing in the ETH Oberon development environment. The need to develop a protocol testing tool that automates the execution of specified test cases was identified in collaboration with a local company that develops protocols in the programming language Oberon. Oberon is a strongly typed secure language that supports modularisation and promotes a readable programming style. The required tool should translate specified test cases into executable test code supported by a runtime environment. A test case consists of a sequence of input actions to which the software under test is expected to respond by executing observable output actions. A number of issues are considered of which the first is concerned with the representation of test case specifications. For this, a notation was used that is basically a subset of the test specification language TTCN-3 as standardised by the European Telecommunications Standards Institute. The second issue is the format of executable test cases and a suitable runtime environment. A translator was developed that generates executable Oberon code from specified test cases. The compiled test code is supported by a runtime library, which is part of the tool. Due to the concurrent nature of a protocol environment, concurrent processes in the runtime environment are identified. Since ETH Oberon supports multitasking in a limited sense, test cases are executed as cooperating background tasks. The third issue is concerned with the interaction between an executing test case and a system under test. It is addressed by an implementation dependent interface that maps specified test interactions onto real interactions as required by the test context in which an implementation under test operates. A supporting protocol to access the service boundary of an implementation under test remotely and underlying protocol service providers are part of a test context. The ETH Oberon system provides a platform that simplifies the implementation of protocol test systems, due to its size and simple task mechanism. Operating system functionality considered as essential is pointed out in general terms since other systems could be used to support such testing tools. In conclusion, directions for future work are proposed.
AFRIKAANSE OPSOMMING: Toetsstelsels vir programmatuur vereenvoudig en outomatiseer die slaafse werk wat met toetsing assosieer word. 'n Toetsstelsel laat verder toe dat komplekse gelyklopende programmatuur, soos rekenaarprotokolle, op 'n abstrakte vlak getoets word, wat onafhanklik van spesifieke implementasies is. Daar bestaan standaard metodes vir konformeringstoetsing en 'n aantal toetsstelsels is kommersiëel beskikbaar. Uitvoerige beskrywings van die implementering van sulke stelsels is egter nie algemeen beskikbaar nie. Hierdie tesis ondersoek die ontwikkeling van 'n stelsel vir outomatiese toetsing van protokolle in die ontwikkelingsomgewing van ETH Oberon. Die behoefte om 'n protokoltoetsstelsel te ontwikkel, wat die uitvoering van gespesifiseerde toetsgevalle outomatiseer, is geïdentifiseer in oorleg met 'n plaaslike maatskappy wat protokolle ontwikkel in die Oberon programmeertaal. Oberon is 'n sterkgetipeerde taal wat modularisering ondersteun en a leesbare programmeerstyl bevorder. Die toestsstelsel moet gespesifiseerde toetsgevalle vertaal na uitvoerbare toetskode wat ondersteun word deur 'n looptydomgewing. 'n Toetsgeval bestaan uit 'n reeks van toevoeraksies waarop verwag word dat die programmatuur wat getoets word, sal reageer deur die uitvoering van afvoeraksies wat waargeneem kan word. 'n Aantal kwessies word aangeraak, waarvan die eerste te make het met die voorstelling van die spesifikasie van toetsgevalle. Hiervoor is 'n notasie gebruik wat in wese 'n subversameling van die toetsspesifikasietaal TTCN-3 is. TTCN-3 is gestandardiseer deur die European Telecommunications Standards Institute. Die tweede kwessie is die formaat van uitvoerbare toetsgevalle en 'n geskikte looptydomgewing. 'n Vertaler is ontwikkel wat uitvoerbare Oberon-kode genereer vanaf gespesifiseerde toetsgevalle. Die vertaalde toetskode word ondersteun deur 'n biblioteek van looptydfunksies, wat deel van die stelsel is. As gevolg van die eienskap dat 'n protokolomgewing uit gelyklopende prosesse bestaan, word daar verskillende tipes van gelyklopende prosesse in 'n protokoltoetsstelsel geïdentifiseer. Aangesien ETH Oberon 'n beperkte multitaakstelsel is, word toetsgevalle vertaal na eindige outomate wat uitgevoer word as samewerkende agtergrondtake. Die derde kwessie het te make met die interaksie tussen 'n toetsgeval wat uitgevoer word en die stelsel wat getoets word. Dit word aangespreek deur 'n koppelvlak wat gespesifiseerde interaksies afbeeld op werklike interaksies soos vereis deur die konteks waarin 'n implementasie onderworpe aan toetsing uitvoer. 'n Ondersteunende protokolom die dienskoppelvlak van die implementasie oor 'n afstand te bereik en ander onderliggende protokoldienste is deel van 'n toetskonteks. Die ETH Oberon-stelsel help in die vereenvoudiging van die implementasie van protokol toetsstelsels, as gevolg van die stelsel se grootte en die eenvoudige taakhanteerder . Die essensiële funksionaliteit van bedryfsstelsels word uitgelig in algemene terme omdat ander stelsels gebruik kan word om toetsstelsels te ondersteun. Ten slotte word voorstelle vir opvolgwerk gemaak.
30
Al-Azzani, Sarah. "Architecture-centric testing for security." Thesis, University of Birmingham, 2014. http://etheses.bham.ac.uk//id/eprint/5206/.
Full textAbstract:
This thesis presents a novel architecture-centric approach, which uses Implied Scenarios (IS) to detect design-vulnerabilities in the software architecture. It reviews security testing approaches, and draws on their limitations in addressing unpredictable behaviour in the face of evolution. The thesis introduces the concept of Security ISs as unanticipated (possibly malicious) behaviours that indicate potential insecurities in the architecture. The IS approach uses the architecture as the appropriate level of abstraction to tackle the complexity of testing. It provides potential for scalability to test large scale complex applications. It proposes a three-phased method for security testing: (1) Detecting design-level vulnerabilities in the architecture in an incremental manner by composing functionalities as they evolve. (2) Classifying the impact of detected ISs on the security of the architecture. (3) Using the detected ISs and their impact to guide the refinement of the architecture. The refinement is test-driven and incremental, where refinements are tested before they are committed. The thesis also presents SecArch, an extension to the IS approach to enhance its search-space to detect hidden race conditions. The thesis reports on the applications of the proposed approach and its extension to three case studies for testing the security of distributed and cloud architectures in the presence of uncertainty in the operating environment, unpredictability of interaction and possible security IS.
31
Cao, Bingfei. "Augmenting the software testing workflow with machine learning." Thesis, Massachusetts Institute of Technology, 2018. http://hdl.handle.net/1721.1/119752.
Full textAbstract:
Thesis: M. Eng., Massachusetts Institute of Technology, Department of Electrical Engineering and Computer Science, 2018.This electronic version was submitted by the student author. The certified thesis is available in the Institute Archives and Special Collections.
Cataloged from student-submitted PDF version of thesis.
Includes bibliographical references (pages 67-68).
This work presents the ML Software Tester, a system for augmenting software testing processes with machine learning. It allows users to plug in a Git repository of the choice, specify a few features and methods specific to that project, and create a full machine learning pipeline. This pipeline will generate software test result predictions that the user can easily integrate with their existing testing processes. To do so, a novel test result collection system was built to collect the necessary data on which the prediction models could be trained. Test data was collected for Flask, a well-known Python open-source project. This data was then fed through SVDFeature, a matrix prediction model, to generate new test result predictions. Several methods for the test result prediction procedure were evaluated to demonstrate various methods of using the system.
by Bingfei Cao.
M. Eng.
32
Kieżun, Adam. "Effective software testing with a string-constraint solver." Thesis, Massachusetts Institute of Technology, 2009. http://hdl.handle.net/1721.1/53291.
Full textAbstract:
Thesis (Ph. D.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2009.Cataloged from PDF version of thesis.
Includes bibliographical references (p. 91-100).
This dissertation presents techniques and tools for improving software reliability, by using an expressive string-constraint solver to make implementation-based testing more effective and more applicable. Concolic testing is a paradigm of implementation-based systematic software testing that combines dynamic symbolic execution with constraint-based systematic execution-path enumeration. Concolic testing is easy to use and effective in finding real errors. It is, however, limited by the expressiveness of the underlying constraint solver. Therefore, to date, concolic testing has not been successfully applied to programs with highly-structured inputs (e.g., compilers), or to Web applications. This dissertation shows that the effectiveness and applicability of concolic testing can be greatly improved by using an expressive and efficient string-constraint solver, i.e., a solver for constraints on string variables. We present the design, implementation, and experimental evaluation of a novel string-constraint solver. Furthermore, we show novel techniques for two important problems in concolic testing: getting past input validation in programs with highly-structured inputs, and creating inputs that demonstrate security vulnerabilities in Web applications.
by Adam Kieżun.
Ph.D.
33
Marinov, Darko 1976. "Automatic testing of software with structurally complex inputs." Thesis, Massachusetts Institute of Technology, 2005. http://hdl.handle.net/1721.1/30161.
Full textAbstract:
Thesis (Ph. D.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2005.Includes bibliographical references (p. 123-132).
Modern software pervasively uses structurally complex data such as linked data structures. The standard approach to generating test suites for such software, manual generation of the inputs in the suite, is tedious and error-prone. This dissertation proposes a new approach for specifying properties of structurally complex test inputs; presents a technique that automates generation of such inputs; describes the Korat tool that implements this technique for Java; and evaluates the effectiveness of Korat in testing a set of data-structure implementations. Our approach allows the developer to describe the properties of valid test inputs using a familiar implementation language such as Java. Specifically, the user provides an imperative predicate--a piece of code that returns a truth value--that returns true if the input satisfies the required property and false otherwise. Korat implements our technique for solving imperative predicates: given a predicate and a bound on the size of the predicate's inputs, Korat automatically generates the bounded-exhaustive test suite that consists of all inputs, within the given bound, that satisfy the property identified by the predicate. To generate these inputs, Korat systematically searches the bounded input space by executing the predicate on the candidate inputs. Korat does this efficiently by pruning the search based on the predicate's executions and by generating only nonisomorphic inputs. Bounded-exhaustive testing is a methodology for testing the code on all inputs within the given small bound.
(cont.) Our experiments on a set of ten linked and array- based data structures show that Korat can efficiently generate bounded-exhaustive test suites from imperative predicates even for very large input spaces. Further, these test suites can achieve high statement, branch, and mutation coverage. The use of our technique for generating structurally complex test inputs also enabled testers in industry to detect faults in real, production-quality applications.
by Darko Marinov.
Ph.D.
34
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.
35
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.
36
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
37
Liu, Ning Lareina, and 劉寧. "A study on improving adaptive random testing." Thesis, The University of Hong Kong (Pokfulam, Hong Kong), 2006. http://hub.hku.hk/bib/B36428061.
Full text
38
Reid, Stuart Christopher. "Software component testing : a standard and the effectiveness of techniques." Thesis, University of South Wales, 1997. https://pure.southwales.ac.uk/en/studentthesis/software-component-testing(14d22b70-809b-44e4-8240-12a5ead3fdd6).html.
Full textAbstract:
This portfolio comprises two projects linked by the theme of software component testing, which is also often referred to as module or unit testing. One project covers its standardisation, while the other considers the analysis and evaluation of the application of selected testing techniques to an existing avionics system. The evaluation is based on empirical data obtained from fault reports relating to the avionics system. The standardisation project is based on the development of the BC BSI Software Component Testing Standard and the BCS/BSI Glossary of terms used in software testing, which are both included in the portfolio. The papers included for this project consider both those issues concerned with the adopted development process and the resolution of technical matters concerning the definition of the testing techniques and their associated measures. The test effectiveness project documents a retrospective analysis of an operational avionics system to determine the relative effectiveness of several software component testing techniques. The methodology differs from that used in other test effectiveness experiments in that it considers every possible set of inputs that are required to satisfy a testing technique rather than arbitrarily chosen values from within this set. The three papers present the experimental methodology used, intermediate results from a failure analysis of the studied system, and the test effectiveness results for ten testing techniques, definitions for which were taken from the BCS BSI Software Component Testing Standard. The creation of the two standards has filled a gap in both the national and international software testing standards arenas. Their production required an in-depth knowledge of software component testing techniques, the identification and use of a development process, and the negotiation of the standardisation process at a national level. The knowledge gained during this process has been disseminated by the author in the papers included as part of this portfolio. The investigation of test effectiveness has introduced a new methodology for determining the test effectiveness of software component testing techniques by means of a retrospective analysis and so provided a new set of data that can be added to the body of empirical data on software component testing effectiveness.
39
Merkel, Robert Graham, and robert merkel@benambra org. "Analysis and enhancements of adaptive random testing." Swinburne University of Technology, 2005. http://adt.lib.swin.edu.au./public/adt-VSWT20050804.144747.
Full textAbstract:
Random testing is a standard software testing method. It is a popular method for reli-ability assessment, but its use for debug testing has been opposed by some authorities. Random testing does not use any information to guide test case selection, and so, it is argued, testing is less likely to be effective than other methods.
Based on the observation that failures often cluster in contiguous regions, Adaptive Random Testing (ART) is a more effective random testing method. While retaining random selection of test cases, selection is guided by the idea that tests should be widely spread throughout the input domain. A simple way to implement this concept, FSCS-ART, involves randomly generating a number of candidates, and choosing the candidate most widely spread from any already-executed test. This method has already shown to
be up to 50% more effective than random testing. This thesis examines a number of theoretical and practical issues related to ART.
Firstly, an theoretical examination of the scope of adaptive methods to improve testing
effectiveness is conducted. Our results show that the maximum improvement in failure detection effectiveness possible is only 50% - so ART performs close to this limit on many occasions. Secondly, the statistical validity of the previous empirical results is examined. A mathematical analysis of the sampling distribution of the various failure-detection effectiveness methods shows that the measure preferred in previous studies has a slightly unusual distribution known as the geometric distribution, and that that it and other measures are likely to show high variance, requiring very large sample sizes for accurate comparisons.
A potential limitation of current ART methods is the relatively high selection overhead. A number of methods to obtain lower overheads are proposed and evaluated, involving a less-strict randomness or wide-spreading criterion. Two methods use dynamic, as-needed partitioning to divide the input domain, spreading test cases throughout the partitions as required. Another involves using a class of numeric sequences called quasi-random sequences. Finally, a more efficient implementation of the existing FSCS-ART method is proposed using the mathematical structure known as the Voronoi diagram.
Finally, the use of ART on programs whose input is non-numeric is examined. While existing techniques can be used to generate random non-numeric candidates, a criterion for 'wide spread' is required to perform ART effectively. It is proposed to use the notion of category-partition as such a criterion.
40
Sekgweleo, Tefo Gordon. "A decision support system framework for testing and evaluating software in organisations." Thesis, Cape Peninsula University of Technology, 2018. http://hdl.handle.net/20.500.11838/2772.
Full textAbstract:
Thesis (DPhil (Informatics))--Cape Peninsula University of Technology, 2018.Increasingly, organisations in South African and across the world rely on software for various reasons, such as competitiveness and sustainability. The software are either developed in-house or purchased from the shelf. Irrespective of how the software was acquired, they do encounter challenges, from implementation to support, and use stages. The challenges sometimes hinder and are prohibitive to processes and activities that the software is intended to enable and support. Majority of the challenges that are encountered with software are attributed to the fact that they were not tested or appropriately tested before implementation. Some of the challenges has been costly to many organisations, particularly in South Africa. As a result, some organisations have been lacking in their efforts toward growth, competitiveness and sustainability. The challenges manifest from the fact that there are no testing tools and methods that can be easily customised for an organisation’s purposes. As a result, some organisations adopt more tools and methods for the same testing purposes, which has not solved the problem, as the challenges continue among South Africa organisations. Based on the challenges as stated above, this study was undertaken. The aim was to develop a decision support system framework, which can be used for software testing by any organisation, owing to its flexibility for customisation. The interpretivist and inductive approaches were employed. The qualitative methods and the case study design approach were applied. Three South African organisations, a private, public and small to medium enterprise (SME) were used as cases in this study. A set of criteria was used to select the organisations. The analysis of the data was guided by two sociotechnical theories, actor network theory (ANT) and diffusion of innovation (DOI). The theories were complementarily applied because of their different focuses. The actor network theory focuses on actors, which are both human and non-human, heterogeneity of networks, and the relationship between the actors within networks. This includes the interactions that happen at different moments as translated within the heterogeneous networks. Thus, ANT was employed to examine and gain better understanding of the factors that influence software testing in organisations. The DOI focuses on how new (fresh) ideas are diffused in an environment, with particular focus on innovation decision process, which constitute five stages: knowledge, persuasion, decision, implementation and confirmation. Findings from the data analysis of the three cases were further interpreted. Based on the interpretation, a decision support system framework was developed. The framework is intended to be of interest to software developers, software project managers and other stakeholders, most importantly, to provide guide to software testers in their tasks of testing software. Thus, this research is intended to be of interest and benefit to organisations and academic through its theoretical, practical and methodological contribution as detailed in the chapter seven (conclusion). In conclusion, even though this research is rigorous, comprehensive and holistic, there are room for future studies. I would like to propose that future research should be in the areas of measurement of software testing. Also, sociotechnical theories like structuration theory and technology acceptance model should be considered in the analysis of such studies.
41
Kahsai, Temesghen. "Property preserving development and testing for CSP-CASL." Thesis, Swansea University, 2009. https://cronfa.swan.ac.uk/Record/cronfa42217.
Full textAbstract:
This thesis describes a theoretical study and an industrial application in the area of formal systems development, verification and formal testing using the specification language CSP-CASL. The latter is a comprehensive specification language which allows to describe systems in a combined algebraic / process algebraic notation. To this end it integrates the process algebra CSP and the algebraic specification language CASL. In this thesis we propose various formal development notions for CSP-CASL capable of capturing informal vertical and horizontal software development which we typically find in industrial applications. We provide proof techniques for such development notions and verification methodologies to prove interesting properties of reactive systems. We also propose a theoretical framework for formal testing from CSP-CASL specifications. Here, we present a conformance relation between a physical system and a CSP-C ASL specification. In particular we study the relationship between CSP-CASL development notions and the implemented system. The proposed theoretical notions of formal system development, property verification and formal testing for CSP-CASL, have been successfully applied to two industrial application: an electronic payment system called EP2 and the starting system of the BR725 Rolls- Royce jet engine control software.
42
Hays, Christopher Thomas. "An algebraic axiom environment for software testing (axenvironment)." Diss., The University of Arizona, 1993. http://hdl.handle.net/10150/186399.
Full textAbstract:
This dissertation describes the design and implementation of an algebraic axiom support environment for software testing. Since absolute software correctness is undecidable, "approximate" correctness is as good as software engineering can hope to do. The approximately correct behavior of a software system with respect to a specification can only be demonstrated incrementally, beginning with the modules of a system and finishing with the external interface. Software module specification in the form of algebraic axioms provides a base from which we can be complete and concise in developing and testing the behavior of modules. Algebraic axioms can also be useful for a variety of software issues such as reusability, completeness and consistency of a requirements specification, and the definition of abstract and hierarchical data types. The primary focus of this dissertation is that algebraic axioms can provide a complete and consistent means to record a specification with which to test a software system's behavior at the module level. A major aim of this research has been to specify and develop sufficient support software to demonstrate the viability of this approach in actual software development, making design for testability a development parameter. This research focuses on the following issues: (1) The relationship between algebraic axioms and other formal methods for specifying software behavior. (2) Extensions needed to make the algebraic axiom method encompass testing. (3) What software support is necessary to make algebraic specifications, with our extensions, useful for real-world software development. Results indicate that using the formal method of algebraic specifications can have a positive impact on software development when adequate and realistic support software is introduced into the process. The approach results in additional initial labor for a software system, but is shown to be economical in terms of testing completeness, maintenance, and potential reuse.
43
Liu, Huai. "On even spread of test cases in adaptive random testing." Swinburne Research Bank, 2008. http://hdl.handle.net/1959.3/40129.
Full textAbstract:
Thesis (Ph.D) - Swinburne University of Technology, Faculty of Information & Communication Technologies, 2008.A thesis submitted for the degree of Doctor of Philosophy, Faculty of Information and Communication Technologies, Swinburne University of Technology, 2008. Typescript. Bibliography: p. 107-123.
44
Ho, Chun-fai Jeffrey. "Towards automatic oracles for the testing of mesh simplification software." Click to view the E-thesis via HKUTO, 2005. http://sunzi.lib.hku.hk/hkuto/record/B36393228.
Full text
45
Williams, Alan Webber. "Software component interaction testing: Coverage measurement and generation of configurations." Thesis, University of Ottawa (Canada), 2002. http://hdl.handle.net/10393/6387.
Full textAbstract:
Systems constructed from components, including distributed systems, consist of a number of elements that interact with each other. When a system is integrated, there may be undesired interactions among those components that cause system failures. There are two complementary problems in testing a software system. The first problem is to create a test suite, given a description of the expected behaviour of a system configuration. The second problem is to deal with a large number of distinct test configurations. We investigate the second problem in this thesis: the situation when there are various system parameters, each of which can take on a value from a discrete set. The trade-off that the system tester faces is the thoroughness of test configuration coverage, versus availability of limited resources. We introduce a coverage measure that can provide a basis for determining a set of configurations with "sufficient" coverage, or for evaluation of a set of test configurations that already exists. This thesis addresses the problem of testing interactions among components of a software system: the "interaction test coverage" problem. We formally define this problem, and give it a set-theoretic framework. This is done through the introduction of an "interaction element," which becomes the unit of test coverage. The problem is compared to, and distinguished from, the minimum set cover problem and the {0,1} integer programming problem. As a result, the status of the NP-completeness of this problem remains open. Methods from statistical experimental design are introduced, and applied to the problem of generating a set of configurations that achieve coverage of all pair-wise combinations of parameter values. We present a fast, deterministic algorithm to generate such a set of test configurations. The method is compared with other methods, and shown to produce fewer configurations in most situations. The number of configurations generated is logarithmic in the number of parameters, and polynomial in the number of values per parameter. As a result, the number of configurations is usually feasible in practice, and is a significant reduction from the number of possible configurations.
46
Hegazy, Wael A. "The requirements of testing a class of reusable software modules /." The Ohio State University, 1989. http://rave.ohiolink.edu/etdc/view?acc_num=osu1487668215806965.
Full text
47
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
48
Ho, Chun-fai Jeffrey, and 何晉輝. "Towards automatic oracles for the testing of mesh simplification software." Thesis, The University of Hong Kong (Pokfulam, Hong Kong), 2005. http://hub.hku.hk/bib/B36393228.
Full text
49
Lipkin, Ilya. "Testing Software Development Project Productivity Model." University of Toledo / OhioLINK, 2011. http://rave.ohiolink.edu/etdc/view?acc_num=toledo1321593577.
Full text
50
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