Uploaded by portnovschool on Feb 21, 2009
The "What is test case?" question is a very common interview question in Software Testing field.
Taking QA class in a college you might be just fine giving THE definition provided in that course. But, for the purpose of a successful job interview you might come up with a brief discussion, showing the multitude of views and concepts.
The Institute of Electrical and Electronics Engineers defines test case as "A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement."
Wikipedia provides slightly different definition: "Set of conditions or variables under which a tester will determine whether an application or software system meets specifications."
The difference between two is "verifying compliance with requirement" versus "meeting specification". In the ideal world we have perfectly defined requirements. In the real world we might have literally none. So, in QA we might deal with actual requirements or with self-inflicted, self-imposed requirements. No matter how well the formal requirements or specifications are defined Software tester will develop and execute test cases in the course of testing the software product.
To the testers who are developing the test cases it is an instrument of planning for future testing. Many companies are outsourcing execution of test procedures. As a result we are seeing more and more people for whom test cases are about execution, not planning. This is why the Internet is now full of definitions like "test cases is a document that describes step-by-step process how to test the application". Step-by-step process of executing something developed by someone else. You can mention that as one of the existing views, but in Silicon Valley you should not make it your preferred definition.
Practically all the definitions imply that test cases will either fail or pass. And that is how tester verifies the requirement. But there is a very important difference in viewing or not viewing test case as smallest test with no more than one verification inside. In some companies one requirement has just one test case assigned. And that single test case will have many verifications inside. Wikipedia expresses different opinion:
1. "there must be at least one test case for each requirement". By the way. Think about how many negative test cases we might have for just one positive test case
2. "test cases are usually collected into test suites". Not into other test cases.
There is an absolutely amazing definition I found on PC Magazine web site: "A test case validates one or more system requirements and generates a pass or fail". Wow!!! It is not even one test case for one requirement. It is about one test case validating multiple requirements.
Think about it. You come to an interview. They ask you "What is test case?". And the person who asks the question might be a proponent of any of the views we discussed so far. The only way not to take the risk of coming with your favorite definition is giving an overview of existing concepts. Make sure you tell the interviewer that you do not know exactly how that QA team defines the term, but you will be happy to adopt their definition.
-
44 likes, 3 dislikes
Link to this comment:
14:51Basics of Manual testing part-1by shaiksw17,902 views
3:59Answers to 5 toughest job interview questionsby 133Antony84,108 views
44:32Software QA Testing Online Training course - 1/20by portnovschool9,210 views
7:46Mock interview Online Qa training interview que...by h2kinfosys4,941 views
4:48Basic Software Testing Interview Questionsby davidkood40,630 views
2:00Top 10 Tips to Get Software Testing Jobsby davidkood44,840 views
37:20Software QA Online Training course - 2/20 - GUI...by portnovschool4,768 views
3:17Virtual interview - based on Google interviewsby vinterview29,522 views
9:5750 Job interview Mistakes (Interview killers) -...by portnovschool6,979 views
5:21Software Testing Interview Questions Tutorialby CreativeLucky32,060 views
4:38Tell me about yourself - job interview question...by JobInterviewTips89,155 views
3:50Test Caseby de515121,034 views
9:43generate test casesby clemensreijnen46,715 views
1:23:37Testing for beginners [RUS] 2008by musttodont2,245 views
8:31Understanding Requirements, Scenarios, Test Cas...by IISTtestingtips8,529 views
5:23Two Sample Interviewsby jem786466,235 views
5:46HP: Quality Center Flash Demoby HewlettPackardVideos29,432 views
8:17Software Testing Interview Questions & Answersby davidkood89,671 views
3:49software Testing Test Plan Overviewby softwaretesting1097,300 views
- Loading more suggestions...
Thank you for this comprehensive and definitive discussion about test cases. Showing a spectrum perspectives of TC and showing the willingness to adapt to the environment of interviewing companies. A good tactic.
I think a TC = Precondition + Postcondition + Invariants, and it should be blackboxed and repeatable. A test case is to examine the behaviour of modules against their specifications.
In unit test, a specification need not be documented, but perceived in programmers' mind.
wclient 1 month ago
@straightfaceliar its a set of test inputs, with expected conditions comparable to the expected outputs.
oleghristov 2 months ago
so what is a test case? never did answer the question in plain english.
straightfaceliar 2 months ago
The same person: youtube.com/watch?v=Pah2rhneNeQ
StSmotritel 3 months ago
good advice. tnx!)
serjrubens 7 months ago
I like the fact the he provided the different definitions of Test Case. especially for an interview question, you need more information that just a definition. Thank you
fnabulsi 8 months ago
Very good.
GeeSlimmy1972 1 year ago
very good video - your main point is left until the very end but it is very good advice (and applies to all interviews not just those for a software test job).
evansopen 1 year ago