Bug 1311450 - Test Case Failure while executing TicketMonster application tests
Test Case Failure while executing TicketMonster application tests
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Other (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: jboss-set
Pavel Slavicek
Depends On:
  Show dependency treegraph
Reported: 2016-02-24 04:50 EST by deepalic
Modified: 2016-02-24 07:37 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-02-24 07:37:02 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Console log (3.98 KB, text/plain)
2016-02-24 04:50 EST, deepalic
no flags Details
TestCaseLog (9.23 KB, text/plain)
2016-02-24 04:51 EST, deepalic
no flags Details

  None (edit)
Description deepalic 2016-02-24 04:50:45 EST
Created attachment 1130140 [details]
Console log

Description of problem:
One test case fails while executing tests for TicketMonster demo application.

Version-Release number of selected component (if applicable):
EAP v6.3.2
TicketMonster sample extracted from jboss-wfk-2.7.0-richfaces-demo.zip

How reproducible:

Steps to Reproduce:
1.Download and extract jboss-wfk-2.7.0-richfaces-demo.zip
2. Configure required maven repo and Start EAP.
3. Execute the command mvn clean package -Parq-jbossas-remotefrom the ticketmonster demo sample folder. 
4. testGetEventMedia(org.jboss.examples.ticketmonster.test.rest.EventServiceTest test fails.

Actual results:
All tests should pass.

Expected results:
One test testGetEventMedia(org.jboss.examples.ticketmonster.test.rest.EventServiceTest fails.

Additional info:
Comment 1 deepalic 2016-02-24 04:51 EST
Created attachment 1130141 [details]
Comment 2 Ivo Studensky 2016-02-24 07:37:02 EST
Please don't file issues for EAP in Red Hat Bugzilla directly. Contact our Support team instead. Thanks.

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