Answer Posted / ravindramallikarjun
Test case
From Wikipedia, the free encyclopedia
Jump to:navigation, search
This article is about the term in software engineering. For
the use of the term in law, see Test case (law).
This article does not cite any references or sources.
Please help improve this article by adding citations to
reliable sources. Unsourced material may be challenged and
removed. (July 2009)
Portal-puzzle.svg Software Testing portal
A test case in software engineering is a set of conditions
or variables under which a tester will determine whether an
application or software system is working correctly or not.
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 functioning correctly. Test cases are often
referred to as test scripts, particularly when written.
Written test cases are usually collected into test suites.
Contents
[hide]
* 1 Formal test cases
* 2 Informal test cases
* 3 Typical written test case format
* 4 References
* 5 Test Case Management Software
* 6 External links
[edit] Formal test cases
In order to fully test that all the requirements of an
application are met, there must be at least two test cases
for each requirement: one positive test and one negative
test; unless a requirement has sub-requirements. In that
situation, each sub-requirement must have at least two test
cases. Keeping track of the link between the requirement and
the test is frequently done using a traceability matrix.
Written test cases should include a description of the
functionality to be tested, and the preparation required to
ensure that the test can be conducted.
A formal written test-case is characterized by a known input
and by an expected output, which is worked out before the
test is executed. The known input should test a precondition
and the expected output should test a postcondition.
[edit] Informal test cases
For applications or systems without formal requirements,
test cases can be written based on the accepted normal
operation of programs of a similar class. In some schools of
testing, test cases are not written at all but the
activities and results are reported after the tests have
been run.
In scenario testing, hypothetical stories are used to help
the tester think through a complex problem or system. These
scenarios are usually not written down in any detail. They
can be as simple as a diagram for a testing environment or
they could be a description written in prose. The ideal
scenario test is a story that is motivating, credible,
complex, and easy to evaluate. They are usually different
from test cases in that test cases are single steps while
scenarios cover a number of steps.
[edit] Typical written test case format
A test case is usually a single step, or occasionally a
sequence of steps, to test the correct
behaviour/functionalities, features of an application. An
expected result or expected outcome is usually given.
Additional information that may be included:
* test case ID
* test case description
* test step or order of execution number
* related requirement(s)
* depth
* test category
* author
* check boxes for whether the test is automatable and
has been automated.
Additional fields that may be included and completed when
the tests are executed:
* pass/fail
* remarks
Larger test cases may also contain prerequisite states or
steps, and descriptions.
A written test case should also contain a place for the
actual result.
These steps can be stored in a word processor document,
spreadsheet, database or other common repository.
In a database system, you may also be able to see past test
results and who generated the results and the system
configuration used to generate those results. These past
results would usually be stored in a separate table.
Test suites often also contain
* Test summary
* Configuration
Besides a description of the functionality to be tested, and
the preparation required to ensure that the test can be
conducted, the most time consuming part in the test case is
creating the tests and modifying them when the system changes.
Under special circumstances, there could be a need to run
the test, produce results, and then a team of experts would
evaluate if the results can be considered as a pass. This
happens often on new products' performance number
determination. The first test is taken as the base line for
subsequent test / product release cycles.
Acceptance tests, which use a variation of a written test
case, are commonly performed by a group of end-users or
clients of the system to ensure the developed system meets
the requirements specified or the contract. User acceptance
tests are differentiated by the inclusion of happy path or
positive test cases to the almost complete exclusion of
negative test cases.
| Is This Answer Correct ? | 1 Yes | 0 No |
Post New Answer View All Answers
Do we have any certifications for ETL Testing ?
Need to know about Quality Center in brief
what is the most critical bug u have to find in ur project.My application is ERP based,in this purchase module is there.plz tell me the answer?
How to find bug in photos and videos ??
What r the features,u take care in prototype testing?
can we do database testing in manual testing? then how we write the test case?
How can you do the scalability testing?
What is an entry criteria?
HOW TO CREATE SRS REVIEW REPORT TO PL?
What is the difference between qa, qc, and testing?
1.What is bidirectional traceability ??? and how it is implemented? 2.What is Automation Test frame work ? 3. Define the components present in test strategy? 4. Define the components present in test plan? 5. Have u written Test plan ?…. thank u!plz reply........
How would u test and automate an Antivirus application ?
please send me interview questions asked in google in testing - manual
How do you know the code has met specifications?
Define brain stromming?
