Test Driven Development in Ruby: A Practical Introduction to TDD Using Problem and Solution Domain Analysis

 ContentsAbout the AuthorAbout the Technical ReviewerForewordAcknowledgmentsIntroductionChapter 1: The BasicsTerminologyKataCoding KataDomainProblem DomainSolution DomainDomain ExpertDomain KnowledgeDefining the Problem Domain and the Solution DomainLearning TDDLearning by Coding KataLearning RetrospectiveIntent vs. ImplementationIntentImplementationIntent and ImplementationMusicLyricsHome PlanSeparate Intent from ImplementationSheep ExampleTest API ExampleBowling Game ExamplePrecision in Language and MeaningTests Are Executable DocumentationShift in Mental StateOverview of TDDTest Driven DevelopmentThe Five Steps of TDDFailing TestWriting a Failing TestMinimal ImplementationRefactoringSeparation of Intent from ImplementationPing Pong Pair Programming TechniqueBlack Box PerspectiveShift in System and Mental StatesImportance of DisciplineOvercoming DifficultyProblem-Solving SkillsFour Phases of Problem SolvingUnderstand the ProblemDevise a PlanCarry Out the PlanLook BackSubskills of Test Driven DevelopmentProblem Domain AnalysisSolution Domain AnalysisAlternative RepresentationsDivide and Conquer StrategyDesigning Test CasesSum a List of NumbersSequence of Test CasesStarter TestNext TestStory TestAssertionTest Driving CalculatorCanonical Test StructureGivenWhenThenArrange, Act, AssertCalculatorAdditionSubtractionCommon MistakesCommon Mistakes in the TDD CycleMistakes in Step OneMistakes in Step TwoMistakes in Step ThreeMistakes in Step FourMistakes in Step FiveBase ConversionProblem StatementProblem Domain AnalysisSolution Domain AnalysisAlgorithmCodeCode Reflecting Test DataMultiple AssertionsVowel CheckerForgetting to Test the Negative CaseNot Testing the Boundary ConditionsNot Updating the TestsImplementation-Aware TestsSummaryChapter 2: KatasFibonacci SequenceProblem StatementProblem Domain AnalysisSolution Domain AnalysisAssumptionsTest-Driven FibonacciFizz BuzzProblem StatementProblem Domain AnalysisSolution Domain AnalysisTest-Driven FizzBuzzNo if-else ConstraintNo if ConstraintImplementation-Independent TestsCrossing the System BoundaryMocking as a Design TechniqueAbstraction Levels in a SystemTesting Random BehaviorTesting Time-Dependent BehaviorSimulating User InputOpen Closed PrincipleDifference ReductionDefect LocalizationStackBasic StackTest Precisely and ConcretelyMake Your Code RobustThe Sieve of EratosthenesAlgorithmPrime FactorsProblem StatementProblem Domain AnalysisSolution Domain AnalysisSummaryChapter 3: Techniques in TDDObvious ImplementationFake It Till You Make ItTriangulationAdditionSum a List of NumbersProblem Domain AnalysisSolution Domain AnalysisInitial ConditionSteps to Solve the ProblemAlgorithm DescriptionAssumptionsTest CasesSolution Domain Analysis ReduxReductionProblem StatementExample....1Example....2Steps to Solve the ProblemIterative ConstructInitial ConditionsEuclidean AlgorithmTest-Driven GCDTransformation Priority PremiseRefactorings and TransformationsTransformation ListCounterProblem StatementProblem Domain AnalysisSolution Domain AnalysisSteps to Solve the ProblemAlgorithmLogical DesignSkeleton CodeTerminating ConditionInitial ConditionPseudo CodeTest-Driven CounterFactorialSummaryChapter 4: Importance of Test CasesProblem StatementProblem Domain AnalysisSolution Domain AnalysisAlgorithm DescriptionCodeSummaryChapter 5: Character-to-Number ConversionProblem StatementDiscussionSolution Domain AnalysisTest CasesSummaryChapter 6: Conway’s Game of LifeProblem StatementProblem Domain AnalysisAssumptionsSolution Domain AnalysisMoore NeighborhoodTest CasesTest-Driven Game of LifeApplication StatementRefactor SolutionCode ReviewSummaryChapter 7: Gilded RoseForm vs. StructureProblem StatementInitial SetupFormStructureDeMorgan’s LawsMaking Temporal Dependency ExplicitImproving the StructureExpress IntentTell-Don’t-Ask PrincipleInheritanceImplementing the New FeatureExpress Domain ConceptsRetrospectiveSummaryChapter 8: Dealing with Third-Party APIsSubscription PlanCreate a PlanDelete a PlanStripe CustomerSubscribe a Customer to a PlanTest-Driven Stripe LibraryIntegration TestsUnit TestsMake Your Code RobustSummaryChapter 9: Pair RankingProblem Domain AnalysisSolutionSummaryIndex