10.12.2012 Views

Domain Testing: Divide and Conquer - Testing Education

Domain Testing: Divide and Conquer - Testing Education

Domain Testing: Divide and Conquer - Testing Education

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Analysis of Performance Test Results for Sowmya Padmanabhan's Thesis Data<br />

Cem Kaner, J.D., Ph.D.<br />

January 30, 2004<br />

This memo summarizes my notes on the results of two experiments conducted by Sowmya<br />

Padmanabhan in the summer of 2003. I am the research advisor for that work.<br />

Three of us, James Bach, Pat McGee <strong>and</strong> I, have done this analysis. I have discussed analysis<br />

criteria <strong>and</strong> results with both McGee <strong>and</strong> Bach. Their analyses have influenced my analysis to<br />

some degree, <strong>and</strong> I have somewhat influenced their analysis. My primary influence on them was<br />

in helping them develop their performance criterion. The evaluation criterion that I laid out for<br />

them is this:<br />

Compare the results from this Performance Test to the results that you would<br />

expect from a tester who claimed to have a year's experience <strong>and</strong> who claimed to<br />

be good at domain testing.<br />

All three of us have substantial testing experience, <strong>and</strong> have interviewed, hired <strong>and</strong> supervised<br />

testers. All of us have our own sense of what we would expect from a 1-year tester, <strong>and</strong> we also<br />

differ in the details of how we would do a domain testing analysis. We also recognize that there<br />

are different approaches to domain testing <strong>and</strong> that our goal was to determine whether this<br />

person looked reasonably experienced <strong>and</strong> whether the work looked reasonably sound.<br />

I am confident that our discussions influenced how we articulated our conclusions, but did not<br />

influence our conclusions. Each of us was independently uncomfortable with the results.<br />

I analyzed two experiments' results. Experiment 1's subjects had been mis-instructed on all-pairs<br />

testing. Additionally, the wording of some of the Experiment 1 questions was confusing.<br />

Accordingly, I am ignoring the Experiment 1 data on combination testing.<br />

The students took this as an open book exams. They had lecture notes, checklists, <strong>and</strong> other<br />

materials available. The lecture notes <strong>and</strong> h<strong>and</strong>outs presented a series of concepts associated with<br />

domain testing, <strong>and</strong> then boiled the concepts down into step-by-step procedures.<br />

Overview<br />

Student performance was remarkably consistent. They approached the task in the same order,<br />

identified the same variables, analyzed <strong>and</strong> discussed them in essentially the same way,<br />

presented the results in extremely similar tables, <strong>and</strong> made the same mistakes.<br />

Overall, I think that the students learned the procedures well, but didn't learn domain testing<br />

well.<br />

The answers are both more <strong>and</strong> less than I would expect from a 1-year experienced tester.<br />

• The tables are tidy <strong>and</strong> well-structured. Each variable is analyzed in terms of several<br />

dimensions. The all-pairs analyses of the Experiment 2 students look OK.<br />

• The students' descriptions of risks are uninsightful <strong>and</strong> largely redundant with the tests.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!