Loading...

XML

Word

Printable

Steps to Reproduce:
Hide

Create a new project in BC

Import [^DriverStatusYoung.rdrl] and [^DriverStatus.scesim] and [^Driver.java]

Go and run [^DriverStatus.scesim] you will see [1]

Go to [^DriverStatusYoung.rdrl] and rename it to "DriverStatusYoungRenamed"

Go to [^DriverStatus.scesim] and run scenario

Expected the same as [1] but DriverStatusYoungRenamed instead of DriverStatusYoungRenamed

Actual Duplicates of rules fired [2]

[1]
[2]
Show
Create a new project in BC Import [^DriverStatusYoung.rdrl] and [^DriverStatus.scesim] and [^Driver.java] Go and run [^DriverStatus.scesim] you will see [1] Go to [^DriverStatusYoung.rdrl] and rename it to "DriverStatusYoungRenamed" Go to [^DriverStatus.scesim] and run scenario Expected the same as [1] but DriverStatusYoungRenamed instead of DriverStatusYoungRenamed Actual Duplicates of rules fired [2] [1] [2]
Workaround:

Workaround Exists
Workaround Description:

Hide

If you build project on project level, then there would no any duplicates and the outdated versions would not be shown

Show
If you build project on project level, then there would no any duplicates and the outdated versions would not be shown
Docs QE Status:
NEW
QE Status:
NEW

Defect: If user renames Guided rules used in Test Scenario, then coverage report shows both original and renamed versions.
See [^renamed.webm]

clones

RHDM-1334 Scenario Coverage Report counts and shows previous names of renamed rules