Bug 724428 (BRMS-373) - Test scenario ignores any edits made after it has been run and cannot be saved.
Summary: Test scenario ignores any edits made after it has been run and cannot be saved.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-373
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: 5.1.0.ER1,5.1.0.ER2
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 5.1.0.ER3
Assignee: Toni Rikkola
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-15 14:16 UTC by Jiri Locker
Modified: 2011-01-14 14:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-04 16:47:49 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 724379 0 high MODIFIED Copying a Test Scenario does not keep the current values 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 724427 0 medium CLOSED Test scenarios imported from 5.0.x repositories display 'Show rules fired' button, which doesn't work anymore 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 724618 0 high CLOSED Unable to Update Test Scenario Fields 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker BRMS-373 0 None None None Never

Internal Links: 724379 724427 724618

Description Jiri Locker 2010-09-15 14:16:39 UTC 
securitylevel_name: Public

Create a new Test scenario. Run it first, then make some edits (define facts in the GIVEN sections, add some EXPECTATIONS). If you save the scenario now and re-open it, you will see a blank scenario -- none of the changes made after the first run were saved.
Comment 1 Jiri Locker 2010-09-15 14:18:03 UTC 
Link: Added: This issue is related to BRMS-372
Comment 2 Jiri Locker 2010-09-15 14:18:03 UTC 
Link: Added: This issue is related to BRMS-325
Comment 3 Jiri Locker 2011-01-14 14:42:14 UTC 
Link: Added: This issue Cloned to BRMS-524
Note You need to log in before you can comment on or make changes to this bug.