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
Can any one share the domain knwoldege of Telecom Jeeva jeevachr@gmail.com
what are risks and contigencies(solutions) of an ecommerce (online shopping and bidding project)application?we describe this in Test plan can anyone tell me abt this?
what is the use of l10n testing?
Hi,all i have a desktop App. which have a feature, It's a demo version if u want full version then u have to perches it. Pls give me some idea ASAP how can i break the App.
What is validation in software testing?
What is mean by Schedule report who is the responsible for generated that one ?
is it not possible to automate full project??what r the parts in project that cant be automated(tht has to be done manually)?
What is Dynamic Binding and Dynamic Loss?
Can you explain steps in function points?
i) functional test cases can we consider for regression test ? or we have to write separet test cases for regression test ? ii) How to write the system test case and what are the technique shall we have to follow ?
what types of bugs will we find out in banking projects
Hello. I am not here to answer your question. I jus found a job as software QA engr. And i am totally new to software testing. So can someone pls help me in the following scenario? there is this registration screen, and it contain: One textbox called Nickname which only accept alphanumerical One textbox called Contact which only accept numerical, One textbox called Email which can be filled with alphanumerical and symbol and One button called Register now becos there is so many textboxes, where i can filled with alphabet, number, symbol, "just space", leading zeros, leading space. there will be lots of combination. can someone pls help.. i will be appreciated if u can post the test case of the scenario i mentioned. Lots of Thanks
from where do u collect test data if u miss some data what will happen
What is the full form of cmmi?
What is the responsibility of programmer’s vs QA?
