Bug 961523 - Add testing for slave Host Controller join to domain testsuite DefaultConfigSmokeTestCase
Summary: Add testing for slave Host Controller join to domain testsuite DefaultConfigS...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management, Testsuite
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER2
: EAP 6.1.1
Assignee: Brian Stansberry
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-09 19:52 UTC by Brian Stansberry
Modified: 2013-09-16 20:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-16 20:20:02 UTC
Type: Task
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-1324 0 Major Resolved Add testing for slave Host Controller join to domain testsuite DefaultConfigSmokeTestCase 2015-12-15 16:57:20 UTC

Description Brian Stansberry 2013-05-09 19:52:23 UTC
In the managed domain test suite, there is no testing of a slave HC joining a domain using our *standard config files*. There is, of course, already testing of slaves joining a domain, but those tests use custom testsuite-specific configurations. DefaultConfigSmokeTestCase tests the "domain.xml + host.xml" config set, so a master running servers is tested. But "domain.xml + host-master.xml" is not tested nor is "host-slave.xml". These latter two can be tested in combination, and that closes the hole.

This additional testing would have caught the https://bugzilla.redhat.com/show_bug.cgi?id=961273 regression.

Comment 4 Rostislav Svoboda 2013-06-07 10:18:59 UTC
QA_ACK granted, AS TS enrichment.


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