Explain in XXXX XXXXXXX here how unit XXXX XXXXXX XX XXXXXXXXXX. Include in XXXX discussion answers to the following questions: What XXX the goals and XXXXXXXXXX XXX unit test? XXXX XXX XXX key criteria for XXXX XXXX XX be XXXXXXXX – how do you know you XXX XXXX unit testing? What kind XX testing XX XXXX XXXX (XXXXX-box, XXXXX-XXX, XXXXXXXX, etc.) XXX XXXX XXXX to explain XXXX that XXXX XX testing does? XXXX XXX code coverage XXX data XXXXXXXX and how they XXXXXX XX XXXX XXXX?XXXX are test characteristics XXXX you learned XXXXX in week 3 XX XXXX XXXXXX? XXXX them XXX XXXXXXX in your own XXXXX.Who normally XXXXXX and executes unit test? How do you determine that a XXXXXX XXX been XXXXX in UT? As XXXXXXX XXX found XXXXXX XXXX test XXX XXXX XXXXX them? XXXX happens XXXX after XXXXXX is fixed in the XXXX XXXXX XXXXXX? Be as complete and thorough in XXXX discussion XXXXXXXXXXXXX your XXXXXXXXXXXXX XX XXXX XXXX.
XXXXX and objective of unit test:
XXXX XXXX XXX done XX check XXXXXXX a XXXXXXXXXX module or XXXX of code XX XXXXXXX fine. It eliminates all logical XXX XXXXXXX XXXXXX. It XX particularly useful for testing XXXX at XXX XXXX XXXXX module to XXXXXX any errors XXX’t XXXXXXXXX up XX the modules up in the hierarchy.
How XX you know you XXX done XXXXXXX? :
When you XXXX XXXXXXXX XXX XXXXXXXX inputs that a XXXXXX can XXXX and the XXXXXX shows XXX XXXXXXXX XXXXXXX. XXXXX an important XXXXXX XX all possible inputs is XXXXX to save XXXX XXX XXX XXXX tests in XXXXXXXXXX XXXX. All XXXXXX XXXXX and boundary values XXXX also XX XXXXXXXX in XXXX data.
XXXX kind of testing XX unit XXXX (XXXXX-XXX, XXXXX-box, boundary, XXX.) and XXXX XXXX to explain what that type of testing does?
Black XXX XXXXXXX is XXXX XXXX only the XXXXXX XX XXXXXXX XXXX is XXXXX XXXXXX. XXX internal XXXXXXXXX of code is not XXXXX XXXX XXXXXXX. XXXXX XXX testing XX done XXXX you XXXX to check the XXXXXXXX variables/methods XX XXXX. XXX entire code XXXXXXXXX and XXX local/global variables and methods are XXXXX XXXX account XXX observed.
Unit XXXXXXX can XX XXXX in both XXX ways.
What XXX XXXX coverage XXX XXXX XXXXXXXX XXX how XXXX XXXXXX XX unit test?
Code XXXXXXXX XXXXXX XX XXX lines/blocks XX XXXX XXXXX XXXXXXXXX XX XXXXXXXXXX XXXX XXX. Data coverage refers to the span of XXXX XXXX that XX XXX able to cover by deploying a particular XXXX XXX.
XXXX XXXXXXXXX to XXXX XXXX, we must XXXXXXXX both XXXX coverage and XXXX XXXXXXXX. XXX% XXXX coverage XX often not possible so XX XXXX XXXXXXXX XXX XXXX XXXX XX XXXX increasing data XXXXXXXX while XXXXXXX in XXXX a XXXXXXXXXX r
XXXXXX for the XXXXX.
XXXX XXX test XXXXXXXXXXXXXXX that you learned XXXXX in week 3 XX XXXX XXXXXX? XXXX XXXX XXX explain in your own XXXXX:
(//XXXX this answer XXXXX in XXX course)
Who XXXXXXXX writes and XXXXXXXX unit test?
White XXX unit XXXXXXX is XXXX XX XXXXXXXXXX themselves. XXXXXXX black XXX XXXX XXXXXXX XXX be done XX XXXXXXXX XXXXXXX. XXXX XXXXX XXXX the XXXXXXX XX XXXX XX XXX XXXXXXXXXX XXXXXXXXXX.
XXX do you determine XXXX a XXXXXX has XXXX XXXXX in XX?
XXXXXXXX, various assertion statements XXX used to perform XXXXXXX. XXXXXXX of XXXXXXXXX XX XXXXXXXX in XXXX XXXXXXXX any such assertion fails. Logs XXXXXXXXX after XXXXXXX XXX XXXXX should be carefully examined.
XX XXXXXXX XXX XXXXX XXXXXX XXXX test XXX XXXX XXXXX XXXX?
XXX XXXX XXXXXXX are directed XXXX to XXX developers (in XXXX someone else did the testing) Proper conditions and XXXXXX-XXXX XXXXXX are placed in the code to XXXXXX the bugs XXXXXXXXXXX.
What happens next after XXXXXX is fixed in the code being tested?
XXXX the code is fixed XXX unit tests XXX XX-run, XX there XX any significant code XXXXXXX XXXXX fixing XXX XXX, we XXXX incorporate XXXX XXXX cases in XXX XXXX XXXX XX XXXXXXX XXXXXXXX XXX XXXX coverage.
1.X
XXX% Code XXXXXXXX Test Cases
X.2.1 Test XXXX 1
XXXX case XXXX:
Method being XXXXXX:
XXXXX XXXXXXXXXXX:
Input Data XX constructor and/or method you XXX XXXXXXX:
XXXXXXXX Results:
1.2.X Test Case 2
Test case name:
Method being XXXXXX:
XXXXX XXXXXXXXXXX:
Input Data to XXXXXXXXXXX XXX/or XXXXXX you XXX XXXXXXX:
Expected Results:
1.2.X Test Case 3
Test XXXX XXXX:
XXXXXX XXXXX tested:
Short Description:
Input Data XX XXXXXXXXXXX XXX/or XXXXXX you XXX testing:
Expected XXXXXXX:
…
X.X XXXXXXXXXX XXXX XXXXX for XXXX XXXXXXXX
X.3.X XXXX Case X
Test XXXX XXXX:
Method XXXXX XXXXXX:
Short Description:
XXXXX Data to constructor and/or method you are XXXXXXX:
Expected XXXXXXX:
X.3.2 Test XXXX X
Test case XXXX:
Method XXXXX tested:
Short XXXXXXXXXXX:
XXXXX XXXX XX constructor XXX/or XXXXXX you XXX testing:
Expected Results:
X.X.3 XXXX XXXX 3
Test case name:
XXXXXX XXXXX tested:
Short XXXXXXXXXXX:
Input XXXX XX XXXXXXXXXXX and/or XXXXXX you are testing:
Expected Results:
…
X.
XXXXXXX
This section lists all XXXXXXXXXX XXXXXXX
2.1
XXXXXXX
2.1.1
Defect X
Method/Constructor:XXX here the source XXXXXX or constructor name that XXX a defect
Defect Description: Put here, what behavior XX incorrect and why you believe it’s a XXXXXX. XXXX XXX expected XXXXXX XXXXXX XXXXXXXX?
XXX Found:XXXXXXX how you were able to XXXX this defect and XXXXX XXXX XXXX (name of testcase) XXXXX the XXXXX
X.1.2 Defect 2
Method/XXXXXXXXXXX:Put here XXX XXXXXX XXXXXX or constructor XXXX that has a defect
Defect XXXXXXXXXXX: Put XXXX, XXXX behavior is XXXXXXXXX and XXX you believe it’s a XXXXXX. What was XXXXXXXX XXXXXX actual behavior?
XXX Found:XXXXXXX how you were able XX find this defect XXX XXXXX test case (name of XXXXXXXX) found the XXXXX
.…
3.
XXXXX
XXX in this XXXXXXX XXX other XXXXXXXX or XXXXXXXX that XX not fit in the XXXXX sections that you XXXX to share with the XXXXXXXXXX.
3.1
XXX
3.X
YYY
">