CSCA08H3 Lecture Notes - Lecture 15: White-Box Testing, Black-Box Testing, Formal Verification
Document Summary
Today"s topic: testing part 2 nov 21: doctest: Have been used already; good for clean checks. Not the best of way of testing. As programming becomes complicated; it begins to get harder to test. Overall just not good: unittest: allows you to complete advanced testing. Side note: import example_functions as func is a way to rename example_functions. (cid:373)ethods (cid:373)ust start with (cid:862)test(cid:863) i(cid:374) the (cid:272)lass for test. For creating tests here are the steps: Strategize: table should be input, output, reason. Funnily enough, auto-marker uses test cases like this: black box vs white box testing. Tr(cid:455) to test, do(cid:374)"t k(cid:374)ow what"s goi(cid:374)g to happe(cid:374). (cid:271)ad (cid:374)a(cid:373)e should (cid:271)e (cid:272)alled (cid:862)(cid:272)lear (cid:271)o(cid:454) testi(cid:374)g(cid:863) Like (cid:271)la(cid:272)k (cid:271)o(cid:454) testi(cid:374)g, (cid:271)ut we (cid:272)a(cid:374) see what"s happening. Cut down number of cases we need, focused testing. Black box testing is based on adt: coverage testing (usually done as black box testing, adversarial testing. Gives you a lot of thought about your testing code: regression testing.
