Relevant bibliographies by topics / Test case specifications

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Test case specifications'

Author: Grafiati
Published: 4 June 2021
Last updated: 1 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Test case specifications.'

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.

Journal articles on the topic "Test case specifications"

1

Denney, R. "Test-case generation from Prolog-based specifications." IEEE Software 8, no. 2 (1991): 49–57. http://dx.doi.org/10.1109/52.73749.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Chen, T. Y., and M. F. Lau. "Test case selection strategies based on Boolean specifications." Software Testing, Verification and Reliability 11, no. 3 (2001): 165–80. http://dx.doi.org/10.1002/stvr.221.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Hue, Chu Thi Minh, Duc-Hanh Dang, Nguyen Ngoc Binh, and Anh-Hoang Truong. "USLTG: Test Case Automatic Generation by Transforming Use Cases." International Journal of Software Engineering and Knowledge Engineering 29, no. 09 (2019): 1313–45. http://dx.doi.org/10.1142/s0218194019500414.

Full text
Abstract:
This paper proposes a transformation-based method to automatically generate functional test cases from use cases named USLTG (Use case Specification Language (USL)-based Test Generation). We first focus on developing a modeling language named Test Case Specification Language (TCSL) in order to express test cases. Test cases in TCSL can contain detailed information including test steps, test objects within steps, actions of test objects, and test data. Such information is often ignored in currently available test case specifications. We then aim to generate test cases in a TCSL model by a transformation from use cases that are represented by a USL. The USLTG transformation includes three main steps in generating (1) scenarios, (2) test data, and (3) a TCSL model. Within our transformation, the OCL solver is employed in order to build system snapshots as the part of test cases and to identify other test data. We applied our method to two case studies and evaluated our method by comparing it with other recent works.
APA, Harvard, Vancouver, ISO, and other styles
4

Liu, Shaoying, Wuwei Shen, and Shin Nakajima. "A formal approach to testing programs in practice." Computer Science and Information Systems 9, no. 4 (2012): 1469–91. http://dx.doi.org/10.2298/csis120301050l.

Full text
Abstract:
A program required to be tested in practice often has no available source code for some reason and how to adequately test such a program is still an open problem. In this paper, we describe a formal specification-based testing approach to tackle this challenge. The principal idea is first to formalize the informal requirements into formal operation specifications that take the interface scenarios of the program into account, and then utilize the specifications for test case generation and test result analysis. An example and case study of applying the approach to an IC card system is presented to illustrate its usage and analyze its performance.
APA, Harvard, Vancouver, ISO, and other styles
5

Tassone, A., A. D. Smirnov, and G. V. Tikhomirov. "Specifications for a coupled neutronics thermal-hydraulics SFR test case." Journal of Physics: Conference Series 781 (January 2017): 012047. http://dx.doi.org/10.1088/1742-6596/781/1/012047.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Mei, Lijun, Yan Cai, Changjiang Jia, Bo Jiang, and W. K. Chan. "Test Pair Selection for Test Case Prioritization in Regression Testing for WS-BPEL Programs." International Journal of Web Services Research 10, no. 1 (2013): 73–102. http://dx.doi.org/10.4018/jwsr.2013010104.

Full text
Abstract:
Many web services not only communicate through XML-based messages, but also may dynamically modify their behaviors by applying different interpretations on XML messages through updating the associated XML Schemas or XML-based interface specifications. Such artifacts are usually complex, allowing XML-based messages conforming to these specifications structurally complex. Testing should cost-effectively cover all scenarios. Test case prioritization is a dimension of regression testing that assures a program from unintended modifications by reordering the test cases within a test suite. However, many existing test case prioritization techniques for regression testing treat test cases of different complexity generically. In this paper, the authors exploit the insights on the structural similarity of XML-based artifacts between test cases in both static and dynamic dimensions, and propose a family of test case prioritization techniques that selects pairs of test case without replacement in turn. To the best of their knowledge, it is the first test case prioritization proposal that selects test case pairs for prioritization. The authors validate their techniques by a suite of benchmarks. The empirical results show that when incorporating all dimensions, some members of our technique family can be more effective than conventional coverage-based techniques.
APA, Harvard, Vancouver, ISO, and other styles
7

Aschenbrener, Tim, and Nam Tran. "Optimizing In-Place Density Through Improved Density Specifications." Transportation Research Record: Journal of the Transportation Research Board 2674, no. 3 (2020): 211–18. http://dx.doi.org/10.1177/0361198120908224.

Full text
Abstract:
The objective of this research was to (1) determine critical requirement(s) for in-place density based on a review of the literature; (2) analyze density test results shared by state highway agencies (SHAs) across the country to identify state specifications that minimize density results failing the identified critical requirement; and (3) document specification parameters that are important to achieve the critical requirement to share with SHAs that are interested in improving their density specifications. Based on prior research, the minimum density of an asphalt mixture should be 92.0% of the theoretical maximum specific gravity, as density below this critical level would have a detrimental effect on the long-term performance of the mix. Twelve SHAs identified thus far in this research have successfully adopted density specifications that minimize the number of test results below the 92.0% threshold. The statewide density results below the threshold in these states ranged from 3.1 to 11.0%. The density specifications in the 12 states play an important role in achieving these results as discussed in the paper. The case study presented in this paper showed that the density results below the identified threshold for a state in the Federal Highway Administration (FHWA) Demonstration Project decreased from 20.0% to only 5.7% with an improved density specification. There are likely more states with test results like those identified, and they will be added as they are identified in the future. In addition, more states will be added as they make improvements to their density specifications through this effort.
APA, Harvard, Vancouver, ISO, and other styles
8

Qian, Ling-li, and Yi-hai Chen. "Generating test case specifications of web service composition using model checking." Journal of Shanghai University (English Edition) 15, no. 5 (2011): 409–14. http://dx.doi.org/10.1007/s11741-011-0760-3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

CHEN, T. Y., P. L. POON, and T. H. TSE. "AN INTEGRATED CLASSIFICATION-TREE METHODOLOGY FOR TEST CASE GENERATION." International Journal of Software Engineering and Knowledge Engineering 10, no. 06 (2000): 647–79. http://dx.doi.org/10.1142/s0218194000000353.

Full text
Abstract:
This paper describes an integrated methodology for the construction of test cases from functional specifications using the classification-tree method. It is an integration of our extensions to the classification-hierarchy table, the classification tree construction algorithm, and the classification tree restructuring technique. Based on the methodology, a prototype system ADDICT, which stands for AutomateD test Data generation system using the Integrated Classification-Tree method, has been built.
APA, Harvard, Vancouver, ISO, and other styles
10

Jalila, A., D. Jeya Mala, and M. Eswaran. "Functional Testing Using OCL Predicates to Improve Software Quality." International Journal of Systems and Service-Oriented Engineering 5, no. 2 (2015): 56–72. http://dx.doi.org/10.4018/ijssoe.2015040104.

Full text
Abstract:
Formal specification-based testing is one of the major criterions to detect faults in the requirement specification or design of a system. However, due to the non-availability of implementation details, test case generation from formal specifications become a challenging task. This research work has proposed an automated fault-based testing framework to test the specification of a system written in OCL (Object Constraint Language). Accordingly, the possible faults in OCL specification of a system have been anticipated by mutating its method based on predicate-based fault classes. Then, test cases are generated by applying Chaotic Simulated Annealing (CSA) algorithm. In this paper, a novel OCL predicate based fitness function is defined to evaluate the generated test data. The experiment results indicate that the OCL specification based testing adopting CSA form an excellent combination for performing functional testing at the earliest to improve software quality.
APA, Harvard, Vancouver, ISO, and other styles

Dissertations / Theses on the topic "Test case specifications"

1

Salman, Alzahraa. "Test Case Generation from Specifications Using Natural Language Processing." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-281352.

Full text
Abstract:
Software testing plays a fundamental role in software engineering as it ensures the quality of a software system. However, one of the major challenges of software testing is its costs since it is a time and resource-consuming process which according to academia and industry can take up to 50% of the total development cost. Today, one of the most common ways of generating testcases is through manual labor by analyzing specification documents to produce test scripts, which tends to be an expensive and error prone process. Therefore, optimizing software testing by automating the test case generation process can result in time and cost reductions and also lead to better quality of the end product. Currently, most of the state-of-the-art solutions for automatic test case generation require the usage of formal specifications. Such formal specifications are not always available during the testing process and if available, they require expert knowledge for writing and understanding them. One artifact that is often available in the testing domain is test case specifications written in natural language. In this thesis, an approach for generating integration test cases from natural language test case specifications is designed, applied and, evaluated. Machine learning and natural language processing techniques are used to implement the approach. The proposed approach is conducted and evaluated on an industrial testing project at Ericsson AB in Sweden. Additionally, the approach has been implemented as a tool with a graphical user interface for aiding testers in the process of test case generation. The approach involves performing natural language processing techniques for parsing and analyzing the test case specifications to generate feature vectors that are later mapped to label vectors containing existing C# test scripts filenames. The feature and label vectors are used as input and output, respectively, in a multi-label text classification process. The approach managed to produce test scripts for all test case specifications and obtained a best F1 score of 89% when using LinearSVC as the classifier and performing data augmentation on the training set.<br>Programvarutestning spelar en grundläggande roll i programvaruutveckling då den säkerställer kvaliteten på ett programvarusystem. En av de största utmaningarna med programvarutestning är dess kostnader eftersom den är en tids och resurskrävande process som enligt akademin och industrin kan ta upp till 50% av den totala utvecklingskostnaden. Ett av de vanligaste sätten att generera testfall idag är med manuellt arbete genom analys av testfallsspecifikationer, vilket tenderar att vara en dyr och felbenägen process. Därför kan optimering av programvarutestning genom automatisering av testfallsgenereringsprocessen resultera i tids- och kostnadsminimeringar och även leda till bättre kvalitet på slutprodukten. Nuförtiden kräver de flesta toppmoderna lösningarna för automatisk testfallsgenerering användning av formella specifikationer. Sådana specifikationer är inte alltid tillgängliga under testprocessen och om de är tillgängliga, så krävs det expertkunskap för att skriva och förstå dem. En artefakt som ofta finns i testdomänen är testfallspecifikationer skrivna på naturligt språk. I denna rapport utformas, tillämpas och utvärderas en metod för generering av integrationstestfall från testfallsspecifikationer skrivna på naturligt språk. Maskininlärnings- och naturlig språkbehandlingstekniker används för implementationen av metoden. Den föreslagna metoden genomförs och utvärderas vid ett industriellt testprojekt hos Ericsson AB i Sverige. Dessutom har metoden implementerats som ett verktyg med ett grafiskt användargränssnitt för att hjälpa testare i testfallsgenereringsprocessen. Metoden fungerar genom att utföra naturlig språkbehandlingstekniker på testfallsspecifikationer för att generera egenskapsvektorer som senare mappas till etikettsvektorer som innehåller befintliga C# testskriptfilnamn. Engenskaps och etikettsvektorerna används sedan som indata och utdata, respektive, för textklassificeringsprocessen. Metoden lyckades producera testskript för allatestfallsspecifikationer och fick en bästa F1 poäng på 89% när LinearSVC användes för klassificeringen och datautökning var utförd på träningsdatat.
APA, Harvard, Vancouver, ISO, and other styles
2

HORI, Érica Aguiar Andrade. "ucsCNL A controlled natural language for use case specifications." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/2393.

Full text
Abstract:
Made available in DSpace on 2014-06-12T15:57:41Z (GMT). No. of bitstreams: 2 arquivo3220_1.pdf: 1307302 bytes, checksum: 42435c33fd14be36778e3c202d24fd2d (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2010<br>A maioria das empresas utiliza a linguagem natural livre para documentar software, desde os seus requisitos, até os casos de uso e testes usados para verificar o produto final. Visto que as fases de análise, projeto, implementação e teste do sistema dependem essencialmente dessa documentação, é preciso assegurar inicialmente a qualidade desses textos. Contudo, textos escritos em linguagem natural nem sempre são precisos, devido ao fenômeno da ambigüidade (léxica e estrutural), podendo dar margem a diferentes interpretações. Uma alternativa para se minimizar esse problema é o uso de uma Linguagem Natural Controlada - um subconjunto de alguma língua natural, que usa um vocabulário restrito a um domínio particular, e regras gramaticais que guiam a construção de sentenças com redução de ambigüidade semântica visando padronização e precisão dos textos. Este trabalho, na área de Teste de Software, apresenta a ucsCNL (Use Case Specification CNL), uma Linguagem Natural Controlada para escrever especificações de casos de uso no domínio de dispositivos móveis. A ucsCNL foi integrada à TaRGeT (Test and Requirements Generation Tool), uma ferramenta para geração automática de casos de teste funcionais baseados em cenários de casos de uso escritos em Inglês. A ucsCNL provê um ambiente para geração de casos de teste mais claros, com ambigüidade reduzida, influindo diretamente na qualidade dos testes e na produtividade dos testadores. A ucsCNL já está em uso e tem alcançado resultados satisfatórios
APA, Harvard, Vancouver, ISO, and other styles
3

Juhnke, Katharina [Verfasser]. "Improving the quality of automotive test case specifications / Katharina Juhnke." Ulm : Universität Ulm, 2021. http://d-nb.info/1228439095/34.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Alhroob, Aysh M. "Software test case generation from system models and specification. Use of the UML diagrams and High Level Petri Nets models for developing software test cases." Thesis, University of Bradford, 2010. http://hdl.handle.net/10454/5453.

Full text
Abstract:
The main part in the testing of the software is in the generation of test cases suitable for software system testing. The quality of the test cases plays a major role in reducing the time of software system testing and subsequently reduces the cost. The test cases, in model de- sign stages, are used to detect the faults before implementing it. This early detection offers more flexibility to correct the faults in early stages rather than latter ones. The best of these tests, that covers both static and dynamic software system model specifications, is one of the chal- lenges in the software testing. The static and dynamic specifications could be represented efficiently by Unified Modelling Language (UML) class diagram and sequence diagram. The work in this thesis shows that High Level Petri Nets (HLPN) can represent both of them in one model. Using a proper model in the representation of the software specifications is essential to generate proper test cases. The research presented in this thesis introduces novel and automated test cases generation techniques that can be used within a software sys- tem design testing. Furthermore, this research introduces e cient au- tomated technique to generate a formal software system model (HLPN) from semi-formal models (UML diagrams). The work in this thesis con- sists of four stages: (1) generating test cases from class diagram and Object Constraint Language (OCL) that can be used for testing the software system static specifications (the structure) (2) combining class diagram, sequence diagram and OCL to generate test cases able to cover both static and dynamic specifications (3) generating HLPN automat- ically from single or multi sequence diagrams (4) generating test cases from HLPN. The test cases that are generated in this work covered the structural and behavioural of the software system model. In first two phases of this work, the class diagram and sequence diagram are decomposed to nodes (edges) which are linked by Classes Hierarchy Table (CHu) and Edges Relationships Table (ERT) as well. The linking process based on the classes and edges relationships. The relationships of the software system components have been controlled by consistency checking technique, and the detection of these relationships has been automated. The test cases were generated based on these interrelationships. These test cases have been reduced to a minimum number and the best test case has been selected in every stage. The degree of similarity between test cases is used to ignore the similar test cases in order to avoid the redundancy. The transformation from UML sequence diagram (s) to HLPN facilitates the simpli cation of software system model and introduces formal model rather than semi-formal one. After decomposing the sequence diagram to Combined Fragments, the proposed technique converts each Combined Fragment to the corresponding block in HLPN. These blocks are con- nected together in Combined Fragments Net (CFN) to construct the the HLPN model. The experimentations with the proposed techniques show the effectiveness of these techniques in covering most of the software system specifications.
APA, Harvard, Vancouver, ISO, and other styles
5

Alhroob, Aysh Menoer. "Software test case generation from system models and specification : use of the UML diagrams and high level Petri nets models for developing software test cases." Thesis, University of Bradford, 2010. http://hdl.handle.net/10454/5453.

Full text
Abstract:
The main part in the testing of the software is in the generation of test cases suitable for software system testing. The quality of the test cases plays a major role in reducing the time of software system testing and subsequently reduces the cost. The test cases, in model de- sign stages, are used to detect the faults before implementing it. This early detection offers more flexibility to correct the faults in early stages rather than latter ones. The best of these tests, that covers both static and dynamic software system model specifications, is one of the chal- lenges in the software testing. The static and dynamic specifications could be represented efficiently by Unified Modelling Language (UML) class diagram and sequence diagram. The work in this thesis shows that High Level Petri Nets (HLPN) can represent both of them in one model. Using a proper model in the representation of the software specifications is essential to generate proper test cases. The research presented in this thesis introduces novel and automated test cases generation techniques that can be used within a software sys- tem design testing. Furthermore, this research introduces e cient au- tomated technique to generate a formal software system model (HLPN) from semi-formal models (UML diagrams). The work in this thesis con- sists of four stages: (1) generating test cases from class diagram and Object Constraint Language (OCL) that can be used for testing the software system static specifications (the structure) (2) combining class diagram, sequence diagram and OCL to generate test cases able to cover both static and dynamic specifications (3) generating HLPN automat- ically from single or multi sequence diagrams (4) generating test cases from HLPN. The test cases that are generated in this work covered the structural and behavioural of the software system model. In first two phases of this work, the class diagram and sequence diagram are decomposed to nodes (edges) which are linked by Classes Hierarchy Table (CHu) and Edges Relationships Table (ERT) as well. The linking process based on the classes and edges relationships. The relationships of the software system components have been controlled by consistency checking technique, and the detection of these relationships has been automated. The test cases were generated based on these interrelationships. These test cases have been reduced to a minimum number and the best test case has been selected in every stage. The degree of similarity between test cases is used to ignore the similar test cases in order to avoid the redundancy. The transformation from UML sequence diagram (s) to HLPN facilitates the simpli cation of software system model and introduces formal model rather than semi-formal one. After decomposing the sequence diagram to Combined Fragments, the proposed technique converts each Combined Fragment to the corresponding block in HLPN. These blocks are con- nected together in Combined Fragments Net (CFN) to construct the the HLPN model. The experimentations with the proposed techniques show the effectiveness of these techniques in covering most of the software system specifications.
APA, Harvard, Vancouver, ISO, and other styles
6

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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
7

Grabowski, Jens. "Test case generation and test case specification with message sequence charts /." [S.l.] : [s.n.], 1994. http://www.ub.unibe.ch/content/bibliotheken_sammlungen/sondersammlungen/dissen_bestellformular/index_ger.html.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Meudec, Christophe. "Automatic generation of software test cases from formal specifications." Thesis, Queen's University Belfast, 1998. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.263505.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Sinha, Avik. "Domain specific test case generation using higher ordered typed languages for specification." College Park, Md. : University of Maryland, 2005. http://hdl.handle.net/1903/2406.

Full text
Abstract:
Thesis (Ph. D.) -- University of Maryland, College Park, 2005.<br>Thesis research directed by: Reliability Engineering Program. Title from t.p. of PDF. Includes bibliographical references. Published by UMI Dissertation Services, Ann Arbor, Mich. Also available in paper.
APA, Harvard, Vancouver, ISO, and other styles
10

OLIVEIRA, NETO Francisco Gomes de. "Investigation of similarity-based test case selection for specification-based regression testing." Universidade Federal de Campina Grande, 2014. http://dspace.sti.ufcg.edu.br:8080/jspui/handle/riufcg/360.

Full text
Abstract:
Submitted by Johnny Rodrigues (johnnyrodrigues@ufcg.edu.br) on 2018-04-10T20:00:05Z No. of bitstreams: 1 FRANCISCO GOMES DE OLIVEIRA NETO - TESE PPGCC 2014..pdf: 5163454 bytes, checksum: 228c1fc4f2dc9aad01698011238cfde1 (MD5)<br>Made available in DSpace on 2018-04-10T20:00:05Z (GMT). No. of bitstreams: 1 FRANCISCO GOMES DE OLIVEIRA NETO - TESE PPGCC 2014..pdf: 5163454 bytes, checksum: 228c1fc4f2dc9aad01698011238cfde1 (MD5) Previous issue date: 2014-07-30<br>uring software maintenance, several modifications can be performed in a specification model in order to satisfy new requirements. Perform regression testing on modified software is known to be a costly and laborious task. Test case selection, test case prioritization, test suite minimisation,among other methods,aim to reduce these costs by selecting or prioritizing a subset of test cases so that less time, effort and thus money are involved in performing regression testing. In this doctorate research, we explore the general problem of automatically selecting test cases in a model-based testing (MBT) process where specification models were modified. Our technique, named Similarity Approach for Regression Testing (SART), selects subset of test cases traversing modified regions of a software system’s specification model. That strategy relies on similarity-based test case selection where similarities between test cases from different software versions are analysed to identify modified elements in a model. In addition, we propose an evaluation approach named Search Based Model Generation for Technology Evaluation (SBMTE) that is based on stochastic model generation and search-based techniques to generate large samples of realistic models to allow experiments with model-based techniques. Based on SBMTE,researchers are able to develop model generator tools to create a space of models based on statistics from real industrial models, and eventually generate samples from that space in order to perform experiments. Here we developed a generator to create instances of Annotated Labelled Transitions Systems (ALTS), to be used as input for our MBT process and then perform an experiment with SART.In this experiment, we were able to conclude that SART’s percentage of test suite size reduction is robust and able to select a sub set with an average of 92% less test cases, while ensuring coverage of all model modification and revealing defects linked to model modifications. Both SART and our experiment are executable through the LTS-BT tool, enabling researchers to use our selections trategy andr eproduce our experiment.<br>During software maintenance, several modifications can be performed in a specification model in order to satisfy new requirements. Perform regression testing on modified software is known to be a costly and laborious task. Test case selection, test case prioritization, test suite minimisation,among other methods,aim to reduce these costs by selecting or prioritizing a subset of test cases so that less time, effort and thus money are involved in performing regression testing. In this doctorate research, we explore the general problem of automatically selecting test cases in a model-based testing (MBT) process where specification models were modified. Our technique, named Similarity Approach for Regression Testing (SART), selects subset of test cases traversing modified regions of a software system’s specification model. That strategy relies on similarity-based test case selection where similarities between test cases from different software versions are analysed to identify modified elements in a model. In addition, we propose an evaluation approach named Search Based Model Generation for Technology Evaluation (SBMTE) that is based on stochastic model generation and search-based techniques to generate large samples of realistic models to allow experiments with model-based techniques. Based on SBMTE,researchers are able to develop model generator tools to create a space of models based on statistics from real industrial models, and eventually generate samples from that space in order to perform experiments. Here we developed a generator to create instances of Annotated Labelled Transitions Systems (ALTS), to be used as input for our MBT process and then perform an experiment with SART.In this experiment, we were able to conclude that SART’s percentage of test suite size reduction is robust and able to select a sub set with an average of 92% less test cases, while ensuring coverage of all model modification and revealing defects linked to model modifications. Both SART and our experiment are executable through the LTS-BT tool, enabling researchers to use our selections trategy andr eproduce our experiment.
APA, Harvard, Vancouver, ISO, and other styles

Books on the topic "Test case specifications"

1

Hodgkinson, David, and Alan Herbert. Specification of a Test Problem for HYDROCOIN Level 2 Case 1: Thermal Convection and Conduction Around a Field Heat Transfer Experiment. AEA Technology Plc, 1985.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Hodgkinson, David, and John Barker. Specification of a Test Problem for HYDROCOIN Level 1 Case 1: Transient Flow from a Borehole in a Fractured Permeable Medium. AEA Technology Plc, 1985.

Find full text
APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "Test case specifications"

1

Grieskamp, Wolfgang, Lev Nachmanson, Nikolai Tillmann, and Margus Veanes. "Test Case Generation from AsmL Specifications." In Abstract State Machines 2003. Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/3-540-36498-6_27.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Burguillo-Rial, Juan C., Manuel J. Fernández-Iglesias, Francisco J. González-Castaño, and Martín Llamas-Nistal. "Heuristic-Driven Test Case Selection from Formal Specifications. A Case Study." In FME 2002:Formal Methods—Getting IT Right. Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/3-540-45614-7_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Avinash Gupta, Anshu Gupta, and Dharmender Singh Kushwaha. "Test Case Reduction Using Decision Table for Requirements Specifications." In Proceedings of the International Congress on Information and Communication Technology. Springer Singapore, 2016. http://dx.doi.org/10.1007/978-981-10-0755-2_44.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Helke, Steffen, Thomas Neustupny, and Thomas Santen. "Automating test case generation from Z specifications with Isabelle." In Lecture Notes in Computer Science. Springer Berlin Heidelberg, 1997. http://dx.doi.org/10.1007/bfb0027283.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Goldstein, Harrison, John Hughes, Leonidas Lampropoulos, and Benjamin C. Pierce. "Do Judge a Test by its Cover." In Programming Languages and Systems. Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-72019-3_10.

Full text
Abstract:
AbstractProperty-based testing uses randomly generated inputs to validate high-level program specifications. It can be shockingly effective at finding bugs, but it often requires generating a very large number of inputs to do so. In this paper, we apply ideas from combinatorial testing, a powerful and widely studied testing methodology, to modify the distributions of our random generators so as to find bugs with fewer tests. The key concept is combinatorial coverage, which measures the degree to which a given set of tests exercises every possible choice of values for every small combination of input features.In its “classical” form, combinatorial coverage only applies to programs whose inputs have a very particular shape—essentially, a Cartesian product of finite sets. We generalize combinatorial coverage to the richer world of algebraic data types by formalizing a class of sparse test descriptions based on regular tree expressions. This new definition of coverage inspires a novel combinatorial thinning algorithm for improving the coverage of random test generators, requiring many fewer tests to catch bugs. We evaluate this algorithm on two case studies, a typed evaluator for System F terms and a Haskell compiler, showing significant improvements in both.
APA, Harvard, Vancouver, ISO, and other styles
6

Sottas, Gabriel, and Inge L. Ryhming. "Test Cases Specifications." In 3D-Computation of Incompressible Internal Flows. Vieweg+Teubner Verlag, 1993. http://dx.doi.org/10.1007/978-3-322-89452-6_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Capellmann, Carla, and Heinz Dibold. "Petri Net based specifications of services in an Intelligent Network-Experiences gained from a test case application." In Application and Theory of Petri Nets 1993. Springer Berlin Heidelberg, 1993. http://dx.doi.org/10.1007/3-540-56863-8_66.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Hirsch, Ch, and Erbing Shang. "Specification of Test Case TC3." In Notes on Numerical Fluid Mechanics (NNFM). Vieweg+Teubner Verlag, 1998. http://dx.doi.org/10.1007/978-3-322-89859-3_19.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Venkatesh, R., Ulka Shrotri, Amey Zare, and Supriya Agrawal. "On Generating Test Cases from EDT Specifications." In Communications in Computer and Information Science. Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-30243-0_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Viswanath, J., M. Parthiban, J. Thangakumar, and M. Roberts Masillamani. "Specification Based Test Case Generation Using Classification Tree Method." In Computer Networks and Information Technologies. Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-19542-6_48.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Test case specifications"

1

Sinnott, R. "Architecting specifications for test case generation." In 1st IEEE International Conference Software Engineering and Formal Methods. SEFM'03. IEEE, 2003. http://dx.doi.org/10.1109/sefm.2003.1236204.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Juhnke, Katharina, Matthias Tichy, and Frank Houdek. "Challenges with automotive test case specifications." In ICSE '18: 40th International Conference on Software Engineering. ACM, 2018. http://dx.doi.org/10.1145/3183440.3195070.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Mori, Ryusei, and Masaki Nakamura. "Automated Test Case Generation from OTS/CafeOBJ Specifications by Specification Translation." In 2017 IEEE International Conference on Software Testing, Verification and Validation: Workshops (ICSTW). IEEE, 2017. http://dx.doi.org/10.1109/icstw.2017.78.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Bloem, Roderick, Stefan Galler, Barbara Jobstmann, Nir Piterman, Amir Pnueli, and Martin Weiglhofer. "Automatic Hardware Synthesis from Specifications: A Case Study." In Design, Automation & Test in Europe Conference. IEEE, 2007. http://dx.doi.org/10.1109/date.2007.364456.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Wang, Chunhui, Fabrizio Pastore, Arda Goknil, Lionel Briand, and Zohaib Iqbal. "Automatic generation of system test cases from use case specifications." In ISSTA '15: International Symposium on Software Testing and Analysis. ACM, 2015. http://dx.doi.org/10.1145/2771783.2771812.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

VASILACHE, SIMONA. "DEPENDENCY DIAGRAMS: FROM REQUIREMENTS SPECIFICATIONS TO TEST CASE GENERATION." In World Congress on Engineering (WCE 2016) & World Congress on Engineering and Computer Science (WCECS 2016). WORLD SCIENTIFIC, 2017. http://dx.doi.org/10.1142/9789813230774_0033.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Juhnke, Katharina, Matthias Tichy, and Frank Houdek. "Challenges Concerning Test Case Specifications in Automotive Software Testing." In 2018 44th Euromicro Conference on Software Engineering and Advanced Applications (SEAA). IEEE, 2018. http://dx.doi.org/10.1109/seaa.2018.00015.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Wang, Chunhui, Fabrizio Pastore, Arda Goknil, Lionel C. Briand, and Zohaib Iqbal. "UMTG: a toolset to automatically generate system test cases from use case specifications." In ESEC/FSE'15: Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering. ACM, 2015. http://dx.doi.org/10.1145/2786805.2803187.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Aoyama, Yusuke, Takeru Kuroiwa, and Noriyuki Kushiro. "Executable Test Case Generation from Specifications Written in Natural Language and Test Execution Environment." In 2021 IEEE 18th Annual Consumer Communications & Networking Conference (CCNC). IEEE, 2021. http://dx.doi.org/10.1109/ccnc49032.2021.9369549.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Carvalho, Gustavo, Diogo Falcão, Flávia Barros, et al. "Test case generation from natural language requirements based on SCR specifications." In the 28th Annual ACM Symposium. ACM Press, 2013. http://dx.doi.org/10.1145/2480362.2480591.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Test case specifications"

1

Montgomery, Doug, Mark Carson, Timothy Winters, Michayla Newcombe, and Timothy Carlin. USGv6 Profile. National Institute of Standards and Technology, 2020. http://dx.doi.org/10.6028/nist.sp.500-267br1.

Full text
Abstract:
This profile establishes a basic taxonomy of IPv6 capabilities, defined in terms of IETF specifications, resulting in specific capability labels for common network functions and usage scenarios. The profile maps each such labeled capability to one or more specific technical specifications, or parts of specifications. Each labeled capability adopts by reference the normative requirements of the cited specifications. In rare cases the profile may augment or modify the normative requirements of a base specification. The defined capability labels effectively form a vocabulary for expressing IPv6 requirements for, and documenting the IPv6 capabilities of, specific products. It is expected that this profile, when combined with the USGv6 Test Program, can facilitate the efficient adoption of IPv6 technologies in Federal information systems.
APA, Harvard, Vancouver, ISO, and other styles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography