thoughtbot Build Phase #36
Rubyの.reverseをObj-Cでできるようにする
TDD
DHHの話
Unit Testだけに頼りすぎるのは良くないと言っていると思う
Integration Testだけに頼りすぎるのも良くない
side project keeping me interest
tony
stray dogs
fed taken cared off
drunk kick dog killed
testing
turned the corner
more fun to write
proponent
in theory
teaching best learn
.reverse ruby
mimic that
category
literaly reverse string
kind of skip
tdd
fail pass
big point
another failing test pass
mindset
similar
are you need it
refactor red green
code coverage
unit test
feels crappy
writes wrapper
easy
everybody does
stub out
black box
keychain
stupid wrapper
testing implementation
not testing code anymore
simple class
inverse true
static table view
thin wrapper
not worth
hard
should test everything
conditional
keychain
user default
needs to be verified
mutate
independently
lot of factories
setting up url session
starting c
concept
wrap wrong place
easier
not testing
functional programming
less mutation
slowing something
right thing
concurrency
up and down
api
specta
shared example
non unique part
create dictionary
system
conform
smell code duplicate
barebone
base request
shared examples group
separating behavior
contest decision
explicit
every request
other way
assertion
qualify
expose
care about
other request
feels
spec
server act
servers behavior
request spec
mock nothing
payload
end to end
bottom layer
network
perform request
reusable
af networking
ns url session
tested on its own
doesnt care about
json
test json
stub out url
json fixture
404 error
json error
super simple
factory method for each endpoint
taken dictionary
mapping
day string
url string
3 pieces
glue
completion block
5 lines
request
username passeord
json
return user
error
user nil
public interface
everything
single condition
network client
testing implementation
3 tests
40lines total
mocking network
grabbing right request
ugly
refactor
3 individual test
3 expectation
dosen
should listen
sucks to test
bad code
trying stub
goal
acceptance test
feels good
actual request
return specific file
parsing
expectation after 3 lines setup
wouldnt rely on unit test
integration test
pseudo duplication
crappy
business code view code
mental separation
railsconf keynote
dhh
havent seen either
dont over rely on unit test
save time
benefit
shouldnt over rely on integration test
thin glue code
view model
assert
hooked up
dont trust library
view model
compiler
blog post
tdd on ruby
builds clean
warning
we have
other dont have
lean on
