One of the first things I learned as a Quality Assurance Analyst more than 15 years ago was I had to mark a test Pass or Fail. Green was associated with a test that passed and red associated with a test that failed. It seemed very black or white, but we all know that there is always room for some gray (or grey).
I was taught to follow the steps in the test case and when done mark it Pass or Fail - the vast Excel spreadsheet would have the empty column labeled Pass/Fail. I'd follow steps like these:
I was taught to follow the steps in the test case and when done mark it Pass or Fail - the vast Excel spreadsheet would have the empty column labeled Pass/Fail. I'd follow steps like these:
- Write the words "This IS a tESt"
- Highlight "Test"
- Bold "THIS"
- Underline another word
Expected Result: THIS IS a tESt
Actual Result: This IS a Test
And the test would be marked Pass...but is it? Is it Fail? Most of it Passes, there's just this one tiny detail.
And that's the thing, the Detail. It wasn't until many more years of testing did the performing of the steps, the marking of the scenario Pass or Fail come to matter. What I was learning was to pay attention to the details.
I have marked hundreds of test scenarios Pass/Fail, but looking back the Sort of was and is the more interesting aspect of testing. It would evolve into conversations, discussions, meetings, thoughts, solutions and fixes. It would be a step (followed) that got this tester to be part of the team.
Comments
Post a Comment