|
About Brian Marick
|
I
consult
mainly on Agile software development, with a special
focus on how testing fits in.
Contact me
here: marick@exampler.com.
|
|
Syndication
|
|
|
|
Agile Testing Directions
|
Introduction
Tests
and examples
Technology-facing
programmer support
Business-facing
team support
Business-facing
product critiques
Technology-facing
product critiques
Testers
on agile projects
Postscript
Permalink
to this list
|
|
Working your way out of the automated GUI testing tarpit
|
-
Three
ways of writing the same test
-
A test should deduce its setup path
-
Convert the suite one failure at a time
-
You should be able to get to any page
in one step
-
Extract
fast tests about single pages
-
Link
checking without clicking on links
-
Workflow
tests remain GUI tests
Permalink to this list
|
|
Design-Driven Test-Driven Design
|
Creating
a test
Making
it (barely) run
Views
and presenters appear
Hooking up the real GUI
|
|
Popular Articles
|
A roadmap for testing on an agile project:
When consulting on testing in Agile projects, I like
to call this plan "what I'm biased toward."
Tacit knowledge:
Experts often have no theory of their work. They simply
perform skillfully.
Process and personality:
Every article on methodology implicitly begins "Let's
talk about me."
|
|
Related Weblogs
|
|
Wayne Allen
James Bach
Laurent Bossavit
William Caputo
Mike Clark
Rachel Davies
Esther Derby
Michael Feathers
Developer Testing
Chad Fowler
Martin Fowler
Alan Francis
Elisabeth Hendrickson
Grig Gheorghiu
Andy Hunt
Ben Hyde
Ron Jeffries
Jonathan Kohl
Dave Liebreich
Jeff Patton
Bret
Pettichord
Hiring
Johanna Rothman
Managing
Johanna Rothman
Kevin Rutherford
Christian Sepulveda
James Shore
Jeff Sutherland
Pragmatic Dave
Thomas
Glenn
Vanderburg
Greg Vaughn
Eugene Wallingford
Jim Weirich
|
|
Where to Find Me
|
|
Software
Practice Advancement
|
|
Archives
|
All of 2006
All of 2005
All of 2004
All of 2003
|
|
Join!
|
|
|
