Testing & Testability

Why code that is hard to test almost always has a dependency it should not.

0 of 19 answered

• Not triedA test written after a bugFoundation
• Not triedCode that is hard to testFoundation
• Not triedNaming a testFoundation
• Not triedTests as a description of behaviourFoundation
• Not triedThe shape of a testFoundation
• Not triedUnit or integrationFoundation
• Not triedWhat a failing test should tell youFoundation
• Not triedA fake that actually worksCore
• Not triedCode that depends on nowCore
• Not triedHow much one test should checkCore
• Not triedMock or stubCore
• Not triedTesting a private methodCore
• Not triedTests that depend on each otherCore
• Not triedWhat coverage measuresCore
• Not triedA test that fails sometimesChallenge
• Not triedA test that passes while the code is brokenChallenge
• Not triedMocking a third-party libraryChallenge
• Not triedThe class that cannot be testedChallenge
• Not triedThe test that fails one run in twentyChallenge