Bug 1270258 - Arquillian tests fail on java.lang.ClassCastException
Summary: Arquillian tests fail on java.lang.ClassCastException
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Quickstarts
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER5
: 6.2.0
Assignee: Bill Rainford
QA Contact: Tomas David
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-09 12:24 UTC by Tomas David
Modified: 2020-03-27 20:10 UTC (History)
1 user (show)

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


Attachments (Terms of Use)
stacktrace (8.66 KB, text/plain)
2015-10-09 12:24 UTC, Tomas David
no flags Details

Description Tomas David 2015-10-09 12:24:16 UTC
Created attachment 1081323 [details]
stacktrace

Description of problem:
When arquillian quickstarts tests are executed, tests fail on java.lang.ClassCastException. See stacktrace in attachment.

Failing tests: 
HouseFireTest.java in stateful-ksession quickstart
TransactionsTest.java in helloworld-cep quickstart

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

How reproducible:
-

Steps to Reproduce:
1. Execute one of the mentioned tests. (mvn clean install test -Parq-jbossas-remote)

Actual results:
Tests failed with java.lang.ClassCastException.

Expected results:
Tests pass.

Additional info:
It looks like it is similar to this problem: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1193473.

Comment 1 Petr Široký 2015-10-13 10:41:02 UTC
Fixed on 6.2.x branch (correct branch for Quickstarts):
https://github.com/jboss-developer/jboss-brms-quickstarts/commit/32306d6a1a484

Comment 2 Tomas David 2015-10-15 08:43:15 UTC
The fix is not included in ER4.

Comment 3 Lukáš Petrovický 2015-10-15 10:43:04 UTC
Moving to MODIFIED, since the fix is already committed.

Comment 4 Tomas David 2015-11-04 13:10:19 UTC
Verified on 6.2.0.ER5.


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