[{"_1":2,"_46":-5,"_47":-5},"loaderData",{"_3":4,"_14":15,"_44":-5,"_45":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9,"_10":11},"user","shoppingCartId","toast","locale","en","constants",{"_12":13},"paypalClientId","AenrHU49peF-ZUH-Yq7AXLLNZYGUGlml474U16NCjB4ZznmQCEjiliN3whyuVZmkb7VxEzmTALgtKEKE","routes/_store+/_readers+/email_author.$slug/route",{"_16":17,"_43":-5},"book",{"_18":19,"_20":21,"_22":23,"_24":25,"_26":27,"_28":29},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvMjYyNTM","title","Unit Testing and Test-Driven Development Self-Check","state","published","contactAuthorMethod","email","aboutText","

The self-check is a multiple-choice quiz you can take on your own to check your knowledge of the subjects of software unit testing and test-driven development (TDD). Participants in my training classes on TDD receive email invites to take the quiz on Google Docs. They also receive a document that reviews the answers to the quiz and provides additional information about the topics mentioned in the quiz.

This book comprises the quiz and the review document as a PDF file. These documents do not constitute a complete training course on unit testing and TDD. The material is supplemental to information provided in the training courses. The reader must not expect to learn how to test-drive software just by reading this material.

People who might get value from this material include those who

\n
are curious about TDD or automated unit testing, but aren't sure how these techniques might apply to their work context.
\n
\n
are not sure what forms of value to expect from unit test automation and/or TDD.
\n
\n
do not understand what programmers mean when they say TDD is not a testing
\n
technique.
\n
\n
do not understand what testers mean when they say automated testing is not really testing.
\n
\n
have attempted to use TDD in the past with poor results or mixed results.
\n
\n
hold opinions (or reservations) about TDD based on negative past experiences or negative reports from others.
\n
\n
are not sure exactly what constitutes a \"unit\" or a \"unit test.\"
\n
\n
are not sure whether or how TDD and/or automated unit testing can play a role in different work situations, such as greenfield development, enhancement of existing applications, debugging software during a production support event, or remediating accumulated technical debt.
\n
\n
are not sure whether or how TDD can be applied to different technologies, such as embedded systems, mobile applications, mainframe systems, or in configuring thirdparty application platforms.
\n
\n
are not sure whether or how TDD can be applied with different types of programming languages, such as objectoriented, functional, or procedural.
\n
\n
are not sure whether or how TDD and unit testing can be applied to languages with different characteristics, such as strong type systems, static type systems, or dynamic type systems.
\n

","authors",[30],{"_18":31,"_32":33,"_5":34},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci8yNzMwOA","name","David Nicolette",{"_35":36},"avatar",{"_37":38,"_39":40,"_41":42},"url","https://secure.gravatar.com/avatar/e27e8f1c2ac0b54e49a053521d02772e?r=pg&d=mm","styleName","medium","exists",true,"currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the Author