Rapid Testing, Rapid Development
by mennovanslooten on Oct 16, 2010
- 1,598 views
My presentation at the jQuery Boston conference on October 16th 2010
My presentation at the jQuery Boston conference on October 16th 2010
Accessibility
Categories
Tags
More...Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 3
- Downloads
- 0
- Comments
- 0
- Embed Views
- Views on SlideShare
- 1,547
- Total Views
- 1,598
from amsterdam Honored and excited
flown all the way to tell about how I avoid work
when I started hooked by productivity, easy to create something from nothing
The work I avoid I avoid to stay fast
Not telling how to be lazy. Telling about feedback loop.
Initially short, get momentum going, get rhythm, get in the zone
As project grows the loop grows, Dependencies, interaction
Not once but every time, for every browser
forget what your latest change was
really here to make you aware of the loop and the things we can do to keep it small
start with the refresh phase
a little demo to illustrate
typical feature: group chat or conferencing
after a change I’d have to go through these steps to be able to verify
backend may be broken, AIM may slow, blocked accounts
what can we do?
otherwise we can try to automate the interaction
what about dependencies?
go through these solutions one by one
start with static html
problem is that DOM and CSS modified by JS
we want the page in the state we see it
the other option was automated interaction
been a good boy or girl? trigger jQuery event handlers like a user
created a little plugin autorun let’s check out code
very useful and savesme a lot of time
by the way did you notice this little trick?
now we’ve got 2 options to deal with long interactions
what about the dependencies? I said something about mocking them
mockjax mocks all types of ajax, including json with a great level of configuration
mockjson is specialized for json and can do random template-based responses
let’s look at a little mockjax example
plan to move to mockjax soon
super configurable
great for when backend isn’t ready yet
great for testing error handling like timeouts and 404’s
for myself (again) I built something specialized for json requests
that concludes my suggestions for the “refresh” phase
let’s move to “verify” phase
if not, what failed
if so, what to do next
consists of 2 aspects:
there are many frameworks but it all boils down to this:
figured that jquery makes both things very easy
set out to build a framework for our new webclient
super easy to write, debug, run tests
no config, no install
small demo to refresh your memory
again 2 things: first simulating interaction
then testing UI properties
then wrap inside a testcase
that’s UITest you can use any framework you want of course
now that we’ve automated this part of the verification phase, what about the other?
so we’ve optimized our verification phase
what about the edit phase?
you are here means you are trying to become better programmers
what about editors?
some take it really far and personally. in my opinion it really doesn’t matter much
because
there’s tons of features you’re not using when you could
scratch that
I find it amazing to see people wanting to be rockstar developers
but don’t invest any time in learning their instrument
your editor is the most important tool in your arsenal
it is such a shame that some devs don’t go beyond the basics
it is a huge part of your productivity
the most important message I want to get across is the awareness of feedback loop
be aware of the time you’re wasting
be aware of the unnecessary taks you are accumulating
thank you