| Summary: | Test Scenarios cannot run with invalid .drl file in the project | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Zuzana Krejčová <zkrejcov> | ||||||
| Component: | Business Central | Assignee: | Toni Rikkola <trikkola> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Zuzana Krejčová <zkrejcov> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 6.0.0 | CC: | etirelli, lpetrovi, manstis, zkrejcov | ||||||
| Target Milestone: | ER5 | ||||||||
| Target Release: | 6.0.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-08-06 20:15:44 UTC | 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: |
|
||||||||
Created attachment 798850 [details]
error popup
The real cause of TS failing is that the project cannot be built. Invalid DRL is just one possible cause of this. Can we safely exclude assets with errors from the kbase build? Does it make sense in a rules/processes project to do that? (In reply to Edson Tirelli from comment #3) > Can we safely exclude assets with errors from the kbase build? Does it make > sense in a rules/processes project to do that? Perhaps in the incremental build only? Although it might still cause problems - how about I manage to create a rule with errors and then create another rule that will extend it. If you do exclude assets with errors from the regular build (the one that the user can directly request from the project screen), please, also include some warning visible to the user. Shouldn't it fail? The test scenarios are meant to test the knowledge base. If the kbase can not be built, then none of the test scenarios should pass. The way we notify about this currently is something different. I don't think we should use the error popup for compile errors. They should be reported in the Problems screen. (In reply to Toni Rikkola from comment #6) > Shouldn't it fail? The test scenarios are meant to test the knowledge base. > If the kbase can not be built, then none of the test scenarios should pass. > > The way we notify about this currently is something different. I don't think > we should use the error popup for compile errors. They should be reported in > the Problems screen. Good point. In that case, the Reporting panel should contain some kind of message that the Test Scenario failed, because the kbase couldn't be built - if it is meant to test that. Because in that case, this is a normal result, same as success and same as failure due to e.g. rule not being fired. If the Test Scenarios are meant to test whether the kbase is buildable, it should also be obvious from the way it handles such errors. Similar information about the failed build or rather the reasons for it belongs to the Problems panel as well. (Something should already be there, but due to other reported bugs, it usually isn't visible now.) Pop-up definitely isn't a good idea for this nor is the message currently displayed in it. Test Scenario's "Reporting Panel" now marks tests as failed if kie-wb was unable to obtain build the project and gives an indication of actions for the user to follow. Verified with ER5 - the Reporting panel now shows the message "Unable to get a Session to run tests. Check the project for build errors." and the Problems panel correctly reports troubles with the .drl file. Thanks! |
Created attachment 798849 [details] exception stacktrace Description of problem: Having an invalid .drl file in the project prevents you from running any Test Scenario. It will fail with "Unable to complete your request. The following exception occurred: null." message. Version-Release number of selected component (if applicable): BPMS 6.0 ER3 Steps to Reproduce: 1. Create a new DRL file. 2. Append 'asd;' and save. (Optionally validate and dismiss validation errors.) 3. Create a new Test Scenario. Save it, run it.