Bug 1311450 - Test Case Failure while executing TicketMonster application tests
Summary: Test Case Failure while executing TicketMonster application tests
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Other
Version: 6.3.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: jboss-set
QA Contact: Pavel Slavicek
eap-docs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-24 09:50 UTC by deepalic
Modified: 2016-02-24 12:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-24 12:37:02 UTC
Type: Bug

Attachments (Terms of Use)
Console log (3.98 KB, text/plain)
2016-02-24 09:50 UTC, deepalic 		no flags Details
TestCaseLog (9.23 KB, text/plain)
2016-02-24 09:51 UTC, deepalic 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description deepalic 2016-02-24 09:50:45 UTC 
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:
Consistent

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 09:51:20 UTC 
Created attachment 1130141 [details]
TestCaseLog
Comment 2 Ivo Studensky 2016-02-24 12:37:02 UTC 
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.