[
https://issues.jboss.org/browse/WFCORE-1673?page=com.atlassian.jira.plugi...
]
Martin Schvarcbacher updated WFCORE-1673:
-----------------------------------------
Description:
*Description:*
Test plan to add integration tests for "use-legacy-override", behavior of
default-controller and default-protocol defined in jboss-cli.xml when connecting to a
server. Additionally test that the correct port is used according to specified protocol
when no port is explicitly specified.
Added integration tests for server aliases defined in jboss-cli.xml
Usage in bin/jboss-cli.xml:
{code:xml}
<controllers>
<controller name="ServerOne">
<protocol>http-remoting</protocol>
<host>localhost</host>
<port>9990</port>
</controller>
</controllers>
{code}
{code:bash}
./bin/jboss-cli.sh --controller=ServerOne --connect
{code}
+*TEST PLAN for controller aliases*+
# set invalid default controller configuration to ensure all settings are being loaded
only from controller aliases
# connect to controller alias with all options (protocol, hostname, port) specified
# protocol specified in <default-controller> overrides <default-protocol> when
calling --connect without --controller
# empty jboss-cli.xml configuration uses implicit settings for both default controller and
controller alias
*+TEST PLAN for use-legacy-override+*
{code:shell}
./bin/jboss-cli.[sh/bat] --connect [--controller=localhost:$TESTED_PORT]
{code}
* <default-protocol use-legacy-override=true> && no protocol specified
&& port=9999 → use remoting://
* <default-protocol use-legacy-override=false> && no protocol specified
&& port=9999 → use protocol from <default-protocol>
* no protocol specified in <default-controller> → use <default-protocol>
* <default-protocol> is overridden by protocol defined in <default-controller>
(JBEAP 7.0.0 new element)
was:
Added integration tests for server aliases defined in jboss-cli.xml
Usage in bin/jboss-cli.xml:
{code:xml}
<controllers>
<controller name="ServerOne">
<protocol>http-remoting</protocol>
<host>localhost</host>
<port>9990</port>
</controller>
</controllers>
{code}
{code:bash}
./bin/jboss-cli.sh --controller=ServerOne --connect
{code}
+*TEST PLAN for controller aliases*+
# set invalid default controller configuration to ensure all settings are being loaded
only from controller aliases
# connect to controller alias with all options (protocol, hostname, port) specified
# protocol specified in <default-controller> overrides <default-protocol> when
calling --connect without --controller
# empty jboss-cli.xml configuration uses implicit settings for both default controller and
controller alias
*+TEST PLAN for use-legacy-override+*
{code:shell}
./bin/jboss-cli.[sh/bat] --connect [--controller=localhost:$TESTED_PORT]
{code}
* <default-protocol use-legacy-override=true> && no protocol specified
&& port=9999 → use remoting://
* <default-protocol use-legacy-override=false> && no protocol specified
&& port=9999 → use protocol from <default-protocol>
* no protocol specified in <default-controller> → use <default-protocol>
* <default-protocol> is overridden by protocol defined in <default-controller>
(JBEAP 7.0.0 new element)
Testsuite: tests for CLI controller aliases
-------------------------------------------
Key: WFCORE-1673
URL:
https://issues.jboss.org/browse/WFCORE-1673
Project: WildFly Core
Issue Type: Task
Components: CLI, Test Suite
Reporter: Martin Schvarcbacher
Assignee: Martin Schvarcbacher
Priority: Minor
*Description:*
Test plan to add integration tests for "use-legacy-override", behavior of
default-controller and default-protocol defined in jboss-cli.xml when connecting to a
server. Additionally test that the correct port is used according to specified protocol
when no port is explicitly specified.
Added integration tests for server aliases defined in jboss-cli.xml
Usage in bin/jboss-cli.xml:
{code:xml}
<controllers>
<controller name="ServerOne">
<protocol>http-remoting</protocol>
<host>localhost</host>
<port>9990</port>
</controller>
</controllers>
{code}
{code:bash}
./bin/jboss-cli.sh --controller=ServerOne --connect
{code}
+*TEST PLAN for controller aliases*+
# set invalid default controller configuration to ensure all settings are being loaded
only from controller aliases
# connect to controller alias with all options (protocol, hostname, port) specified
# protocol specified in <default-controller> overrides <default-protocol>
when calling --connect without --controller
# empty jboss-cli.xml configuration uses implicit settings for both default controller
and controller alias
*+TEST PLAN for use-legacy-override+*
{code:shell}
./bin/jboss-cli.[sh/bat] --connect [--controller=localhost:$TESTED_PORT]
{code}
* <default-protocol use-legacy-override=true> && no protocol specified
&& port=9999 → use remoting://
* <default-protocol use-legacy-override=false> && no protocol specified
&& port=9999 → use protocol from <default-protocol>
* no protocol specified in <default-controller> → use <default-protocol>
* <default-protocol> is overridden by protocol defined in
<default-controller> (JBEAP 7.0.0 new element)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)