(I can't edit original page because of https://jira.jboss.org/jira/browse/ORG-82 .)

EAR Tests

testBasicEarDeployment

Done

assertion:  verify deployment of basic Enterprise Archive package
test Strategy:  Navigate to Enterprise Applications. Add a new resource.

Verify the resource was successfully deployed.

testBadEarRedeploy

Done, currently disabled as it breaks the build: DISABLEDtestBadEarRedeploy()

assertion:  Verify an .ear that contained a bad deployment descriptor
fails deployment, fixed using console, and can then be
successfully deployed.
test Strategy: Deploy an .ear that is known to have a bad deployment
descriptor.  Verify the console shows deployment failed.
Edit the .ear resource to fix the achive.  Redeploy and
verify the archive has been deployed successfully.

testNavigationToEar

Done

           
assertion:  Verify the navigation sequence to Enterprise Applications
test Strategy: From the root of the navigation tree:
Click JBossAS Servers ==> JBoss App Server:${config} ==> Applications
                    ==> Enterprise Application

testEarSummary

assertion:  Verify the content of the Enterprise Application Summary tab.

testEarProperties

Done in testEarSummaryTab()

assertion:  Verify the General Properties of a successfully deployed .ear

test Strategy: After verifying an Enterprise Archive was successfully
deployed, select the .ear from the list of available applications on the Summary Tab
of Enterprise Application (EAR).  This brings you to Summary Tab of the deployed
enterprise achive.  Verify the General Properties:
         *              Name:
         *              Version:
         *              Description:

testEarResourceTraits

Done in testEarSummaryTab()

assertion:  Verify the Resource Traits of a successfully deployed .ear.
test Strategy: After verifying an Enterprise Archive was successfully
deployed, select the .ear from the list of available applications on the Summary Tab
of Enterprise Application (EAR).  This brings you to Summary Tab of the deployed
enterprise achive.  Verify the Resource Traits:
         *              Path:
         *              Exploded?:

testEarMetricsSummaryName

No numeric metric values for EAR.

assertion:  Verify the Metrics Summary of a successfully deployed .ear.
test Strategy: After verifying an Enterprise Archive was successfully
deployed, select the .ear from the list of available applications on the Summary Tab
of Enterprise Application (EAR).  This brings you to Summary Tab of the deployed
enterprise achive.  Verify the selection of the Metrics Summary option:
         *              NAME

testEarMetricsSummaryValue

No numeric metric values for EAR.

assertion:  Verify the Metrics Summary of a successfully deployed .ear.
test Strategy: After verifying an Enterprise Archive was successfully
deployed, select the .ear from the list of available applications on the Summary Tab
of Enterprise Application (EAR).  This brings you to Summary Tab of the deployed enterprise achive.  Verify the selection of the Metrics Summary option:
         *              VALUE

testEarMetricsSummaryDescription

No numeric metric values for EAR.

assertion:  Verify the Metrics Summary of a successfully deployed .ear.
test Strategy: After verifying an Enterprise Archive was successfully deployed, select the .ear from the list of available applications on the Summary Tab
of Enterprise Application (EAR).  This brings you to Summary Tab of the deployed
enterprise achive.  Verify the selection of the Metrics Summary option:
         *              DESCRIPTION

testEarConfigurationPage

Done in testEarConfigurationTab()

assertion:  Verify the Configuration Page of a successfully deployed .ear.
test Strategy: After verifying an Enterprise Archive was successfully
deployed, select the .ear from the list of available applications on the Summary Tab
of Enterprise Application (EAR).  This brings you to Summary Tab of the deployed

enterprise achive.  Choose the Configuration Tab and verify the Configuration.

testModifyEarAndCancel

Done in testEarConfigurationTabCancel()

assertion:  From the Configuration Tab, Edit a deployed resource and SAVE the changes.
test Strategy:  Deploy an .ear.  Verify it is UP.  Navigate to the Configuration  tab and Edit the Resource.  Save the changes and verify the changes were saved.    testModifyEarAndSave        Currently only see EDIT RESOURCE SAVE/CANCEL.  Cannot edit the resource.  Same as EMBJOPR-69?
assertion:  From the Configuration Tab, Edit a deployed resource but  CANCEL the changes.
test Strategy:  Deploy an .ear.  Verify it is UP.  Navigate to the Configuration tab and Edit the Resource.  Cancel the changes and verify the resource did not get updated .

testEarMetricTraits

TBD.

assertion:  Verify the Metrics Page of a successfully deployed .ear.
test Strategy: After verifying an Enterprise Archive was successfully
deployed, select the .ear from the list of available applications on the Summary Tab
of Enterprise Application (EAR).  This brings you to Summary Tab of the deployed
enterprise achive.  Choose the Metrics Tab and verify the Trait Values as shown.
         *              Path:
         *              Exploded?:

testEarNumericValues

No numeric metric values for EAR.

        Does the user have control over whether the archive is exploded?
assertion:  Verify the Metrics Page of a successfully deployed .ear.
test Strategy: After verifying an Enterprise Archive was successfully deployed, select the .ear from the list of available applications on the Summary Tab of Enterprise Application (EAR).  This brings you to Summary Tab of the deployed enterprise achive.  Choose the Metrics Tab and verify the Numeric Values as shown.

testEarMetricsRefresh

Done in testEarMetricsTabRefreshButton()

What numeric values are expected to be exposed for a applications?
assertion:  Verify the Metrics Page of a successfully deployed .ear.
test Strategy: After verifying an Enterprise Archive was successfully
deployed, select the .ear from the list of available applications on the Summary Tab
of Enterprise Application (EAR).  This brings you to Summary Tab of the deployed
enterprise achive.  Choose the Metrics Tab. Verify the use of the REFRESH button.                                    

testEarContent

Done in testEarRedeployment()

assertion:  Verify an .ear can be updated reloading from disk.
test Strategy: After verifying an Enterprise Archive was successfully
deployed, select the .ear from the list of available applications on the Summary Tab
of Enterprise Application (EAR).  This brings you to Summary Tab of the deployed
enterprise achive.  Choose the Content Tab.  Browse to pick up the .ear that is currently deployed.  Hit Update.  Verify the change to the archive.

testStopAndStartEar

Stops and Starts an EAR with WAR in the Control tab.
FAILS because of EMBJOPR-133.

testRestartEar

Restarts an EAR with WAR in the Control tab.
FAILS because of EMBJOPR-133.

management of deployed applications using a variety of archive packaging.

The creation or resuse of the test packages will be done through the build tools in the
AS testsuite.  The building of  test packages already exists so we don't
replicate it in the EMBJOPR-JSFUNIT project.  It is anticipated that test
cases will also be written for the AS 5 testsuite to confirm the successful
deployment of these newly created test archives.  Most of the tests used in
the AS 5 testsuite consist of J2EE 1.4 applications including with deployment
descriptors and not many with EE 5 packaging.  Some may already exist.

The tests will use component classes that are written with annotations
and use sparse deployment descriptors as necessary.  Some archives will
also use metadata-complete to define the metadata.



assertion: Deploy two Enterprise Archives with both contain an ejb module
that have the same classes in each.  Verify isolation is working.



assertion:  Deploy an Enterprise Archive that contains a persistence unit
in the EAR's lib directory.  The Enterprise Archive also contains an ejb.jar
and a web.war.  The persistence unit is made available to both components
being packaged in this directory.  The EJBs and web classes should contain
code to inject an EntityManager to confirm the deployment is successful.


assertion:
Deploy .EAR containing ejb.jar with persistence unit packaged
in the root of the ejb.jar


assertion:  deploy an EAR containing multiple ejb.jars and
a war.  Deploy the ear.  Invoke the web application from the browser
and call a business method on the ejb from the war using local interface.

assertion: Deploy two different Enterprise Archvies.  One of the .ears contains only a client.jar that references
bean in the other EARs ejb.jar via an ejb-ref.   The jboss-client.xml file should
contain </ignore-dependency> so the deployment will succeed.  JBCTS-788

assertion:
Create an archive using a deployment descriptor with the element metadata-complete.


assertion:
Create an archive that has references between ejb.jars.
Package already exists:  refs.ear and refs-ejb3-ejb3link.ear