Bug 1268286 - TS: cannot run test scenario when using knowledge sessions
Summary: TS: cannot run test scenario when using knowledge sessions
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: ---
Assignee: Toni Rikkola
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-02 12:37 UTC by Jakub Schwan
Modified: 2020-03-27 19:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:03:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jakub Schwan 2015-10-02 12:37:12 UTC
Description of problem:
When there is any kbase defined with ksession, the test scenarios failed. Test result is: "test : Test scenario runner could not find a stateful knowledge session with the name 'ksession'."
No sign of troubles in the server log.

The obvious workaround is to add a kbase without ksession, then test pass.


Version-Release number of selected component (if applicable):
BRMS 6.2 ER3


Steps to Reproduce:
1. Create a new project. Create a test scenario in this project.
2. Run the test scenario.
3. Go to Project editor, Knowledge Base Settings and add a new kbase (optionally make it default) and add ksession(optionally make it default too), save the changes.
4. Go back to the test scenario and run it again.


Actual results:
Step 2: Test runs fine
Step 4: Test failed with message: "Test scenario runner could not find a stateful knowledge session with the name 'ksession'."
 

Expected results:
Step 2: Test runs fine
Step 4: Test runs fine

Comment 2 Jiri Locker 2015-10-02 13:56:48 UTC
I am afraid this is going to be "notabug" or "wontfix". AFAIK if there are any kbases and ksessions defined, then there has to be a single *default stateful* ksession. I am not sure if my description is precisely correct but I can't find the specification.

On the other hand the failure message is rather confusing. It would be helpful if it could guide users to resolve the problem.


Note You need to log in before you can comment on or make changes to this bug.