What is a test condition ?
- 6 Answers
- 47313 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / 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 |
Answer / anu
Condition given to the test data is called test condition.
for example:Username field Condition will be like it should
start with alphabet, should contain atleast 2 digits
without any special charecters.So condition for Username
field will be something like Ap22le.Using this condition
you will check actual and expected result.
| Is This Answer Correct ? | 27 Yes | 8 No |
Answer / kanishk
An item or event of a software or component that can be
verified by one or more test cases.
| Is This Answer Correct ? | 16 Yes | 3 No |
Answer / jahas n
In a simple way ...Test condition is the condition which is the Process that we should follow to test an application
| Is This Answer Correct ? | 5 Yes | 1 No |
Answer / mfsi_priyankaa
An item or event of a component or system that could be
verified by one or more test cases, e.g. a function,
transaction, feature, quality attribute, or structural element.
| Is This Answer Correct ? | 4 Yes | 1 No |
Answer / rajesh pothina
The input ,excepted result and the actual result are the
test conditions.
| Is This Answer Correct ? | 5 Yes | 33 No |
Can anybody describe what might be the reasons or situations where the developer doesn't accept a bug as a bug , raised by tester ?
ad-hoc testing is not organized, it's not repeatable, it can't be tracked, and when it's complete, there's no proof that it was ever done. is it?
hi, this is an interview question."what are the testing skills that u have ?". how can i answer to this one ? reply me correct answer plzzzzzzz
what is buddy testing ?
how we do system testingf project?
What do you mean by peer rieviews
Hi, I got an offer with maveric systems and I have around 3.5 years of work experience. But inspite of that they are asking to sign a bond for 2 years and to pledge all the original certificates for that bond. Can anybody please advice me whether its a good company or not and can i go ahead with this?
Please anybody explain the interaction of tester with developers and team lead regarding bugs or any issue, how they interact? How they discuss... Plz be clear in detail
6 Answers eSymbiosis, Infosys,
What is difference between Client-Server and Web based architecture.?
2 Answers Disha Tech, Verisoft,
what is agile testing with example
Explain briefly your project.
what is the use case ? what is the use of the use case ?
Automation Testing 
