TEST CONDITION vs. TEST SCENARIO (same or different?)

Question

I have been searching for the difference between TEST CONDITION vs TEST SCENARIO, it seems that they are the same. Can anyone explain to me the difference? And can you please give me specific examples of each? I just want to understand. Thanks.

Answer 1

I know this question is quite old, but I feel people get too hung up on terminology. There are far too many words to describe 'things' in testing. The ISTQB define a Test Condition as:

'An aspect of the test basis that is relevant in order to achieve specific test objectives.' - http://glossary.istqb.org/search/test%20condition

and the Test Basis is:

'The body of knowledge used as the basis for test analysis and design.' - http://glossary.istqb.org/search/test%20basis

Which in English is: Requirements (Test Basis) inform what you can Test (Test Condition) and from this, you make scenarios/cases.

In the picture below, the requirements define what the 'Functionality' circle is. Such as 'The user must be able to add a note', 'The user must be able to delete a note' etc.

Then from this, there is a main Test Condition of 'Create Note' and further Test Conditions of Add, Edit, Save, Delete and Close then from these conditions you would write test cases that examine this functionality.

Answer 2

Test Scenarios

• Test scenarios are possible ways to test an application. Example: For testing you have so many ways like positive testing, negative testing, BVA etc.
• Test scenarios can be a single or a group of test cases.
• It is important when time is less and most team members understand the details from one line scenarios.
• Good test coverage can be achieved by dividing an application in test scenarios which reduces the complexity.
• Test scenarios are rather vague and covers wide range of possibilities.

Test Conditions

• Test conditions are the constraints that you should follow to test an application. Example: When User Name and Password are valid then application will move forward.
• Test conditions can be a piece of functionality or anything you want to verify. In simple terms the goal of a test case.
• It is an item or event of a system that could be verified by one or more test cases. Eg; transaction, function, structural element etc.
• Good test conditions ensure a system is bug free
• Test conditions are very specific

I took this from: http://www.guru99.com/test-scenario-vs-test-condition.html

There is a lot of information available online, just googling "test condition" gave me a load of comparisons.