what is test condition?how do u rank a test condition?
Answers were Sorted based on User's Feedback
Answer / venkat
Breaking the functionality into sublime parts and analyzing
each part and deriving conditions to test it can be called
as a test conditon.
in some instances a condition can have multiple scenarios.
In some a condition can be a subset of a scenario.
Ranking is based on the seriousness of the feature to be
tested and it's impact on the overall functionality.
| Is This Answer Correct ? | 24 Yes | 2 No |
Answer / sherry t
test condition: 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.
(This answer is defined in ISTQB glossary.)
| Is This Answer Correct ? | 23 Yes | 4 No |
Answer / suman
test condition is like as decision table . it's retrived for
business logic.
test condion in login screen :
RL1 RL2 RL3
user name: T T F
pwd: T F T
RESULT: T F F
if my answer wrong correct me
| Is This Answer Correct ? | 9 Yes | 4 No |
Answer / abdullah
A system state or circumstance created by proceeding through
some combination of steps, substeps, or actions in a test
case. The term is sometimes also used to refers to the
steps, substeps, or actions themselves.
| Is This Answer Correct ? | 4 Yes | 1 No |
Answer / zeus
Test conditions are high level requirements,derived from
business / technical requirements.
Test scenarios are derived from test conditions.
Test scripts /Test cases are derived from Test scenarios.
| Is This Answer Correct ? | 16 Yes | 14 No |
Answer / grsmrc2118@yahoo.com
hi srinivas could u give some clear answer
there are total of 45 conditions in ur application
but u wrote around 135
it means
and any way give some example for conditions
and i need condition what exists in ur project plzz
and if u have any thing on qtp plzz send to my mail id
i hope u could able to send
bye
| Is This Answer Correct ? | 7 Yes | 6 No |
Answer / venkat
Hi srinivas374,
I am really happy with your answer. Here I want to clarify
few of things.
Test condition: If we want to complete the test condition,
we have to prepare the collection of test case and execute
to all.
In the same way Test Scenario: if we want to execute the
test scenario, we have to prepare the collection of test
case and execute to all.
So here where you have to differentiate test condition and
test scenario.
Regards,
Venkat
sarulvenki@rediffmail.com
| Is This Answer Correct ? | 3 Yes | 2 No |
Answer / ahmed khalil
test conditions (what can be tested & prioritize)
• A test condition is an item or event that could be
verified by a test. There will be many different test
conditions for a system, and for different categories of
test, such as functionality tests, performance tests,
security tests, etc.
• Testing techniques help testers derive test
conditions in a rigorous and systematic way.
• testing techniques such as equivalence
partitioning, boundary value analysis, cause-effect
• Test conditions are descriptions of the
circumstances that could be examined. They may be
documented in different ways, including brief sentences,
entries in tables, or in diagrams such as flow graphs.
• The activity of identifying test conditions is best
done in parallel with the associated development
activities, i.e. on the left-hand side of the V-model.
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / khiet nguyen
A test condition is derived from a condition in the
requirements statement or functional statement that when
implemented it causes the system to behaves its unique
behavior.
The condition may come from a logic decision, a special
input value or an equivalent class of input value(s), an
event or a group of events that trigger a system execution,
or the change (in system configuration, operating system, or
software version) that may cause different system behavior.
Test condition may be ranked based on the level of testing
it was derived for ie. Unit test, Integration test, system
test, or system integration test.
| Is This Answer Correct ? | 2 Yes | 2 No |
Answer / peter edmond
When we perform testing we need to measure the completeness
for our testing. This is done by measuring the Breadth of
Testing (How much of the system as we going to test). This
is done via Test Conditions. We also need to measure the
depth of tesing (How many different data values or data
sets are needed to ensure complete testing of the test
condition or feature). These test cases are derived using
test design techniques such as Equivalence Partitioning,
boundary value analysis, decision tables, pairwise testing,
use cases, classification trees.
Tyoically atest condition is expressed in natural language
(English) and will start with the words "To show that"
or "To demonstrate"
Examples "To show that the system allows valid users to
logon to the system"
"To show that invalid users are not allowed to logon"
The collection of test conditions should cover all areas of
the system functional and non-functional features that you
need to test. Hope this helps
| Is This Answer Correct ? | 0 Yes | 0 No |
what is telcom Testing and how is it performed is the same methodolgy used for telecom testing as its used for web application
What is fuzz testing?
what is performance testing
what is the difference between testcase and test scenario? Please give one example.
How you will report a bug if u r doing adhoc testing..u are hopping from 1 link to 2nd...so on till 100th link and then there is bug..how will u report this bug...will you write all 100 steps?
how many types of functions in qtp
Hi, Can anybody send some test scenarios or testcases sample for Finance domain on sales and accounting application. I am very new to Finance domain. Or else please send to my mailID "manojdalai2004@gmail.com". Thanks in Advance, Manoj
can anybody pls tell me that what type of interaction takes place or what type of discussions or questions take place between a tester and client regarding the project.
How do you test if you have minimal or no documentation about the product?
How do you test if you have minimal or no documentatioabout the product? How do you decide when you have tested enough? How do you determine what to test?
What do you do if the bug that you found is not accepted by the developer and he is saying its not reproducible.
How is the communication with the developers for the Unit Testing?