brief us stuff or should c1/tdp heavy stuff go here, 15 min?

where we talk about supermarket pricing and some of the concerns that can be practiced with tdd describe kata - https://www.youtube.com/watch?v=auavC2MGnMU

where we describe the system requirments for practicing the exercise

https://www.eclipse.org/downloads/eclipse-packages/ https://www.jetbrains.com/idea/download/

https://github.com/join?source=header-home

or clone, or download zip if skipping travis/git https://github.com/automaticgiant/supermarketcraft

where we describe the initial requirements required to exercise the driver

line item (interface): unit price, unit(default: pkg), desc, qty enum: normal, nx, bogo, discount idk - something that we can do control interface so driver can run some transactions wiht it but cover some of the pricing options

feature branch

watch it fail

make it pass satisfies subtotal 1 commit/merge

https://travis-ci.org/ talk about ci (don't forget to run tests, check pr automatically, don't build on broken code, history) talk about test coverage benefits (prevent brittle code, catch regressions, frees you to iterate, facilitates teamwork)

feature branch

watch it fail

make it pass commit/merge

examples smells naming conventions

• kata
• kata backstory
• supermarket exercise