CSECUTA
The Testing Project
CSE 4321 Motivation
· Provides an opportunity to practice the basic concepts, principles, and techniques covered in this course
. Specifically, you will apply control flow testing to a program of moderate size
- Printtokens.java: a Java class that implements a string tokenizer (available in Canvas).
- about 500 lines of code with seeded faults
CSECUTA
- Both members will receive the same grading. Input and Output
· Input
- Location of a file (i.e., input to the main() method) that contains the tokens to be classified
- If a location is not given, the user is expected to type the tokens to be classified on the console.
· Output
- Type of each token, one per line
CSE 4321, Jeff Lei, UTA
CSECUTA
Type of Tokens
· Keyword: and, or, if, xor, lambda, =>
. Special Symbol: "(", ")", "[", "]", "" ,"", '," (Iparen, rparen, lsquare, rsquare, quote, bquote, comma)
· Identifier: begins with a letter and contains only letters and digits, e.g., a, aa, a1, a2.
· Number Constant: e.g., 123, 1, 321
· String Constant: e.g., "asd", "123"
· Character Constant: e.g., #a, #b, #c, #d
. Comment: Anything starts with ";"
CSE 4321, Jeff Lei, UTA
CSECUTA
•
Error: Everything else
Example
test.txt
1 and` and 2 j
Input:
3 112A
Arguments: C Main (x)= Arguments
JRE Deper
Program arguments:
"./test.txt"
CSE 4321, Jeff Lei, UTA
CSECUTA
Problems @ Javadoc
Declaration
Console
X
Printtokens2 [Java Application] /Library/Java/JavaVirtualMachines keyword , "and". bquote. keyword, "and". identifier,"j".
Output:
error, "112A".
Major Steps
Create the Control Flow Graph (CFG) for each method •
- The code in the catch clauses can be skipped, i.e., these clauses do not need to be represented in the CFG
. Unit Testing: For each method other than the main method, select a set of test paths to achieve edge coverage, i.e., cover all the edges in the CFG of the method
CSE 4321, Jeff Lei, UTA
CSECUTA
• Program Testing: For the main method, select a set of test paths to achieve edge coverage for the entire program, i.e., cover all the edges in all the CFGs.
•
Generate test cases, including test data and expected output, for each test path
- If a test path you selected in the previous step is infeasible, a new test path needs to be selected
. Use JUnit to implement and execute the generated test cases.
· Provide edge coverage reports for tests executed.
- One report for the unit tests of individual methods, and one report for the program-level tests of the main method
Deliverables
. Due date (FIRM): July 3 (midnight, last day of class)
CSE 4321, Jeff Lei, UTA
CSECUTA
. 20%: CFGs along with the corresponding source code, and the basic block table that identifies each basic block
. 30%: Test cases, including each test path, the corresponding test data to execute the test path, and the expected output
. 25%: JUnit source code
· 5%: Code coverage reports . 10%: Faults detected and corrections
· 5%: Summary and discussion.
. 5%: A ReadMe file that explains how to execute your JUnit code
CSE 4321, Jeff Lei, UTA
CSECUTA
Must-Have Files
. Your project should be submitted in GitHub Classroom
· Must contain these but not limited to these files.
- CFG.pdf
- Test Cases.pdf
- Source Code
- Code Coverage Reports.zip
- Faults and Corrections.pdf
- Summary and Discussion.pdf
- ReadMe.txt
· Typed reports are strongly recommended; if you choose to handwrite and scan the reports, it is your responsibility to ensure legibility.
CSE 4321, Jeff Lei, UTA
CSECUTA
Evaluation
· Faults detected and code coverage are not the main focus of our evaluation.
. If you follow the approach correctly, you could expect to detect at least 10 bugs.
. Focus on the "approach", instead of the "faults"
Recommendations
. IDE: Eclipse; Code Coverage: JaCoCo/EclEmma
CSE 4321, Jeff Lei, UTA
CSECUTA
- Refer to the video titled "Get started with the project" in Canvas
- Other tools could be used, but you may be asked to give a demo for the TA
. When you find a fault, fix it before you continue. This could help to discover more faults.
. If fixing a fault alters the control flow, you are not required to construct a new CFG.
. Do not try to use CFG generation tools for Java programs; otherwise, you will receive no points on the project.
- Many tools generate CFGs based on byte code, not source code. The output could be incorrect w.r.t the project specification.
CSE 4321, Jeff Lei, UTA
