| Summary: | Testcases in Guvnor doesn't clean up correctly | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Toshiya Kobayashi <tkobayas> | ||||
| Component: | BRM (Guvnor) | Assignee: | manstis | ||||
| Status: | VERIFIED --- | QA Contact: | Sona Mala <smala> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5.1.0.CR1, BRMS 5.2.0.GA | CC: | lpetrovi, manstis, rwagner, tkobayas | ||||
| Target Milestone: | ER6 | ||||||
| Target Release: | BRMS 5.3.0.GA | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/BRMS-513 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Running the same test scenario multiple times in the BRMS user interface resulted in subsequent executions returning the same results as the first test scenario. This occurred because the results from the original execution were not removed. This issue has been resolved by ensuring the results from the original execution are cleared before subsequent runs.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Toshiya Kobayashi
2010-12-14 10:29:55 UTC
Attachment: Added: repository_export-brms510-GUVNOR-853.zip Steps to Reproduce: Added: - Import attached repository_export-brms510-GUVNOR-853.zip - Run test scenario named t1 - Modify the value in GIVEN section and run again. - You will see the test still run successfully I haven't tested with drools trunk yet because current guvnor build fails to deploy. Link: Added: This issue incorporates GUVNOR-853 I found the issue still exists in Drools 5.2.0.M1 so re-opened GUVNOR-853 and added steps to reproduce etc. gss_prioritized Sorry for responding late. I confirmed that this issue still exists in BRMS 5.3.0.ER3. Please check the steps to reproduce in the first description. Update status to ON_QA. Please verify them against ER6. Verified: - import attached repository - run scenario - change value of object's attribute - run scenario -> second run fails -> without errors alert Hi Mike, For the release notes could you let me know how this issue was resolved. We need to let customers know about any changes in the code that could affect their systems. Sure, no problem Lee. It was fixed by ensuring Test Scenario results from previous runs of a given Test Scenario were cleared before running again.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Running multiple test scenarios in the BRMS user Interface resulted in subsequent test scenarios returning the same results as the first test scenario. This occurred because the results from the original scenario were not removed. This issue has been resolved by ensuring the results from the original test scenario are cleared before subsequent tests are run.
Thanks Mike. Hi Lee, I'd suggest one small alteration to your release notes, something like this:- Running the same test scenario multiple times in the BRMS user Interface resulted in subsequent executions returning the same results as the first execution. This occurred because the results from the original execution were not removed. This issue has been resolved by ensuring the results from the original execution are cleared before subsequent runs. Basically, the problem involved running the same test multiple times. Your release note suggests is was running different tests. AFAIK, this was not the case (and the original report does not suggest this).
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-Running multiple test scenarios in the BRMS user Interface resulted in subsequent test scenarios returning the same results as the first test scenario. This occurred because the results from the original scenario were not removed. This issue has been resolved by ensuring the results from the original test scenario are cleared before subsequent tests are run.+Running the same test scenario multiple times in the BRMS user interface resulted in subsequent executions returning the same results as the first test scenario. This occurred because the results from the original execution were not removed. This issue has been resolved by ensuring the results from the original execution are cleared before subsequent runs.
Updated, thanks Mike. |