A Day between a Developer and a Tester
I think, in every organisation - there would be talks about Developer vs Tester and we have seen many cartoons on it.
Here is one scenario, which is common between teams.
I suppose Developer with "David" and Tester as "Tony". These two persons have two years of experience in their respective roles.
A day appeared, Tony logs a bug in bug triage based on the thinking, how system or application under test can fail and proceeds to next steps.
Next moment, David marks as Not a Bug.
Tony then meets David, and asks why did you mark it as "Not a Bug" and provide a justification for it.
"Fight as if you were right and listen as if you were wrong" - Teamwork
David, then says: Its not mentioned in Requirements.
Yes, Requirements are source of Knowledge, to learn about the product based on the stakeholder ideas.
But Tony uses Critical thinking to recognize the problem.
David, then says: Who told you think Critical, was it written out in requirements ?
Tony Answers: Oracle.
"Its not about Oracle - Database"
David asks: What is this Oracle?
An Oracle is a principle or mechanism used to compare and evaluate the product against the requirement to recognize the problem.
"Every problem cant be taken from requirements but Critical thinking can help to use Oracles to Recognize the problem"
Here is one scenario, which is common between teams.
I suppose Developer with "David" and Tester as "Tony". These two persons have two years of experience in their respective roles.
A day appeared, Tony logs a bug in bug triage based on the thinking, how system or application under test can fail and proceeds to next steps.
Next moment, David marks as Not a Bug.
Tony then meets David, and asks why did you mark it as "Not a Bug" and provide a justification for it.
"Fight as if you were right and listen as if you were wrong" - Teamwork
David, then says: Its not mentioned in Requirements.
Yes, Requirements are source of Knowledge, to learn about the product based on the stakeholder ideas.
But Tony uses Critical thinking to recognize the problem.
David, then says: Who told you think Critical, was it written out in requirements ?
Tony Answers: Oracle.
"Its not about Oracle - Database"
David asks: What is this Oracle?
An Oracle is a principle or mechanism used to compare and evaluate the product against the requirement to recognize the problem.
"Every problem cant be taken from requirements but Critical thinking can help to use Oracles to Recognize the problem"