[jboss-cvs] JBossAS SVN: r109411 - tags/CC_JBPAPP_5_1_0_testsuite/testsuite/src/resources/cc.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Nov 22 13:16:20 EST 2010
Author: pskopek at redhat.com
Date: 2010-11-22 13:16:19 -0500 (Mon, 22 Nov 2010)
New Revision: 109411
Modified:
tags/CC_JBPAPP_5_1_0_testsuite/testsuite/src/resources/cc/testCaseMapping_2.0.xml
Log:
Final test descriptions.
Modified: tags/CC_JBPAPP_5_1_0_testsuite/testsuite/src/resources/cc/testCaseMapping_2.0.xml
===================================================================
--- tags/CC_JBPAPP_5_1_0_testsuite/testsuite/src/resources/cc/testCaseMapping_2.0.xml 2010-11-22 18:11:10 UTC (rev 109410)
+++ tags/CC_JBPAPP_5_1_0_testsuite/testsuite/src/resources/cc/testCaseMapping_2.0.xml 2010-11-22 18:16:19 UTC (rev 109411)
@@ -15,8 +15,11 @@
<!-- Standard EAP testsuite to TOE Security Functionality Interface mapping -->
<testSuite name="EAP">
<testCase name="org.jboss.test.deployers.web.test.WEBDeploymentUnitTestCase">
- <desc></desc>
+ <desc>Test case to check web deployer works correctly.</desc>
<test name="testWEBDeployment">
+ <desc>Test objective: Test if deployed war file created all necessary structures.
+ Expected result: All expected subdeployments of the war file have to be created.
+ </desc>
<TSFI>tsfi.app.web.xml</TSFI>
</test>
</testCase>
@@ -37,7 +40,7 @@
Testcase that unit tests the cloneability of various JBossSX
Principal/Groups
- Also does a test of the serverside Subject deep copy via a mutable
+ Also does a test of the server side Subject deep copy via a mutable
Principal</desc>
<test name="testSubjectCloning">
<desc>Test Objective: Test the Deep Copy of Subjects by the JaasSecurityManager via a test servlet deployed.
@@ -47,65 +50,106 @@
</test>
</testCase>
<testCase name="org.jboss.test.security.test.EJB3SpecUnitTestCase">
- <desc></desc>
+ <desc>This TestCase validates the security behavior of protected EJB3 beans.</desc>
<test name="testAdministratorMethodAccess">
- <desc></desc>
+ <desc>
+ Test Objective: Tests accessing protected methods using a client that has the Administrator role.
+ Test is conducted for stateless and statefull beans.
+ Expected Result: An administrator should have access to all methods but invokeUnavailableMethod (@DennyAll).
+ </desc>
<TSFI>tsfi.ann.DenyAll</TSFI>
<TSFI>tsfi.ann.PermitAll</TSFI>
<TSFI>tsfi.ann.RolesAllowed</TSFI>
<TSFI>tsfi.cfg.deploy.security.security-policies-jboss-beans.xml</TSFI>
</test>
<test name="testRegularUserMethodAccess">
- <desc></desc>
+ <desc>
+ Test Objective: Test accessing regular, administrative and unavailable methods by regular user.
+ Expected Result: A regular user cannot access administrative methods, but can access regular methods.
+ </desc>
<TSFI>tsfi.ann.DenyAll</TSFI>
<TSFI>tsfi.ann.PermitAll</TSFI>
<TSFI>tsfi.ann.RolesAllowed</TSFI>
<TSFI>tsfi.cfg.deploy.security.security-policies-jboss-beans.xml</TSFI>
</test>
<test name="testGuestMethodAccess">
- <desc></desc>
+ <desc>
+ Test Objective: Test accessing regular, administrative and unavailable methods by guest user (not possessing any roles, but authenticated).
+ Expected Result: A guest user should have access to unprotected methods only.
+ </desc>
<TSFI>tsfi.ann.DenyAll</TSFI>
<TSFI>tsfi.ann.PermitAll</TSFI>
<TSFI>tsfi.ann.RolesAllowed</TSFI>
<TSFI>tsfi.cfg.deploy.security.security-policies-jboss-beans.xml</TSFI>
</test>
<test name="testUnauthenticatedMethodAccess">
- <desc></desc>
+ <desc>
+ Test Objective: Test accessing regular, administrative and unavailable methods by unauthenticated user.
+ Expected Result: An unauthenticated user should have access to unprotected methods only.
+ </desc>
<TSFI>tsfi.ann.DenyAll</TSFI>
<TSFI>tsfi.ann.PermitAll</TSFI>
<TSFI>tsfi.ann.RolesAllowed</TSFI>
<TSFI>tsfi.cfg.deploy.security.security-policies-jboss-beans.xml</TSFI>
</test>
<test name="testRunAsMethodAccess">
- <desc></desc>
+ <desc>
+ Test Objective: A client associated with a RegularUser role invokes the RunAsSession
+ the RunAsSession#invokeRunAs() method delegates the call to the DelegateSession using a
+ @RunAs("Manager") annotation.
+
+ DelegateSession#invokeDelegate() requires a role Manager to run. As the client doesn't have the
+ required role, the call will only succeed if the RunAsSession propagates an identity with the
+ Manager role using a @RunAs annotation.
+ Expected Result: Method RunAsSession#invokeRunAs() has to return non null principal.
+ run-as identity should be the default unauthenticated identity configured in the login module
+ which is in this case "anonymous".
+ </desc>
<TSFI>tsfi.ann.RunAs</TSFI>
<TSFI>tsfi.ann.RolesAllowed</TSFI>
<TSFI>tsfi.cfg.deploy.security.security-policies-jboss-beans.xml</TSFI>
</test>
<test name="testDeclareRoles">
- <desc></desc>
+ <desc>
+ Test Objective: Test if declared roles using @DeclareRoles are testable programmatically.
+ Expected Result: UserA and UserB have to have exactly same roles as they have configured and missing "!negativeRole".
+ </desc>
<TSFI>tsfi.ann.DeclareRoles</TSFI>
<TSFI>tsfi.cfg.deploy.security.security-policies-jboss-beans.xml</TSFI>
</test>
</testCase>
<testCase name="org.jboss.test.ejb3.jbpapp2473.unit.RunAsUnitTestCase">
- <desc></desc>
+ <desc>Testcase testing various aspects of @RunAS and @RunAsPrincipal annotations.</desc>
<test name="testRole1">
- <desc></desc>
+ <desc>
+ Test Objective: Test if @RunAs("manager") really sets principal with role "manager".
+ Expected Result: The bean method isCallerInRole has to return true with "manager" as argument.
+ </desc>
<TSFI>tsfi.ann.SecurityDomain</TSFI>
+ <TSFI>tsfi.ann.RunAs</TSFI>
<TSFI>tsfi.cfg.deploy.security.security-policies-jboss-beans.xml</TSFI>
</test>
<test name="testRole2">
- <desc></desc>
+ <desc>
+ Test Objective: Test if @RunAsPrincipal("jbpapp2473") and @RunAs("manager") really sets principal with role "manager".
+ Expected Result: The bean method isCallerInRole has to return true with "manager" as argument.
+ </desc>
<TSFI>tsfi.ann.RunAsPrincipal</TSFI>
<TSFI>tsfi.ann.SecurityDomain</TSFI>
</test>
<test name="testRunAsManager">
- <desc></desc>
+ <desc>
+ Test Objective: Test if @RunAs("manager") really sets principal "anonymouns".
+ Expected Result: The bean method getCallerPrincipal() has to return "anonymouns" principal.
+ </desc>
+ <TSFI>tsfi.ann.RunAs</TSFI>
<TSFI>tsfi.ann.SecurityDomain</TSFI>
</test>
<test name="testRunAsPrincipal">
- <desc></desc>
+ <desc>
+ Test Objective: Test if @RunAsPrincipal("jbpapp2473") and @RunAs("manager") really sets principal "jbpapp2473".
+ Expected Result: The bean method getCallerPrincipal() has to return "jbpapp2473" principal.
+ </desc>
<TSFI>tsfi.ann.RunAsPrincipal</TSFI>
<TSFI>tsfi.ann.SecurityDomain</TSFI>
<TSFI>tsfi.cfg.deploy.security.security-policies-jboss-beans.xml</TSFI>
@@ -491,31 +535,10 @@
<TSFI>tsfi.port.rmi.jrmp</TSFI>
</test>
</testCase>
-<!--
- <testCase name="org.jboss.test.jca.test.SecurityContextUnitTestCase">
- <desc>Tests of how security context interact with the JCA layer.</desc>
- <test name="testCallerIdentityPropagation">
- <desc></desc>
- <TSFI>tsfi.jdbc</TSFI>
- </test>
- <test name="testConfiguredIdentityPropagation">
- <desc></desc>
- <TSFI>tsfi.port.rmi.jrmp</TSFI>
- </test>
- <test name="testRunAsIdentityPropagationFS">
- <desc></desc>
- <TSFI>tsfi.port.rmi.jrmp</TSFI>
- </test>
- <test name="testRunAsIdentityPropagationDS">
- <desc></desc>
- <TSFI>tsfi.port.rmi.jrmp</TSFI>
- </test>
- </testCase>
--->
<testCase name="org.jboss.test.jmx.test.RMIAdaptorAuthorizationUnitTestCase">
<desc>Authorization of the RMI Adaptor
- * Especially tests the usage of the authorization delegate
- * called as org.jboss.jmx.connector.invoker.ExternalizableRolesAuthorization</desc>
+ Especially tests the usage of the authorization delegate
+ called as org.jboss.jmx.connector.invoker.ExternalizableRolesAuthorization</desc>
<test name="testConfigurableRolesAuthorizedAccess">
<desc>Test objective: Test that a valid jmx-console domain user can invoke operations through the jmx/invoker/AuthenticatedRMIAdaptor
Expected result: Calls have to pass without any exception.
@@ -561,7 +584,7 @@
</testCase>
<testCase name="org.jboss.test.security.test.ClientLoginModuleEJBUnitTestCase">
- <desc></desc>
+ <desc>Tests client login module.</desc>
<test name="testClientLoginModule">
<desc>Test objective: Call BeanA using jduke/theduke
+-- call BeanB switching idenity using ClientLoginModule
@@ -623,23 +646,6 @@
<TSFI>tsfi.port.web.http</TSFI>
</test>
</testCase>
- <!--
- <testCase name="org.jboss.test.security.test.CustomSecurityManagerTestCase">
- <desc>JBAS-2703 : Create a AuthenticationManager/AuthorizationManager
- * plugin testcase
- *
- * This testcase overrides test methods from EJBSpecUnitTestCase (that
- * should not be tested) with noop implementation.
- *
- * Also tests the interaction of the web layer with the EJB layer, with
- * a custom security manager plugin installed.</desc>
- <test name="testWebLayer">
- <desc>Tests the access of a BASIC secured servlet that internally
- * accesses a secured EJB</desc>
- <TSFI>tsfi.port.web.http</TSFI>
- </test>
- </testCase>
- -->
<testCase name="org.jboss.test.security.test.DynamicLoginConfigServiceUnitTestCase">
<desc>Unit tests for the Dynamic Login Config Service</desc>
<test name="testAbsoluteLoginConfigURL">
@@ -1109,6 +1115,10 @@
<desc>Tests the CLIENT-CERT JASPI integration.
</desc>
<test name="ClientCertJaspiWebUnitTestCase">
+ <desc>
+ Test objective: Test if one can access servlet secured using org.jboss.security.auth.spi.BaseCertLoginModule.
+ Expected result: Https response while opening page has to be HTTP_OK.
+ </desc>
<TSFI>tsfi.keystore.usercerts</TSFI>
<TSFI>tsfi.app.jboss-beans.xml</TSFI>
</test>
@@ -1116,9 +1126,17 @@
<testCase name="org.jboss.test.pooled.test.BeanStressTestCase">
<desc>Stress tests for pooled invoker</desc>
<test name="testNewProxy">
+ <desc>
+ Test objective: Test creates number of threads to invoke operation on EJB using pooled invoker through new proxy mechanism.
+ Expected result: No exceptions during the test.
+ </desc>
<TSFI>tsfi.port.rmi.pooled</TSFI>
</test>
<test name="testOldProxy">
+ <desc>
+ Test objective: Test creates number of threads to invoke operation on EJB using pooled invoker through old proxy mechanism.
+ Expected result: No exceptions during the test.
+ </desc>
<TSFI>tsfi.port.rmi.pooled</TSFI>
</test>
</testCase>
@@ -1336,7 +1354,7 @@
</test>
</testCase>
<testCase name="org.jboss.test.aop.test.SecurityUnitTestCase">
- <desc></desc>
+ <desc>Testcase for annotated and XML specified security aspects.</desc>
<test name="testAnnotated">
<desc>Test objective: Test all annotated aspects.
Expected result: All AOP tests has to finish without exception.
@@ -1347,10 +1365,13 @@
</test>
</testCase>
<testCase name="org.jboss.test.jbossts.ASCrashRecovery01.TestWithJPA">
- <desc></desc>
+ <desc>Test case simulating error in connection an leaving open transactions in database.
+ As a next step is resolving them after succesful start of the server.
+ </desc>
<test name="testAction">
- <desc>Test objective:
- Expected result:
+ <desc>
+ Test objective: Test case simulating error in connection an leaving open transactions in database.
+ Expected result: Successful resolving opend transactions and server start.
</desc>
<TSFI>tsfi.api.jta</TSFI>
<TSFI>tsfi.ann.TransactionAttribute</TSFI>
@@ -1359,45 +1380,69 @@
</test>
</testCase>
<testCase name="org.jboss.test.tm.test.TxTimeoutAnnotUnitTestCase">
- <desc>Tests for transaction timeout annotation EJB3 version of TxTimeoutUnitTestCase.</desc>
- <test name="testOverriddenTimeoutExpires">
- <desc>Tests if @TransactionTimeout expires system sends EJBTransactionRolledbackException and transaction is rolled back.</desc>
- <TSFI>tsfi.ann.TransactionTimeout</TSFI>
- <TSFI>tsfi.cfg.conf.jbossts-properties.xml</TSFI>
- </test>
- <test name="testOverriddenTimeoutDoesNotExpire">
- <desc>Tests whether @TransactionTimeout expires greater that wait time of doesn't make transaction to roll back or stay in different status that STATUS_ACTIVE.</desc>
- <TSFI>tsfi.ann.TransactionTimeout</TSFI>
- <TSFI>tsfi.cfg.conf.jbossts-properties.xml</TSFI>
- </test>
+ <desc>Tests for transaction timeout annotation EJB3 version of TxTimeoutUnitTestCase.</desc>
+ <test name="testOverriddenTimeoutExpires">
+ <desc>
+ Test objective: Tests if @TransactionTimeout expires system sends EJBTransactionRolledbackException and transaction is rolled back.
+ Expected result: EJBTransactionRolledbackException has to be caught.
+ </desc>
+ <TSFI>tsfi.ann.TransactionTimeout</TSFI>
+ <TSFI>tsfi.cfg.conf.jbossts-properties.xml</TSFI>
+ </test>
+ <test name="testOverriddenTimeoutDoesNotExpire">
+ <desc>
+ Test objective: Tests whether @TransactionTimeout expires greater that wait time of doesn't make transaction to roll back or stay in different status that STATUS_ACTIVE.
+ Expected result: Transaction has to stay in STATUS_ACTIVE.
+ </desc>
+ <TSFI>tsfi.ann.TransactionTimeout</TSFI>
+ <TSFI>tsfi.cfg.conf.jbossts-properties.xml</TSFI>
+ </test>
</testCase>
<testCase name="org.jboss.test.invokers.test.MultiInvokersUnitTestCase">
<desc>Test use of multiple invokers per container</desc>
<test name="testMultiInvokers">
- <desc></desc>
+ <desc>
+ Test objective: Test whether entity bean is reachable through different invokers.
+ Expected result: Entity returned must be identical in both invokers.
+ </desc>
<TSFI>tsfi.port.rmi.unifiedInvoker</TSFI>
</test>
<test name="testClientContainer">
- <desc></desc>
+ <desc>
+ Test objective: Use the IClientContainer view of the proxy to install a custom
+ InvokerInterceptor which routes requests to either the server side
+ selected transport for the BusinessSession, or an mdb depending
+ on the method invoked.
+ Expected result: Test should finish without an exception and JMS transport invoker should decorate result with specific string.
+ </desc>
<TSFI>tsfi.port.rmi.unifiedInvoker</TSFI>
</test>
</testCase>
<testCase name="org.jboss.test.cluster.defaultcfg.test.HAInvokerUnitTestCase">
- <desc></desc>
+ <desc>Clustered HA invoker test case.</desc>
<test name="testJRMPHAProxyFailover">
- <desc></desc>
+ <desc>
+ Test objective: Failover test after undeploying from one cluster node.
+ Expected result: After reconfigure we should have deployment still available. No unexpected exceptions during test run.
+ </desc>
<TSFI>tsfi.port.rmi.jrmpha</TSFI>
</test>
</testCase>
<testCase name="org.jboss.test.ws.jaxws.ejb3Integration.injection.InjectionTestCase">
- <desc></desc>
+ <desc>Tests support for @EJB annotations in WS components</desc>
<test name="testEjb3Endpoint">
- <desc></desc>
+ <desc>
+ Test objective: Tests injection of EJB to component on EJB3 endpoint.
+ Expected result: Call has to return expected string combined with injected comp. call.
+ </desc>
<TSFI>tsfi.ann.WebContext</TSFI>
<TSFI>tsfi.api.jaxws</TSFI>
</test>
<test name="testPojoEndpoint">
- <desc></desc>
+ <desc>
+ Test objective: Tests injection of EJB to component on POJO endpoint.
+ Expected result: Call has to return expected string combined with injected comp. call.
+ </desc>
<TSFI>tsfi.ann.WebContext</TSFI>
<TSFI>tsfi.api.jaxws</TSFI>
</test>
@@ -1406,58 +1451,82 @@
<desc>This test case starts predefined configuration with audit logging enabled and asserts
audit logfile for messages to see if successful audit.</desc>
<test name="testServerStartupAndShutdownAuditMessage">
- <desc>Tests if after successful startup and shutdown of server, audit log contains proper entries.</desc>
+ <desc>
+ Test objective: Tests if after successful startup and shutdown of server, audit log contains proper entries.
+ Expected result: Audit log has to contain proper messages indicating startup and shutdown of the server.
+ </desc>
<TSFI>tsfi.cmd.start</TSFI>
<TSFI>tsfi.cmd.stop</TSFI>
<TSFI>tsfi.cfg.conf.jboss-log4j.xml</TSFI>
</test>
</testCase>
<testCase name="org.jboss.test.security.test.authorization.secured.HttpRequestJmxAuthenticationUnitTestCase">
- <desc></desc>
+ <desc>Test verifies that there is no jmx-console security baypass in secured profiles.</desc>
<test name="testGet">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to jmx-console via HTTP PUT possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.jmx-console.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.jmx-console.web.xml</TSFI>
<TSFI>tsfi.cfg.conf.props.jmx-console-users.properties</TSFI>
<TSFI>tsfi.cfg.conf.props.jmx-console-roles.properties</TSFI>
</test>
<test name="testPost">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to jmx-console via HTTP POST possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.jmx-console.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.jmx-console.web.xml</TSFI>
<TSFI>tsfi.cfg.conf.props.jmx-console-users.properties</TSFI>
<TSFI>tsfi.cfg.conf.props.jmx-console-roles.properties</TSFI>
</test>
<test name="testHead">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to jmx-console via HTTP HEAD possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.jmx-console.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.jmx-console.web.xml</TSFI>
<TSFI>tsfi.cfg.conf.props.jmx-console-users.properties</TSFI>
<TSFI>tsfi.cfg.conf.props.jmx-console-roles.properties</TSFI>
</test>
<test name="testOptions">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to jmx-console via HTTP OPTIONS possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.jmx-console.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.jmx-console.web.xml</TSFI>
<TSFI>tsfi.cfg.conf.props.jmx-console-users.properties</TSFI>
<TSFI>tsfi.cfg.conf.props.jmx-console-roles.properties</TSFI>
</test>
<test name="testPut">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to jmx-console via HTTP PUT possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.jmx-console.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.jmx-console.web.xml</TSFI>
<TSFI>tsfi.cfg.conf.props.jmx-console-users.properties</TSFI>
<TSFI>tsfi.cfg.conf.props.jmx-console-roles.properties</TSFI>
</test>
<test name="testDelete">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to jmx-console via HTTP DELETE possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.jmx-console.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.jmx-console.web.xml</TSFI>
<TSFI>tsfi.cfg.conf.props.jmx-console-users.properties</TSFI>
<TSFI>tsfi.cfg.conf.props.jmx-console-roles.properties</TSFI>
</test>
<test name="testTrace">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to jmx-console via HTTP TRACE possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.jmx-console.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.jmx-console.web.xml</TSFI>
<TSFI>tsfi.cfg.conf.props.jmx-console-users.properties</TSFI>
@@ -1465,51 +1534,72 @@
</test>
</testCase>
<testCase name="org.jboss.test.security.test.authorization.secured.HttpRequestJBossWSAuthenticationUnitTestCase">
- <desc></desc>
+ <desc>Test verifies that there is no jbossws console security baypass in secured profiles.</desc>
<test name="testGet">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to jbossws console via HTTP GET possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.jbossws-management.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.jbossws-management.web.xml</TSFI>
<TSFI>tsfi.cfg.conf.props.jbossws-users.properties</TSFI>
<TSFI>tsfi.cfg.conf.props.jbossws-roles.properties</TSFI>
</test>
<test name="testPost">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to jbossws console via HTTP POST possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.jbossws-management.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.jbossws-management.web.xml</TSFI>
<TSFI>tsfi.cfg.conf.props.jbossws-users.properties</TSFI>
<TSFI>tsfi.cfg.conf.props.jbossws-roles.properties</TSFI>
</test>
<test name="testHead">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to jbossws console via HTTP HEAD possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.jbossws-management.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.jbossws-management.web.xml</TSFI>
<TSFI>tsfi.cfg.conf.props.jbossws-users.properties</TSFI>
<TSFI>tsfi.cfg.conf.props.jbossws-roles.properties</TSFI>
</test>
<test name="testOptions">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to jbossws console via HTTP OPTIONS possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.jbossws-management.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.jbossws-management.web.xml</TSFI>
<TSFI>tsfi.cfg.conf.props.jbossws-users.properties</TSFI>
<TSFI>tsfi.cfg.conf.props.jbossws-roles.properties</TSFI>
</test>
<test name="testPut">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to jbossws console via HTTP PUT possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.jbossws-management.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.jbossws-management.web.xml</TSFI>
<TSFI>tsfi.cfg.conf.props.jbossws-users.properties</TSFI>
<TSFI>tsfi.cfg.conf.props.jbossws-roles.properties</TSFI>
</test>
<test name="testDelete">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to jbossws console via HTTP DELETE possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.jbossws-management.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.jbossws-management.web.xml</TSFI>
<TSFI>tsfi.cfg.conf.props.jbossws-users.properties</TSFI>
<TSFI>tsfi.cfg.conf.props.jbossws-roles.properties</TSFI>
</test>
<test name="testTrace">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to jbossws console via HTTP TRACE possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.jbossws-management.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.jbossws-management.web.xml</TSFI>
<TSFI>tsfi.cfg.conf.props.jbossws-users.properties</TSFI>
@@ -1517,371 +1607,570 @@
</test>
</testCase>
<testCase name="org.jboss.test.security.test.authorization.secured.HttpRequestStatusServletAuthenticationUnitTestCase">
- <desc></desc>
+ <desc>Test verifies that there is no http connector status servlet security baypass in secured profiles.</desc>
<test name="testGet">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to http connector status servlet via HTTP GET possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.app.jboss-web.xml</TSFI>
<TSFI>tsfi.app.web.xml</TSFI>
</test>
<test name="testPost">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to http connector status servlet via HTTP POST possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.app.jboss-web.xml</TSFI>
<TSFI>tsfi.app.web.xml</TSFI>
</test>
<test name="testHead">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to http connector status servlet via HTTP HEAD possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.app.jboss-web.xml</TSFI>
<TSFI>tsfi.app.web.xml</TSFI>
</test>
<test name="testOptions">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to http connector status servlet via HTTP OPTIONS possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.app.jboss-web.xml</TSFI>
<TSFI>tsfi.app.web.xml</TSFI>
</test>
<test name="testPut">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to http connector status servlet via HTTP PUT possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.app.jboss-web.xml</TSFI>
<TSFI>tsfi.app.web.xml</TSFI>
</test>
<test name="testDelete">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to http connector status servlet via HTTP DELETE possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.app.jboss-web.xml</TSFI>
<TSFI>tsfi.app.web.xml</TSFI>
</test>
<test name="testTrace">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to http connector status servlet via HTTP TRACE possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.app.jboss-web.xml</TSFI>
<TSFI>tsfi.app.web.xml</TSFI>
</test>
</testCase>
<testCase name="org.jboss.test.security.test.authorization.secured.HttpRequestAdminConsoleAuthenticationUnitTestCase">
- <desc></desc>
+ <desc>Test verifies that there is no admin console security baypass in secured profiles.</desc>
<test name="testGet">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to admin console via HTTP GET possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.admin.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.admin.web.xml</TSFI>
</test>
<test name="testPost">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to admin console via HTTP POST possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.admin.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.admin.web.xml</TSFI>
</test>
<test name="testHead">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to admin console via HTTP HEAD possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.admin.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.admin.web.xml</TSFI>
</test>
<test name="testOptions">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to admin console via HTTP OPTIONS possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.admin.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.admin.web.xml</TSFI>
</test>
<test name="testPut">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to admin console via HTTP PUT possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.admin.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.admin.web.xml</TSFI>
</test>
<test name="testDelete">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to admin console via HTTP DELETE possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.admin.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.admin.web.xml</TSFI>
</test>
<test name="testTrace">
- <desc></desc>
+ <desc>
+ Test objective: Test whether there is unauthorized access to admin console via HTTP TRACE possible.
+ Expected result: Answer from server should be HTTP_UNAUTHORIZED or HTTP_BAD_METHOD.
+ </desc>
<TSFI>tsfi.cfg.deploy.admin.jboss-web.xml</TSFI>
<TSFI>tsfi.cfg.deploy.admin.web.xml</TSFI>
</test>
</testCase>
<testCase name="org.jboss.test.ann.clustered.test.Ejb3ClusteredAnnTestCase">
- <desc></desc>
+ <desc>Tests if bean marked with @Clustered annotation is able to failover to different node in clustered environment.</desc>
<test name="testAppSetup">
- <desc></desc>
+ <desc>
+ Test objective: Tests whether app is setup and deployed correctly.
+ Expected result:Test application should be retrievable and work fine.
+ </desc>
<TSFI>tsfi.ann.Clustered</TSFI>
<TSFI>tsfi.cfg.deploy.cluster.hapartition-jboss-beans.xml</TSFI>
</test>
<test name="testOneNodeFail">
- <desc></desc>
+ <desc>
+ Test objective: Tests if counting half of cycles on one node and the other half on node which has left after
+ one node undeploy returns expected number of increments.
+ Expected result: Final number returned by bean (after one node undeploy) should be the same like counting on one node.
+ </desc>
<TSFI>tsfi.ann.Clustered</TSFI>
<TSFI>tsfi.cfg.deploy.cluster.hapartition-jboss-beans.xml</TSFI>
</test>
</testCase>
<testCase name="org.jboss.test.jbossmessaging.test.SecurityUnitTestCase">
- <desc></desc>
+ <desc>Test of security features in JMS providers</desc>
<test name="testLoginTest">
- <desc></desc>
+ <desc>
+ Test objective: Tests if properly logged user can send messages to topic.
+ Expected result: Amount of sent messages has to be the same like amount of received messages.
+ Publisher has to publish specified mount of messsages.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testLoginNoCred">
- <desc></desc>
+ <desc>
+ Test objective: Topic worker should be able to connect without credentials.
+ Expected result: No exception thrown during the connect.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testLoginValidCred">
- <desc></desc>
+ <desc>
+ Test objective: Topic worker should be able to connect with valid credentials.
+ Expected result: No exception thrown during the connect.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testLoginInvalidPwd">
- <desc></desc>
+ <desc>
+ Test objective: Topic worker should not be able to connect without valid password.
+ Expected result: Proper exception has to thrown the connect.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testLoginInvalidCred">
- <desc></desc>
+ <desc>
+ Test objective: Topic worker should not be able to connect without valid credentials.
+ Expected result: Proper exception has to thrown the connect.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testClientIDPreconfTest">
- <desc></desc>
+ <desc>
+ Test objective: Tests if client gets preconfigured client id.
+ Expected result: Has to be set preconfigured client id, exactly.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testClientIDSetTest">
- <desc></desc>
+ <desc>
+ Test objective: Tests if connection object receives client id from the client.
+ Expected result: Connection object has to return the same client id as the one set via client.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testClientIDSetAfterInvoke">
- <desc></desc>
+ <desc>
+ Test objective: Tests if connection object receives client id from the client after publishing message to topic.
+ Expected result: Setting client id after publish is not allowed. Proper exception has to be thrown.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzValidTopicPublisher">
- <desc></desc>
+ <desc>
+ Test objective: Test to check valid authorization to publish to topic.
+ Expected result: User has to be able to publish to the topic.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzValidTopicPublisherTransaction">
- <desc></desc>
+ <desc>
+ Test objective: Test to check valid authorization to publish to transacted topic.
+ Expected result: User has to be able to publish to the topic.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzInvalidTopicPublisher">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user with invalid authorization can publish to topic.
+ Expected result: User has not to be able to publish to the topic. Proper exception has to be thrown
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzInvalidTopicPublisherTransaction">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user with invalid authorization can publish to transacted topic.
+ Expected result: User has not to be able to publish to the topic. Proper exception has to be thrown
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzValidTopicSubscriber">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user with valid authorization can subscribe to a topic.
+ Expected result: User has to be able to subscribe to the topic and receive message.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzValidTopicSubscriberTransaction">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user with valid authorization can subscribe to a transacted topic.
+ Expected result: User has to be able to subscribe to the topic and receive message.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzInvalidTopicSubscriber">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user without valid authorization can subscribe to a topic.
+ Expected result: User has not to be able to subscribe to the topic and receive message. Proper exception has to be thrown.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzInvalidTopicSubscriberTransaction">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user without valid authorization can subscribe to a transacted topic.
+ Expected result: User has not to be able to subscribe to the topic and receive message. Proper exception has to be thrown.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzValidQueueSender">
- <desc></desc>
+ <desc>
+ Test objective: Test to check valid authorization to publish to queue.
+ Expected result: User has to be able to publish to the queue.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzValidQueueSenderTransaction">
- <desc></desc>
+ <desc>
+ Test objective: Test to check valid authorization to publish to transacted queue.
+ Expected result: User has to be able to publish to the queue.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzInvalidQueueSender">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user with invalid authorization can publish to queue.
+ Expected result: User has not to be able to publish to the queue. Proper exception has to be thrown.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzInvalidQueueSenderTransaction">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user with invalid authorization can publish to transacted queue.
+ Expected result: User has not to be able to publish to the queue. Proper exception has to be thrown.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzValidQueueReceiver">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user with valid authorization can subscribe to a queue and receive a message.
+ Expected result: User has to be able to subscribe to the queue and receive a message.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzValidQueueReceiverTransaction">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user with valid authorization can subscribe to a transacted queue and receive a message.
+ Expected result: User has to be able to subscribe to the queue and receive a message.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzInvalidQueueReceiver">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user without valid authorization can subscribe to a queue and receive a message.
+ Expected result: User has not to be able to subscribe to the queue and receive a message.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzInvalidQueueReceiverTransaction">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user without valid authorization can subscribe to a transacted queue and receive a message.
+ Expected result: User has not to be able to subscribe to the queue and receive a message.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzValidQueueBrowser">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user with valid authorization can browse a queue.
+ Expected result: User has to be able to browse the queue.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testAuzInvalidQueueBrowser">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user without valid authorization can browse a queue.
+ Expected result: User has not to be able to browse the queue.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testValidPreconfDurSub">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user with valid authorization can durrably subscribe to preconfigured topic and receive a message.
+ Expected result: User has to be able to subscribe to the topic and receive a message.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testInvalidPreconfDurSub">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user without valid authorization can durrably subscribe to preconfigured topic and receive a message.
+ Expected result: User has not to be able to subscribe to the topic and receive a message.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testValidDynDurSub">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user with valid authorization can durrably subscribe to dynamic topic and receive a message.
+ Expected result: User has to be able to subscribe to the topic and receive a message.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testInvalidDynDurSub">
- <desc></desc>
+ <desc>
+ Test objective: Test to check that user without valid authorization can durrably subscribe to dynamic topic and receive a message.
+ Expected result: User has to be able to subscribe to the topic and receive a message.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
</testCase>
<testCase name="org.jboss.test.jbossmessaging.test.Jms11UnitTest">
- <desc></desc>
+ <desc>Basic tests using the jms 1.1 producer/consumer APIs.</desc>
<test name="testQueueMessageOrder">
- <desc></desc>
+ <desc>
+ Test objective: Test that messages are ordered by message arrival and priority.
+ This also tests :
+ Using a non-transacted AUTO_ACKNOWLEDGE session
+ Using a MessageConsumer
+ Using a QueueSender
+ Sending PERSITENT and NON_PERSISTENT text messages.
+ Using a QueueBrowser
+ Expected result: No exceptions thrown.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testTemporaryQueueDelete">
- <desc></desc>
+ <desc>
+ Test objective: Test that temporary queues can be deleted.
+ Expected result: No exceptions thrown.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testTemporaryTopicDelete">
- <desc></desc>
+ <desc>
+ Test objective: Test that temporary topics can be deleted.
+ Expected result: No exceptions thrown.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testInvalidDestinationQueueBrowse">
- <desc></desc>
+ <desc>
+ Test objective: Test invalid destination trying to browse a message.
+ Expected result: InvalidDestinationException has to be thrown while trying to browse queue.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testErrorsTopicSubscribe">
- <desc></desc>
+ <desc>
+ Test objective: Test errors trying on topic subscribe.
+ Expected result: Proper exceptions have to be thrown (InvalidDestinationException).
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testCreateQueue">
- <desc></desc>
+ <desc>
+ Test objective: Test create queue.
+ Expected result: Queue created, no exceptions thrown.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testMessageListener">
- <desc></desc>
+ <desc>
+ Test objective: Testing message listener in different modes.
+ Expected result: No exceptions thrown.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testApplicationServerStuff">
- <desc></desc>
+ <desc>
+ Test objective: Testing message listener on application server in different modes.
+ Expected result: No exceptions thrown.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testTopics">
- <desc></desc>
+ <desc>
+ Test objective: Testing various aspects of topic pub/sub mechanism.
+ Expected result: No exceptions thrown.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testTopicNoLocal">
- <desc></desc>
+ <desc>
+ Test objective: Test to see if the NoLocal feature of topics works.
+ Expected result: Messages sent from the same connection should not
+ be received by Subscribers on the same connection.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testTopicNoLocalBounce">
- <desc></desc>
+ <desc>
+ Test objective: Test to see whether no local works if a message was created somewhere else.
+ Expected result: No local subscriber should not receive the message, but local should.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testTopicSelectorChange">
- <desc></desc>
+ <desc>
+ Test objective: Test subscribing to a topic with one selector, then changing to another.
+ Expected result: Test subscriber with message selector for property A will receive 2 messages
+ sent later, but not acknowledged.
+ Then receives two messages with message property B set, but no A.
+ Later sender sends anothe two messages with prop. A and newly established receiver
+ with selector for prop A will receive 4 messages with A property set.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testTopicSelectorNullOrEmpty">
- <desc></desc>
+ <desc>
+ Test objective: Test subscribing to a topic with a null and empty selector
+ Expected result: Subscribers with null and empty selector have to be able receive messages.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testSendReceiveOutdated">
- <desc></desc>
+ <desc>
+ Test objective: Test sending/receiving an outdated message.
+ Expected result: Receiver should receive only one message (the one which didn't expire).
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testSendReceiveExpired">
- <desc></desc>
+ <desc>
+ Test objective: Test receiving message with JMSExpiration and persistent delivery mode is delivered regardless of JMSExpiration.
+ Expected result: The message has to be received.
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
</test>
<test name="testSendListenOutdated">
- <desc></desc>
+ <desc>
+ Test objective: Test sending/listening an outdated message.
+ Expected result: After sending one outdated and one non-outdated message listener will receive only one message (non-outdated).
+ </desc>
<TSFI>tsfi.cfg.jms.jboss-beans.xml</TSFI>
<TSFI>tsfi.cfg.jms.destinations-service.xml</TSFI>
<TSFI>tsfi.cfg.jms.messaging-service.xml</TSFI>
@@ -1890,30 +2179,48 @@
<testCase name="org.jboss.test.webservice.endpoint.EndpointTestCase">
<desc>Test JAXWS Endpoint deployment</desc>
<test name="testWSDLAccess">
- <desc></desc>
+ <desc>
+ Test objective: Test whether deployment of WS endpoint has wsdl accessible via http://" + getServerHost() + ":8080/jaxws-endpoint?wsdl.
+ Expected result: Has to return non-null wsdl document.
+ </desc>
<TSFI>tsfi.api.jaxws</TSFI>
</test>
<test name="testClientAccess">
- <desc></desc>
+ <desc>
+ Test objective: Test whether client has access to deployed web service.
+ Expected result: Client has to receive expected string from endpoint.
+ </desc>
<TSFI>tsfi.api.jaxws</TSFI>
</test>
<test name="testServletAccess">
- <desc></desc>
+ <desc>
+ Test objective: Test whether one can access endpoint as servlet.
+ Expected result: Resulting http respose contains expected string.
+ </desc>
<TSFI>tsfi.api.jaxws</TSFI>
</test>
</testCase>
<testCase name="org.jboss.test.webservice.admindevel.ExampleTestCase">
<desc>A test for the examples from the JBoss Admin Devel book</desc>
<test name="testHelloString">
- <desc></desc>
+ <desc>
+ Test objective: Test if call to endpoint method returns proper string.
+ Expected result: Expected string has to be returned.
+ </desc>
<TSFI>tsfi.api.ws</TSFI>
</test>
<test name="testHelloBean">
- <desc></desc>
+ <desc>
+ Test objective: Test whether webservice can be access using data bean.
+ Expected result: Data bean has to contain proper result string.
+ </desc>
<TSFI>tsfi.api.ws</TSFI>
</test>
<test name="testHelloArray">
- <desc></desc>
+ <desc>
+ Test objective: Test whether webservice can be access using array query with mutiple data objects.
+ Expected result: All objects have to return expected message from webservice.
+ </desc>
<TSFI>tsfi.api.ws</TSFI>
</test>
</testCase>
@@ -1929,14 +2236,20 @@
<testCase name="org.jboss.test.ws.jaxws.cxf.descriptor.DescriptorJSETestCase">
<desc>Test a CXF endpoint with provided jbossws-cxf.xml</desc>
<test name="testLegalAccess">
- <desc></desc>
+ <desc>
+ Test objective: Test whether test service with descriptor in jboss-cxf file could be accessed.
+ Expected result: Service has to return expected string.
+ </desc>
<TSFI>tsfi.app.jboss-cxf.xml</TSFI>
</test>
</testCase>
<testCase name="org.jboss.test.ws.jaxws.samples.wsse.SignEncryptTestCase">
<desc>WS-Security sign and encrypt test case</desc>
<test name="test">
- <desc></desc>
+ <desc>
+ Test objective: Test if test service can be access using WS-Security sign and encrypt method.
+ Expected result: Service has to return expected string.
+ </desc>
<TSFI>tsfi.api.jaxws</TSFI>
<TSFI>tsfi.api.ws</TSFI>
</test>
@@ -1944,7 +2257,10 @@
<testCase name="org.jboss.test.ws.jaxws.samples.wsse.SignTestCase">
<desc>WS-Security sign test case</desc>
<test name="test">
- <desc></desc>
+ <desc>
+ Test objective: Test if test service can be access using WS-Security sign method.
+ Expected result: Service has to return expected string.
+ </desc>
<TSFI>tsfi.api.jaxws</TSFI>
<TSFI>tsfi.api.ws</TSFI>
</test>
@@ -1952,34 +2268,52 @@
<testCase name="org.jboss.test.ws.jaxws.samples.wsse.UsernameTestCase">
<desc>WS-Security username test case</desc>
<test name="test">
- <desc></desc>
+ <desc>
+ Test objective: Test if test service can be access using WS-Security username and password method.
+ Expected result: Service has to return expected string.
+ </desc>
<TSFI>tsfi.api.jaxws</TSFI>
<TSFI>tsfi.api.ws</TSFI>
</test>
<test name="testWrongPassword">
- <desc></desc>
+ <desc>
+ Test objective: Test if accessing service using WS-Security username and password with wrong password throws exception.
+ Expected result: Test has to catch exception and service cannot be called.
+ </desc>
<TSFI>tsfi.api.jaxws</TSFI>
</test>
</testCase>
<testCase name="org.jboss.test.ws.jaxws.complex.ComplexTestCase">
<desc>A complex JAX-WS test</desc>
<test name="testRegistration">
- <desc></desc>
+ <desc>
+ Test objective: Tests checks possible call to endpoint and ability to throw proper exception uppon unsuccessful registration.
+ Expected result: Proper exception type has to be thrown in case of unsuccessful registration.
+ </desc>
<TSFI>tsfi.api.jaxws</TSFI>
<TSFI>tsfi.api.ws</TSFI>
</test>
<test name="testInvoiceRegistration">
- <desc></desc>
+ <desc>
+ Test objective: Test checks successful invoice registration using WS port.
+ Expected result: No exceptions thrown.
+ </desc>
<TSFI>tsfi.api.jaxws</TSFI>
<TSFI>tsfi.api.ws</TSFI>
</test>
<test name="testOtherPackage">
- <desc></desc>
+ <desc>
+ Test objective: Test if returned port statiscs are correctly returned from server.
+ Expected result: Received statistics has to be as expected.
+ </desc>
<TSFI>tsfi.api.jaxws</TSFI>
<TSFI>tsfi.api.ws</TSFI>
</test>
<test name="testBulkRegistration">
- <desc></desc>
+ <desc>
+ Test objective: Test if bulk customer registration works and can handle faulty included customers.
+ Expected result: ValidationFault_Expection has to thrown with list of customer IDs that failed to be registered.
+ </desc>
<TSFI>tsfi.api.jaxws</TSFI>
<TSFI>tsfi.api.ws</TSFI>
</test>
More information about the jboss-cvs-commits
mailing list