Write a Positive and Negative test cases for White Board Marker ?
Re: Test cases
I hate questions like that on job interviews. Answering it straight is a crap shoot that both the candidate and the interviewer have the same things in mind. That is why I prefer not asking these types of questions when I inverview people and go more into the process of coming up with the test cases. With out the process, the job candidate could of just been lucky and may not be able to repeat future success.
I like to take a step back and talking it through with the interviewer, What are the requirements? What potential issues and risks I want to address? Then I can go forward with building scenarios before talking about test cases.
If you go straight into writing the test cases and skipping the rest of the QA process, then you'll miss a lot of cases or possible concerns the product owner, developer, project manager, etc... might have.
Simple test cases would be - make sure that if there is a marker with no ink, it will not be able to write anything. If the marker has ink, it should be able to write.
The functionality of marker must able to write and should be reusable.
1. The marker should not break if dropped.
2. The marker stops to work if used on a rough surface.
Years later, I still feel the same. But these days I've thought out the mental framework a little more and have a more step by step process that's repeatable.
First off, jumping into the answer right away will bite you. There's an infinite amount of possibilities, and if you happen to miss 1 that the interviewer is expecting, you're dead. Let's take the above examples.. What is the interviewer was expecting, "Color should be same consistency between 100% full to 95% full.". You miss that case, and you automatically lose the job despite how well all your other test cases are. You might of came up with creative things like, "Marker should work when pressing on the board with soft pressure and hard pressure". It doesn't matter, if you jump straight into answers without describing thought process, you'll automatically be dismissed.
What is the thought process.. Here's a framework you can use. For each, think of what it is, and what it is NOT. (The NOT is just as important as what it is.)
1. The first stems from Requirements. Requirement is composed around these parts:
a. Definition - What defines the product? What should a marker do?
b. Business Specs/Rules - What does business want the marker to be? Is this marker special because it has a larger ink capacity? Does the business expect the marker to work with any tilt? What is the cool feature business wants this marker to have?
c. What are the regulations around the product? - Is it expected to be non-toxic? Should it be created to standards to prevent kids from swallowing the product? In the software world, you'd consider things like PCI, HIPAA, Sarbox etc..
2. 2nd is Competitive Analysis. - What should the product have to adhere to, in order to be competitive to the market place?
a. Reliability - Should this marker have a standard consistency?
b. Durability - How strong should the market head be compared to its competitors?
c. Safety / Security - Should the cap be hard to open for kids under 3 years old? Should the marker be leak proof? This can be broken into 2 parts..
i. Safety for the user against himself.
ii. Safety for the user against malicious party.
d. User friendliness - Is the market easy to hold compared to the competitor?
The cool thing about using a thought framework, is you can explain your thoughts in a logical manner and prove to the interviewer, you can produce consistent results that has a high amount of coverage, despite missing some things he was expecting.
Testcast have a podcast that goes into some detail on testing a wine glass, it's available to listen to here:
Season 1 ? Episode 3 ? Do I get the job? | Testcast is a software testing podcast with Bruce Mcleod and Trish Khoo
There are some similar ideas in using a framework and in asking questions about the product under test.
A test case, in software engineering, is a set of conditions under which a tester will determine whether an application, software system or one of its features is working as it was originally established for it to do. The mechanism for determining whether a software program or system has passed or failed such a test is known as a test oracle. In some settings, an oracle could be a requirement or use case, while in others it could be a heuristic. It may take many test cases to determine that a software program or system is considered sufficiently scrutinized to be released. Test cases are often referred to as test scripts, particularly when written - when they are usually collected into test suites.
Test Cases : - A test case, in software engineering, is a set of conditions under which a tester will determine whether an application, software system or one of its features is working as it was originally established for it to do.
1. The Marker should be able to write.
2. The marker should be re-usable, you can refill it with ink.
1. The tip of the marker should be easily visible, so that one can easily identify the position to hold it in while writing.
2. The Marker has a bar code which is a unique item code for it.
3. The Marker has the name of the comapny which has manufactured it.
4. The body color of the marker should suggest the color of ink of the marker.
5. The color of the marker should be plesant to the eye.
1. The effort required to use the marker should be minimal, i.e. one should not has to stress to write something with it.
2. The Marker should be light to hold, so as easy to use.
3. The Marker can be used to write text, make figures, color a portion of desired object.
4. The marker should exhibit smoothness while use.
5. The tip of the marker should be round and not flat, this would prevent putting stress.
6. The marker's circumference should be wide enough to hold, neither too wide nor too thin.
1. The tip of the marker should be made of a material, so that the efficiency of using ink for writing should be high.
2. The life of the marker should be optimum.
1. The marker should have a cap to protect its ink from drying up, when not in use.
1. The marker should be made of a plastic body which incloses, a cushion soaked with ink, a tip to write and a cap to cover it.
1. The Marker should be able to write on paper as well as White Board.
1. The marker should not break if dropped.
2. The marker stops to work if used on a rough surface for some time.
3. The marker can be used to hit someone.
Product Owner: "Sorry, but to develop all of those requirements would cost us $2.99 per marker, we have to hit a manufacturing cost of $0.99 for it to be viable"
Originally Posted by snehasingh90
While you've broken down the possible requirements into -ilities well, and smashed out a number of test cases based on comparison heuristics, you haven't yet stopped to ask what the customer actually wants - and, given that this is an interview situation, you may come across to the interviewer as a tester that will push their own agenda rather than work with the team to deliver a viable product.
("The color of the marker should be plesant to the eye"? Who gets to decide that?)