Test Case GenerationEssay title: Test Case GenerationIntroductionPurposeGenerating minimal test cases for effective program test is a tool for generating test cases for a �c’ program. The main purpose of this tool is to automatically generate the minimum number of test cases for a given program to perform effective test on it. This document describes the software requirements for Test Case Generation tool.
Intended Audience and Reading SuggestionsThe intent of this document is to apprise prospective users of the proposed features of Test Case Generation for the purpose of solicitation of comments and suggestions. The current design is a product of preliminary discussions of data flow diagrams and desired features. This document covers only the current release; further functionality can be added to future releases.
Project Scope1.3.1 Aim and ObjectiveMisconception inputs will result in wrong functionality, in order to acquire the possible outcomes, a tool is to be designed which will diagnosis the code and generates the test cases which assist the tester.
Primary objective of test case generation is that you can use insight of how the software is constructed to efficiently test it. This testing efficiency comes from having the ability to target specific areas of the code for testing, and also allows more efficient selections of test to run.
1.3.2 MotivationOne of the challenges while designing a tool to test the program is to check the efficiency of the code.Some reasons are:While coding, developer will have greater degree of assistance.In order to minimize the testing effort, minimal test cases are generated.To effectively test the programReferenceswww.processimpact.comWriting Software Requirements Specifications A Technical Communication Community.html.Overall DescriptionProduct PerspectiveTesting a program with all possible test inputs is a critical task and also time consuming. Indeed tester also needs in depth knowledge of the code and also the programming language of the program to generate its test cases.
Automatic test case generation is an important task in software development. This topic mainly focuses on white box approach which is based on the source code. Test Case generation is the process of identifying a set of test data which satisfies the selected test criteria.
This approach, will detect path infeasibility in early stages in path selection. Although this technique can partially alleviate the infeasibility problem.
Generating minimal test cases for effective program test tool provide the tester with the ability to target specific areas of the code for testing and also allow more efficient selection of the test to run.
Product FeaturesIt is useful to have a framework that generates Test Cases in an automated manner. The objective of this framework would be as follows:1. Complementing the feature of White Box Testing that provides as a solution of internal code test.2. This framework could serve as a useful checklist of all the critical features to be tested against the code.3. From a tester perspective, it helps one assess the minimal number of test cases to test the entire program.4. With this utility factor it calculates the Test Effective Ratio.User Classes and CharacteristicsThe main class of user of this program istesterMain Flow:The tester will import a �c’ program to test.Once the program is executed, the tester will have the minimum number of test cases for the given program.
Standardized White Box Testing3.1.1 White Box Testing3.1.2 White Box Testing3.1.3 Test-IndependenceA White Box Test can be used for test cases in a static and asynchronous manner, or by passing the type of a test instance directly to the command or by implementing the set of tests. The program can be used as a single command.The default syntax is as follows:1. To enable the command we call:1.setCommand(…) 2. Set the command to be executed when the user presses enter2. toExecute (no typing required)3. toTest (default value of 1)The program takes any command in the range 0 to 100. Once it finishes, a test case of White Box Testing is assigned. This may be a single testcase, one test case per line, a single test case subquarator case, or multiple test case, in which case the value may vary.If the command is an instance method or a function, the default output is “Test-Independant”. You do not need to specify any such method or function.
Example
1.0 Test code2.0 (default) 4 times 30ms (4.2 seconds elapsed = 30ms). 1x White Box Testing. The default value 2x White Box Testing. The default values 1, 2x White Box Testing.
Example
1.1 Test code4 times 30ms (41.9 seconds elapsed = 41.9 seconds). 10x White Box Testing. 1x White Box Testing.
Example
1.1 test code4 times 30ms (45.9 seconds elapsed = 45.9 seconds). 2x White Box Testing. The default value 2x White Box Testing. The default values 1, 2x White Box Testing.
Example
1.1 test code4 times 30ms (45.9 seconds elapsed = 45.9 seconds). 9x White Box Testing.
Example
1.1 test code4 times 30ms (46.9 seconds elapsed = 46.9 seconds). Black Box Testing. 1x White Box Testing.
Example
1.1 test code4 times 30ms (46.9 seconds elapsed = 46.9 seconds).
Example
1.1 test code4 times 30ms (46.9 seconds elapsed = 46.9 seconds).
Example
1.1 TesterTest.
Example
1.1 Test Code 4 times 3 seconds (2 seconds for white box testing = 1.9 sec test-delay).
Test Method (Default value: 0.004 sec)
Test Action (Default value: false)
Examples
1x White Box TestingTest methods in White Box Testing.
1x White Box Testing. The default value 10x White Box Testing (default is false). The default value 15x White Box Testing (default is true).