Test analysis
CAST 2009 Early Bird Rates Extended until May 1
Submitted by sbarber on Thu, 16/04/2009 - 06:42. books | context-driven testing | events | functional testing | general software testing | industry recognition | metaphors | non-functional testing | other online resources | people issues | perspectives | project management | test analysis | test management | usability testing
The 4th Annual Conference of the Association of Software Testing (CAST) 2009
Colorado Springs, Colorado, July 13-16, 2009
Serving Our Stakeholders
Opening Keynote by: Dr. Jonathan Koomey
Closing Keynote by: Robert Sabourin & Tim Coulter
Invited Speakers: Mike Dwyer and Kevin Brennan
CAST 2009 Early Bird Rates Extended until May 1
Submitted by sbarber on Thu, 16/04/2009 - 06:36. books | context-driven testing | events | functional testing | general software testing | industry recognition | metaphors | non-functional testing | other online resources | people issues | perspectives | project management | test analysis | test management | usability testing
The 4th Annual Conference of the Association of Software Testing (CAST) 2009
Colorado Springs, Colorado, July 13-16, 2009
Serving Our Stakeholders
Opening Keynote by: Dr. Jonathan Koomey
Closing Keynote by: Robert Sabourin & Tim Coulter
Invited Speakers: Mike Dwyer and Kevin Brennan
A misleading benchmark...
Submitted by sbarber on Tue, 03/03/2009 - 05:13. general software testing | metaphors | other online resources | patterns | people issues | performance testing | perspectives | project management | test analysis | test management
Archeological Black Swans: tales of observation, deduction and lost treasure
Submitted by Erik Petersen on Tue, 25/11/2008 - 13:38. general software testing | metaphors | perspectives | test analysisI had dinner with Michael Bolton and James Bach during STARwest, which was a great feast of ideas and insights in addition to the fine food. One of the interesting new ideas that I hadn’t yet heard of was Black Swan Theory , mentioned by Michael Bolton. As an Australian, I could see nothing unusual about the concept of a Black Swan, but in Europe before the discovery of Australia, a black swan was seen as an impossibility since none had ever been seen. The Black Swan theory relates to an unexpected, radical event that alters your perception of reality. As testers. we are often told the European view that black swans don’t exist (this code is fully tested, two weeks of testing will be more than enough, one retest all you need, works on my machine), but we know that our world is full of black swans we call bugs. There is also the other myth that “all tests must be scripted” disproved by the black swan of exploratory testing.
Testing Lessons From Civil Engineering
Submitted by sbarber on Sat, 21/06/2008 - 07:13. context-driven testing | development methodology | events | functional testing | general software testing | heuristics | patterns | perspectives | test analysisBelow is the paper I submitted as a prologue to an experience report, discussion, and (hopefully) additional research that I'm presenting for the first time during:
Performance Testing Guidance for Web Applications book
Submitted by sbarber on Mon, 17/12/2007 - 10:49. performance testing | project management | test analysis | test managementSome time back, I blogged about a book I’d been significantly contributing to being available as a free .pdf download. (see the entry here)
Well, the book quietly appeared in “dead tree format” (as Stuart Moncrieff put it in his blog post about the book) a couple of weeks ago and I’ve been getting light heartedly scolded by some of my friends and readers for not making a big announcement, so here’s my “big announcement.”
Performance Testing Guidance for Web Applications
by: J.D. Meier, Scott Barber, Carlos Farre, Prashant Bansode, and Dennis Rea is now available on Amazon.
A Month of Gatherings
Submitted by David Gilbert on Wed, 14/06/2006 - 05:08. events | exploratory testing | general software testing | industry recognition | test analysis | test techniquesI have just finally landed after spending a month running around to various conferences and workshops. I will discuss each of them in a bit of detail below, but first I want to talk about the entire experience.
Conferences, tradeshows, and workshops have many purposes. For vendors, it is an opportunity to try and get your wares in front of an interested audience. For practitioners, it is an opportunity to see the latest in tools and technology, and attend tutorials and sessions, sometimes from prominent industry leaders. And for everyone, it is an opportunity to meet new colleagues, reconnect with old friends, and engage in that most basic and valuable activity of any true conference…conversation.
Conferences, tradeshows, and workshops have many purposes. For vendors, it is an opportunity to try and get your wares in front of an interested audience. For practitioners, it is an opportunity to see the latest in tools and technology, and attend tutorials and sessions, sometimes from prominent industry leaders. And for everyone, it is an opportunity to meet new colleagues, reconnect with old friends, and engage in that most basic and valuable activity of any true conference…conversation.
Tester thinking...
Submitted by sbarber on Sun, 09/04/2006 - 21:23. test analysisSay you were given the following requirements...
- Users shall be able to enter any of nine predefined data objects
- User interface shall consist of nine blocks of three rows and three columns
- Each row, column and/or block shall accept only one member of each data object
What am I describing?
Ever played Soduku?
While indulging my (hopefully temporary) addiction to this brain teasing virus, I spent a few brain cells thinking about testing. I thought about what requirements might look like and led me to wonder *why* requirements so often look like those above. Why not just add a picture of the playing "board" and rules of the game? Wouldn't that be easier?
- Users shall be able to enter any of nine predefined data objects
- User interface shall consist of nine blocks of three rows and three columns
- Each row, column and/or block shall accept only one member of each data object
What am I describing?
Ever played Soduku?
While indulging my (hopefully temporary) addiction to this brain teasing virus, I spent a few brain cells thinking about testing. I thought about what requirements might look like and led me to wonder *why* requirements so often look like those above. Why not just add a picture of the playing "board" and rules of the game? Wouldn't that be easier?