软工国外原课件09MoreBDDTDD.pptxVIP

Explicit vs. Implicit and Imperative vs. Declarative Scenarios (Engineering Software as a Service §7.9);Types of Scenarios;Explicit vs. Implicit Scenarios;Imperative vs. Declarative Scenarios;Example Imperative Scenario;Domain Language;Example Declarative Scenario;Declarative Scenario Needs New Step Definitions;9;Explicit scenarios usually capture integration tests;11;Fallacies Pitfalls, BDD Pros Cons, End of Chapter 7 (Engineering Software as a Service §7.11);Pitfalls;Pitfalls;Pitfalls;Pitfalls;Pitfalls;Pitfalls;19;A BDD downside is requiring continuous contact with customers, which may not be possible;21;Administrivia;How Popular is Agile?;24;BDDGood Bad;BDD;27;RSpec on Rails(Engineering Software as a Service §8.2);Rspec: Domain-Specific Language for Testing;Example: Calling TMDb;The Code You Wish You Had;32;An instance method of the Movie model;34;The TDD Cycle: Red–Green–Refactor(Engineering Software as a Service §8.2);Test-First Development;How to test something “in isolation” if it has dependencies that would affect test?;The Code You Wish You Had;TDD for the Controller Action: Setup;What Model Method?;41;It would override the real method, even if it did exist;43;Seams(Engineering Software as a Service §8.3);Seams;How to Make This Spec Green?;;48;Ensure the API to the real find_in_tmdb matches the fake one used by should_receive;50;Expectations(Engineering Software as a Service §8.4);Where We Are Where We’re Going: “Outside In” Development;The Code You Wish You Had;“It Should Select Search Results View to Display Match”;Should Should-Not;Checking for Rendering;;58;5.should be = result;60