1. Domain configuration Management

config management					no default-web.xml editing
Index	Priority	Test-Id	Testcase-description	Status	Comments
1	P1	domain-xml-0-size	1. create a domain 2. simulate a disk full environment 3. do some app deployment 4. and verify the deployment fails and domain.xml size doesn't become 0		manual

Moving domains to a different directory/installation
Index	Priority	Test-Id	Testcase-description	Status	Comments
1	P2	move-dom-diff-loc-1	create a domain start the domain stop the domain move the domain to a different --domaindir start the domain and make sure it works as before stop the domain delete the domain
2	P2	move-dom-diff-ins-2	create a domain start the domain stop the domain move the domain to a different appserver(same version) installation start the domain and make sure it works as before stop the domain delete the domain		manual
3	P2	move-dom-diff-loc-restore	create a domain start the domain stop the domain backup-domain move the domain to a different --domaindir start the domain stop-domain restore-domain start-domain verify it works fine after restore delete the domain		Bug-6505206
4	P4	move-dom-diff-dom-name	create a domain start the domain stop the domain move the domain to a different --domaindir but under a different domain name start the domain and verify this fails delete the domain		the domain may or maynot start
5	P2	move-insta-diff-loc	create a domain start the domain stop the domain move the installation to a different directory on the same host start the domain and make sure it works as before stop the domain delete the domain		a backup/restore could be done to achive this.
6	P3	move-inst-diff-loc-user-diff	create a domain start the domain stop the domain move the installation to a different directory on the same host but under different user directory will the domain start ?.		manual
7	P2	move-domain-with-ins	create / start domain create / start nodeagent create / start instances stop domain move domain to different domaindir start domain verify the node agents/instances work well with domain moved to different location

3. Management API (AMX)
Questions
The offline config will be possible only through AMX clients or any new cli commands will be added to do offline configuration ?.
No editing support

4. Administrative Security
Will be covered by core security test suites

5. Process Launcher and Startup/Shutdown

Process Launcher
Index	Priority	Test-Id	Testcase-description	Status	Comments
1	P1	pro-launcher-1	Verify at the time of startup/shutdown only 2 java processes gets created(1 for asadmin and other for server jvm)		manual
2.	P2	pro-launcher-2	create a domain start/stop measure the start/shutdown time create several instances in a domain measure the start/shutdown time verify both are equal		manual
3	P3	pro-launcher-3	create and start a domain verify the process name is "com.sun.server.enterprise.server.PELaunch" using jps command create and start instances verify the process name is "com.sun.server.enterprise.server.PELaunch" using jps command create and start node agents verify the process name is "com.sun.enterprise.ee.nodeagent.NodeAgentMain" using jps command		manual
4	P1	pro-launcher-4	set the jms-service type to be EMBEDDED verify there is only one JVM process after the domain starts set the jms-service type to be REMOTE verify there is only one JVM process after the domain starts		manual
5	P1	pro-launcher-5	set the jms-service type to be LOCAL verify there is 2 JVM processes after the domain starts		manual
6	P2	pro-launcher-6	create and start a domain set jms admin user name / password to a wrong value stop /start the domain verify the the server throws a severe message in server.log		manual
7	P2	pro-launcher-7	start the domain thread dum using kill -3 in unix verify the thread happens as expected.		manual

6. Synchronization
No functional spec yet.

7. Node Agent

Admin password change
Index	Priority	Test-Id	Testcase-description	Status	Comments
1	P1	change-admin-passwd-1	create domain start  domain change admin password verify asadmin simply exits with command successfull		PE/EE manual
2	P1	change-admin-passwd-2	create domain start  domain create node agent change admin password verify asadmin simply exits with command successfull		EE manual
3	P1	change-admin-passwd-3	create domain start  domain create node agent start node agent change admin password verify asadmin prints out instructions on what needs to done		EE Bug - 6505244 manual
4	P1	change-admin-passwd-4	create domain start  domain create node agent start node agent stop node agent change admin password verify asadmin prints out instructions on what needs to done		EE manual
5	P1	change-admin-passwd-5	create domain start  domain create node agent start node agent create instance change admin password verify asadmin prints out instructions on what needs to done		EE manual
6	P1	change-admin-passwd-6	create domain start  domain create node agent start node agent create instance start instance change admin password verify asadmin prints out instructions on what needs to done		EE manual
7	P1	change-admin-passwd-7	create domain start  domain create node agent start node agent create instance start instance stop instance change admin password verify asadmin prints out instructions on what needs to done		EE manual
8	P1	change-admin-passwd-8	create domain start  domain create a cluster create instance as part of the cluster change admin password verify asadmin prints out instructions on what needs to done		EE manual

Nodeagent synchronization
covered under admincli testing

Restoring domain in different machine
Index	Priority	Test-Id	Testcase-description	Status	Comments
1	P2	restore-dom-diff-machine-1	create domain start domain create nodeagent start nodeagent stop domain backup domain restore domain in different machine start domain create a instance referring to the nodeagents start instance the node agents should be able to get the newly created instance and start it		manual
2	P2	restore-dom-diff-machine-2	create domain start domain create nodeagent start nodeagent stop node agent stop domain backup domain restore domain in different machine start domain start node agent , will not connect to DAS stop domain start domain create a instance referring to the nodeagents start instance the node agents should be able to get the newly created instance and start it		manual
separation of client and server side trust stores
1	P2	trust-store-1	create/start a domain create and start nodeagent stop nodeagent stop domain create another domain start nodeagent verify start nodeagent succeds, since the nodeagent belonged to domain1 it shouldn't sync up with domain2		manual

Total Tests

Index	Feature	Total Tests
1	config mgmt	1
2	domain relocation	7
3	process launcher	7
4	node agent	8
5	domain restoration	2
6	trust store	1
		26

References

1. Admin Infrastructure Functional Specification