Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 340680

Summary: Incorrect icon decoration on TestStep in Test Suite Browser
Product: [Technology] Jubula Reporter: Tobias Eiss <Tobias.Eiss>
Component: UIAssignee: Markus Tiede <markus.tiede>
Status: CLOSED FIXED QA Contact: Oliver Goetz <Oliver.Goetz>
Severity: normal    
Priority: P1 CC: alexandra.schladebeck, markus.tiede
Version: unspecified   
Target Milestone: Indigo SR1   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Tobias Eiss CLA 2011-03-22 12:30:57 EDT 
Build Identifier: 5.0

After add a new TestStep in a new TestCase in a new TestSuite and map the components, disappear the "red X"-decoration on the TestSuite because not on the new TestSteps.

You can reproduce if you follow the steps:
 * add new TestSuite
 * add new TestCase
 * add new TestStep in the new TestCase
 * reference the TestStep
 * map a component
 * save
 * expand TestSuite

Reproducible: Always

Steps to Reproduce:
1. add new TestSuite
2. add new TestCase
3. add new TestStep in the new TestCase
4. reference the TestStep
5. map a component
6. save
7. expand TestSuite
Comment 1 Oliver Goetz CLA 2011-07-28 06:49:27 EDT 
The incorrect decoration also appears in the TCB. Even though all components have been mapped and all necessary test data has been entered the Test Steps are still decorated with a red X in the TSB. You can still start your test runs but this behaviour can easily confuse users as you can see in this post:
http://www.eclipse.org/forums/index.php/t/225382/
Comment 2 Alexandra Schladebeck CLA 2011-08-22 02:29:50 EDT 
I'm increasing the priority of this, as it has caused confusion in various support and forum threads.
Comment 4 Alexandra Schladebeck CLA 2011-09-12 09:39:48 EDT 
Test Step nodes now generally only show a red cross if data / component names are incomplete. 

Through this fixed behaviour, a new error has come to light:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=357375

As this isn't related to the original issue, I'm closing this bug.