Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / david
A test condition is a categorized input and a required
output. Conditions are written during a planning period,
before executing a test, and they should act a little like
a checklist of variations that you want to test before we
can confidently say that the code appears to be working.
A single requirement can translate into multiple
conditions, and [depending on the writing style] multiple
requirements may be grouped into a single condition. Also,
types or categories of data often enter into a condition,
but the condition itself is data independent.
In the common User Login example, a high level requirement
would state that a user is able to log into a system (we
will call this requirement 1). A sub requirement of that
might state that the username is not case sensitive (call
this requirement 1.1). Below is an example of some test
conditions that may have been written for these
requirements; conditions A-D:
A) 1 – When a valid username is entered with the correct
password, a user is logged into the system.
B) 1 – When a valid username is entered with the wrong
password, an error message displays.
C) 1 – When an invalid username is entered with a password,
an error message displays.
D) 1, 1.1 – When a valid username is entered in all caps
with the correct password, a user is logged into the system.
E) 1, 1.1 – When a valid username is entered in all
lowercase with the correct password, a user is logged into
the system.
These conditions can be refined into fewer conditions.
Since conditions C and D require a valid username/password
combination, condition A is not necessary. However, if we
tested a valid username in all caps (condition D)with the
wrong password (condition B), then in properly executing
code we should see an error message and the user is not
logged in. Had we tried to combine conditions B and D, we
would have both a fail and a pass for the condition.
Or, if the code that checks a username and password
combination was not implemented properly and the username
was also coded to be case sensitive, then it may be unclear
which condition actually failed (assuming there is one
generic error message for both an invalid username and an
invalid password). A condition should have a single cause
for any failure.
The value of writing out each variation that can be tested
is lessened with more simple processes like the user login
example. The time it takes to document each variation that
we plan to test may take twice as long as the test itself.
However, when we need to test a more complicated system,
like a banking application that manages interest, deposits,
withdrawls, etc for a large number of clients, test
conditions are necessary for the simple reason that we
might forget to test it if we don't write it down!
| Is This Answer Correct ? | 22 Yes | 2 No |
Post New Answer View All Answers
what is agile model and spiral maodel?pls explain with an example?
Sentence "Working from onsite is effective" is growing in IT field. How do we bring that knowledge to offshore and do an effective job in Offshore?
Relative to other technical groups in the company? Relative to your staff?
Where we have to use perl scripting in Testing approach and its importance
What is boundary value testing? Give an example.
What is difference in between operating system 2000 and os xp?
Beyond the customary advantages of having a testing group, what are the benefits does a company receive from a well run, automated testing group?
What are cookies?
what is the difference between PEGA based web application testing versus web application testing?
What is an exit criteria?
What icon is used in WinRunner to get an explanation of the syntax of TSL?
Describe some staff conflicts you have handled.
How to explain the Insurance project in the interview?
what are the common errors while doing integration,system,functional,regression,user acceptance testing? can anybody please let me know the answers it is too urgent???
Information about Automated Software Installer
