Avatars of TDD - Agile India€¦ · Avatars of TDD Rule of Diversity ... Outside In Inside Out...

Copyright © 2013, AgileFAQs. All Rights Reserved.

Avatars of TDDRule of Diversity

Distrust all claims for “One True Way”

Naresh [email protected]

@nashjain http://nareshjain.com

1Saturday 2 March 2013

mailto:[email protected]


http://exortech.com/blog

http://exortech.com/blog


Key Questions

Are we building the right product?

Are we building the product right?

Business Facing

Technology/Implementation Facing



Brian Marick’s Test Categorization

Business Facing


Supp

orts

Pro

gram

min

gC

ritique product



It Helps to Think of Tests this way...

Business Facing


Dri

ves

Dev

elop

men

t Critique product




Business Facing


Dri

ves

Dev

elop

men

t Critique productUnit Testing




Business Facing


Dri

ves

Dev

elop

men


Acceptance Testing Low-fi prototypes




Business Facing


Dri

ves

Dev

elop

men



Exploratory TestingUI and Usability Testing




Business Facing


Dri

ves

Dev

elop

men



Exploratory TestingUI and Usability Testing

Performance TestingSystem Tests


Business Facing


Dri

ves

Dev

elop

men

t Critique product

Outside In

Inside Out

Brian Marick’s Test Categorization


TDD RhythmTest, Code, Refactor


Add a Test



Add a Test

Run the Test



Add a Test

Run the Test

Pass



Add a Test

Run the Test

Fail

Pass



Add a Test

Run the Test

Make a little change

Fail

Pass



Add a Test

Run the Test


Run the Test

Fail

Pass



Add a Test

Run the Test


Run the Test

Fail

Fail

Pass



Add a Test

Run the Test


Run the Test

Fail

Pass

Fail

Pass



Add a Test

Run the Test


Run the Test

Refactor

Fail

Pass

Fail

Pass




Acceptance Test Driven Development




Story




Story

Acceptance Criteria




Iteration

Story

Acceptance Criteria




Iteration

Automated Acceptance Tests

Story

Acceptance Criteria




Iteration


Story

Acceptance Criteria

Automated Unit Test




Iteration


AutomatedAcceptance Tests

Story

Acceptance Criteria

Automated Unit Test




Iteration



Story

Acceptance Criteria

ExploratoryTesting

Automated Unit Test




Iteration



Story

Acceptance Criteria

Acceptance Criteria

ExploratoryTesting

Automated Unit Test




Iteration



Story

Acceptance Criteria

Acceptance Criteria

ExploratoryTesting

Automated UI Tests

Automated Unit Test




Iteration



Story

Acceptance Criteria

Acceptance Criteria

ExploratoryTesting

Automated UI Tests

TESTS

PERFORMENCE

Automated Unit Test


Commercial Break!


Mumbai10Saturday 2 March 2013

Tech Talks!



Veterinarian Information System


Outside In: ATDDFitnesse Document:Assertions: 17 right, 0 wrong, 0 ignored, 0 exceptions

com.vis.billing.fixtures.PaidCashBill

account details

account number patient name owner name

1001 Fluffy Dave Atkins

procedure detailsname cost

Routine Office Visit 250

Rabies Vaccination 50

bill

account number? owner name? patient name? total? paid?

1001 Dave Atkins Fluffy 300 false

procedure details on the bill

name cost

Routine Office Visit 250

Rabies Vaccination 50

pay Cash

patient name? owner name? account number? bill no? payment method? amount paid?

Fluffy Dave Atkins 1001 1 Cash 300

check paid true

check total 0


Outside In: Output


ATDD: Another ExampleAcceptance test:class FluffyTest < Test::Unit::TestCase def test_examination_and_shots vet = Veterinarian.new clinic = Clinic.new "Main Line health" dave = Owner.new "Dave" fluffy = Patient.new "Fluffy" dave.has fluffy visit = clinic.visit(fluffy, vet) do |v| v.procedure "Rabies vaccination", 50 end invoice = visit.invoice assert_equal invoice.to_s, <<-INVOICE Routine visit: $200 Rabies vaccination: $50 Total: $250 INVOICE receipt = clinic.pay_for visit, 100 assert_equal receipt.to_s, <<-RECEIPT Paid $100 for Routine visit Paid $0 for Rabies vaccination Outstanding: $150 RECEIPT endend


Outside In: Output


Inside Out: Unit TDDpublic class ClinicTest { private Clinic clinic = new Clinic();

@Test public void amountOnTheReceiptShouldMatchBillableAmount() throws Exception { Billable billable = new Billable() { public int totalAmount() { return 0; } }; Account dave = new Account(101, "Dave");

Receipt rcpt = clinic.payCash(dave, billable); assertEquals("Amount on receipt does match procedure cost", billable.totalAmount(), rcpt.getAmount()); }

@Test public void customerPayesBillableAmountForCashTransaction() throws Exception { final int billableAmount = 56; class AmountCharged { int charged; }; final AmountCharged charged = new AmountCharged();

Billable billable = new Billable() { public int totalAmount() { return billableAmount; } };

Account dave = new Account(101, "Dave") { public void charge(int amount) { charged.charged = amount; } };

clinic.payCash(dave, billable); assertEquals("Account is not charged billable amount", billableAmount,charged.charged); }}

public class BillableTest {

private static final Account daveSAccount = new Account(101, "Dave"); private static final List<Service> services = new ArrayList<Service>();

@Test public void totalBillableAmountShouldBeZeroIfNoServicesAreProvided() { Billable bill = new Bill(daveSAccount, services); assertEquals("Total amount is not Zero", 0, bill.totalAmount()); }

@Test public void totalBillableAmountShouldBeTotalOfEachServiceProvided() { services.add(new Procedure("Rabies Vaccination", 250)); services.add(new Procedure("Regular office Visit", 50));

Billable bill = new Bill(daveSAccount, services);

assertEquals("Total Amount is not 300", 300, bill.totalAmount()); }

@After public void cleanUp() { services.clear(); }}


Inside Out: Output


Inside Out: Another Examplepublic class ChargeAccountForServices { private static final Billable bill = createMock(Billable.class); private static final Accountable account = createMock(Accountable.class); private static final Clinic clinic = new Clinic();

@Before public void setUp() { reset(account); reset(bill); }

@Test public void shouldMakePaymentsAgainstAnAccount() { account.paid(bill); replay(account); clinic.pay(300, bill, account); verify(account); }

@Test public void shouldHaveZeroAmountDueOnReceiptIfCompletePaymentIsMade() { expect(bill.amount()).andReturn(300); replay(bill); Receipt receipt = clinic.pay(300, bill, account); verify(bill); assertEquals(300, receipt.amount()); assertEquals(0, receipt.amountDue()); }

@Test public void shouldDisplayAmountDueOnTheReceiptIfIncompletePaymentIsMade() { expect(bill.amount()).andReturn(500); replay(bill); Receipt receipt = clinic.pay(300, bill, account); verify(bill); assertEquals(300, receipt.amount()); assertEquals(200, receipt.amountDue()); }}


public class CreateBillForClientAccount { private static final List<Service> services = new ArrayList<Service>(); private static final Accountable account = createMock(Accountable.class); private Bill bill;

@Before public void setUp() { reset(account); }

@Test public void shouldThrowExceptionIfAccountIsNotDueForPayment() { expect(account.isPaymentDue()).andReturn(false); replay(account); try { new Bill(account, null); } catch (NoPaymentDueException e) { // expected } verify(account); }

@After public void cleanUp() { services.clear(); }

@Test public void shouldCreateABillWithTheTotalCostOfAllTheServices() { IMocksControl control = createControl(); Service rabiesVaccination = control.createMock(Service.class); Service routineVisit = control.createMock(Service.class); services.add(rabiesVaccination); services.add(routineVisit);

expect(account.isPaymentDue()).andReturn(true); expect(account.unpaidServices()).andReturn(services); bill();

expect(rabiesVaccination.cost()).andReturn(250); expect(routineVisit.cost()).andReturn(50);

control.replay();

assertEquals(300, bill.amount()); control.verify(); }

private void bill() throws NoPaymentDueException { replay(account); bill = new Bill(account, null); verify(account); }}


Inside Out: Output



Where do you Stand?

Unit Test x Acceptance test

API x User Interface

State x Interaction

OO x Procedural

Easy x Core

Narrow x Broad

Drive Design x Validate Design



Bonus Calculator

Sales Quota Commission % Tax % Result1200 1100 10 10 91200 1500 10 10 01200 1200 10 10 0



Sales TaxBasic sales tax is applicable at a rate of 10% on all goods, except books, food, and medical products that are exempt. Import duty is an additional sales tax applicable on all imported goods at a rate of 5%, with no exemptions.

When I purchase items I receive a receipt which lists the name of all the items and their price (including tax), finishing with the total cost of the items, and the total amounts of sales taxes paid.

Write an application that prints out the receipt details for these shopping baskets...

Input 1:1 book at 12.491 music CD at 14.991 chocolate bar at 0.85

Output 1:1 book : 12.491 music CD: 16.491 chocolate bar: 0.85Sales Taxes: 1.50Total: 29.83

Input 2:1 imported box of chocolates at 10.001 imported bottle of perfume at 47.50

Output 2:1 imported box of chocolates: 10.501 imported bottle of perfume: 54.65Sales Taxes: 7.65Total: 65.15

Input 3:1 imported bottle of perfume at 27.991 bottle of perfume at 18.991 packet of headache pills at 9.751 box of imported chocolates at 11.25

Output 3:1 imported bottle of perfume: 32.191 bottle of perfume: 20.891 packet of headache pills: 9.751 imported box of chocolates: 11.85Sales Taxes: 6.70Total: 74.68



Medical System Age Calculating Program



Medical System Age Calculating ProgramAge Reported in

Greater than 1 Year <Patient Name> is # Years old

> 1 Month & < 1 Year <Patient Name> is # Months old

> 1 Day & < 1 Month <Patient Name> is # Days old

> 1 Hr & < 1 Day <Patient Name> is # Hours old



Medical System Age Calculating ProgramAge Reported in

Greater than 1 Year <Patient Name> is # Years old

> 1 Month & < 1 Year <Patient Name> is # Months old

> 1 Day & < 1 Month <Patient Name> is # Days old

> 1 Hr & < 1 Day <Patient Name> is # Hours old

Doctors and Nurses might like to add and remove new Durations.For Ex: If they add Decade, and Patient’s age is greater than 10 years, then age should be reported as <Patient Name> is # Decades old.

Similarly: If they add Week, and Patient’s age is greater than 7 Day, but less than a month, then age should be reported as <Patient Name> is # Weeks old.



Meeting Assistant



Coffee Vending MachineAgileWorks just contracted you to design and build a set of coffee machines for their work place. There are mechanical designers taking care of all the mechanical parts of the machines. You are responsible for the machine's controlling software.

AgileWorks’ requirements are very simple. They want to sell coffee, with or without cream powder and sugar, for $0.35. The front panel will have 4 buttons, for Black, Cream, Sugar and Cream&Sugar. There will also be a Coin Return button. The machine will take (American) coins only, and give change.

Any other displays are up to you to decide on and design. There will be dispensers that can dispense a fixed amount of: cup, hot water, coffee powder, cream powder, sugar.

The basic operations that your machine should be able to perform are• Accept money• Accept coffee selection• Provide coffee • Return change • Allow refill of dispensers • Handle boundary conditions such as insufficient money or material.

You may add any other aspects of your own.



Where do you Stand?

Unit Test x Acceptance test

API x User Interface

State x Interaction

OO x Procedural

Easy x Core

Narrow x Broad

Drive Design x Validate Design



Thank you

Naresh [email protected]




Avatars of TDD - Agile India€¦ · Avatars of TDD Rule of Diversity ... Outside In Inside Out...

Documents

Transcript of Avatars of TDD - Agile India€¦ · Avatars of TDD Rule of Diversity ... Outside In Inside Out...