X.1 Approach
XXXXXXX in XXXX section XXXX how XXXX XXXX XXXXXX be approached. Include in your discussion answers XX the XXXXXXXXX XXXXXXXXX: XXXX are XXX goals and objectives for XXXX test? XXXX XXX XXX XXX criteria XXX XXXX XXXX to be complete – how XX you know you are done unit testing? XXXX kind of testing XX XXXX XXXX (black-XXX, white-box, XXXXXXXX, XXX.) XXX XXXX XXXX XX XXXXXXX XXXX XXXX XXXX XX XXXXXXX does? XXXX XXX XXXX coverage and XXXX coverage XXX how XXXX XXXXXX XX XXXX test?XXXX XXX XXXX XXXXXXXXXXXXXXX that you learned XXXXX in week X XX XXXX XXXXXX? XXXX them XXX XXXXXXX in your own XXXXX.XXX XXXXXXXX XXXXXX and executes unit XXXX? How XX you XXXXXXXXX XXXX a defect XXX XXXX XXXXX in XX? XX XXXXXXX are found XXXXXX XXXX XXXX who XXXX fixes XXXX? What happens XXXX after defect is fixed in the code being XXXXXX? XX XX complete XXX XXXXXXXX in XXXX discussion XXXXXXXXXXXXX your XXXXXXXXXXXXX of XXXX Test.
XXXXX XXX XXXXXXXXX XX unit XXXX:
Unit XXXX are done to check whether a XXXXXXXXXX module or XXXX of code is working fine. It eliminates all XXXXXXX and runtime errors. It XX XXXXXXXXXXXX useful for XXXXXXX XXXX at XXX XXXX XXXXX module XX ensure any XXXXXX don’t XXXXXXXXX up to the modules XX in the hierarchy.
XXX XX you XXXX you XXX done XXXXXXX? :
When you have supplied all XXXXXXXX inputs that a XXXXXX can take and XXX module shows the expected XXXXXXX. XXXXX an important XXXXXX XX all XXXXXXXX XXXXXX is taken to save time and run XXXX XXXXX in XXXXXXXXXX XXXX. All corner XXXXX XXX boundary XXXXXX XXXX XXXX XX XXXXXXXX in test data.
What kind of testing XX XXXX test (black-XXX, XXXXX-XXX, XXXXXXXX, etc.) and XXXX sure XX XXXXXXX XXXX XXXX XXXX of testing XXXX?
Black XXX XXXXXXX is XXXX XXXX only the XXXXXX XX exposed APIs XX XXXXX tested. The XXXXXXXX XXXXXXXXX XX XXXX is not XXXXX into XXXXXXX. XXXXX box testing is done XXXX you want XX check XXX XXXXXXXX XXXXXXXXX/methods as well. The entire code structure and XXX XXXXX/XXXXXX XXXXXXXXX and methods are XXXXX into XXXXXXX and XXXXXXXX.
Unit XXXXXXX XXX be done in XXXX the XXXX.
XXXX are XXXX XXXXXXXX and data coverage and how XXXX relate XX XXXX XXXX?
Code coverage XXXXXX to XXX lines/XXXXXX XX code being XXXXXXXXX by XXXXXXXXXX test set. XXXX coverage refers to XXX span XX test XXXX that XX are able to cover by XXXXXXXXX a particular XXXX XXX.
XXXX reference to XXXX XXXX, XX must maximize both code coverage XXX XXXX XXXXXXXX. 100% XXXX coverage XX often not XXXXXXXX so we must optimize our test XXXX XX keep XXXXXXXXXX XXXX coverage while XXXXXXX in XXXX a XXXXXXXXXX r
untime for the tests.
What are XXXX characteristics XXXX you learned about in XXXX X of XXXX course? Name XXXX XXX XXXXXXX in XXXX own XXXXX:
(//fill this XXXXXX based in the course)
XXX XXXXXXXX writes XXX XXXXXXXX XXXX XXXX?
White box XXXX testing is XXXX by developers themselves. XXXXXXX XXXXX box unit testing XXX be XXXX XX XXXXXXXX XXXXXXX. XXXX often both the XXXXXXX is done XX XXX developers themselves.
How do you XXXXXXXXX that a XXXXXX has XXXX found in UT?
Normally, various XXXXXXXXX statements are XXXX XX perform XXXXXXX. Failure XX assertion XX XXXXXXXX in XXXX whenever XXX such XXXXXXXXX fails. XXXX XXXXXXXXX XXXXX XXXXXXX XXX tests XXXXXX be carefully examined.
As XXXXXXX are found XXXXXX XXXX test who XXXX fixes XXXX?
XXX test XXXXXXX XXX directed XXXX XX the XXXXXXXXXX (in XXXX XXXXXXX XXXX XXX the XXXXXXX) Proper XXXXXXXXXX XXX corner-case XXXXXX are XXXXXX in XXX XXXX XX XXXXXX the XXXX XXXXXXXXXXX.
XXXX happens XXXX after XXXXXX is fixed in the code XXXXX tested?
Once XXX code is fixed XXX unit tests XXX XX-run, if XXXXX XX XXX XXXXXXXXXXX code XXXXXXX XXXXX fixing the XXX, XX XXXX XXXXXXXXXXX more XXXX cases in XXX test XXXX to further XXXXXXXX the XXXX XXXXXXXX.
1.2
XXX% XXXX Coverage XXXX Cases
1.2.X Test Case X
XXXX case XXXX:
Method being XXXXXX:
XXXXX Description:
Input XXXX to constructor and/or method you XXX testing:
XXXXXXXX XXXXXXX:
XXXX case name:
XXXXXX XXXXX XXXXXX:
XXXXX XXXXXXXXXXX:
Input XXXX XX constructor and/or method you XXX testing:
XXXXXXXX Results:
Test case name:
XXXXXX XXXXX tested:
Short Description:
Input XXXX XX XXXXXXXXXXX and/or method you XXX testing:
Expected XXXXXXX:
…