| All GlassFish one pagers are listed at: OnePagersOrFunctionalSpecs. StartAndStop Specifications Submitted to ARC This section contains the specifications that were submitted to the ARC (committee to get them reviewed).
Overall Review Comment – Please fix the typos in the test specifications. Admin Infrastructure Test Specification The spec is here 1 Configuration Management
| ID |
Comments |
Incorporated (YES/NO) |
| ? |
default-web.xml editing support is not available. Sorry, we couldn't do it. |
| ? |
Try to reproduce the zero-length domain.xml issue. It is observed that when the disk gets full and you try to do any admin operation, it results in zero-length domain.xml. This is pretty serious. Can you have a simulation where – you start the domain, fill the disk (at least simulate it) and then do an admin operation. It should never make the domain.xml size 0. |
NO |
2 General
| ID |
Comments |
Incorporated (YES/NO) |
| move-dom-diff-dom-name |
I am not sure if a user will ever want to do this. Name of the domain is rather unimportant to the user. And when the domain is renamed, I'd expect it to work rather than fail. |
NO |
| move-install-diff-loc |
This does not work. We already know that. Please see a bug that I've created under packaging subcomponent, by me. |
NO |
| move-inst-diff-loc-user-diff |
Is the intent here to share the domains? Then why won't you prefer the asadmin backup and restore commands? In this particular case still, I would expect the things to work, because the OS user name is not committed to, anywhere. |
NO |
3 AMX No new tests?
| ID |
Comment |
Incorporated (YES/NO) |
| ? |
We are not doing offline AMX or offline configuration in general. |
NO |
4 Admin Security I'd like to see proper test cases in this section. It is very important to cover these. 5 Process Launcher
| ID |
Comments |
Incorporated (YES/NO) |
| ? |
Add a test to make sure that the stop-domain command executes independently of the "size of the domain". In other words, if you have a domain with 4 instances, it should stop as quickly as a domain with no instances. |
NO |
| ? |
Process Names: It should be easily possible to identify the names of app server using "jps" command. I would like test-suites to depend on "jps" as much as possible. The name of the application server main class is "com.sun.server.enterprise.server.PELaunch". |
NO |
| ? |
It is required that you count the number of processes started with various kinds of domain. For example, a domain with jms-service being configured to be "EMBEDDED", there should be exactly one JVM that finally starts. This JVM is app server VM. If it is "LOCAL", then there would be two JVM processes. If it is "REMOTE" again, there should be one JVM process. When it is REMOTE, you should configure other things as well. |
NO |
| ? |
Misconfigure JMS Broker configuration somehow, using asadmin or Admin GUI. The server must come up with a WARNING or SEVERE message. Because if the server (domain) does not come up, then there is no way (other than manually changing domain.xml) to reconfigure the domain. |
NO |
| ? |
Thread Dumps: Make sure that various JVM parameters when applied to java-config of DAS, the thread-dump works correctly. Thread-dump is usually obtained on Unix systems by sending kill -3 to the app server process. |
NO |
6 Synchronization
| ID |
Comments |
Incorporated (YES/NO) |
| ? |
Need a specific test for testing "instance specific" library synchronization, if we don't have one. When an enterprise/cluster profile domain is created, an instance-specific folder (e.g. instance1-config, instance2-config) is created in domain's config folder. The purpose of this folder is to keep instance specific libraries in them. We need to make sure that instance1 gets what's there in instance1-config and so on. |
NO |
7 Misc
| ID |
Comments |
Incorporated (YES/NO) |
| ? |
Make sure that changes in configuration are handled by verify-domain-xml command |
NO |
Usage Profiles Test Specification Test Specification is here Answers to questions at the top of the test specification 1. What is the difference between developer and classic-pe ?. is it being the number of listeners being
created different ?. – classic-pe is not going to be supported. I am going to update the spec with that effect. 2. Does installer provide all the 3 profile options at the time of installation ?.
– no, the installers are going to be silent. We are not going to expose profiles at the installer level. 3. What happens when user creates a domain with developer profile and tries to create a cluster , will it
work ?. – no, it will not work. It will give a meaningful message. You can try it and let me know if the
message is clear enough. The one pager says the commands are not masked to a particular kind of profile. But the profile
comparison table says "cluster/standalone instance creation is not available for developer profile". What
exactly mean not available. – the developer profile is not capable of creating server instances and clusters. Thus, if you
– create a domain with --profile developer
– asadmin create-instance/cluster/(other cluster commands) and direct it to this domain,
the command will fail. What is the difference between enterprise and classic-ee ?. – no difference. There is no profile like classic-ee. I will update the spec. Does installer provide all the 4 profile options at the time of installation ?. – no, please see above. Review of the test specification:
| ID |
Comments |
Incorporated (YES/NO) |
| pe-dev-factory |
I don't think you should really test it. This not an exposed interface. It is an internal detail of application server. |
NO |
| pe-dev-listeners |
I am going to update the spec for the same. It is not true that a reduced number of ports are being used in developer profile. All the SSL ports will be used to begin with. So, please change this test case. |
NO |
| pe-dev-hrtbeat |
What does this test mean? I don't think you need to ensure that because the heartbeat will be enabled only on clusters. |
NO |
| pe-dev-foreground |
Please remove this test. I am going to change the spec because it was too much of a change. The domain will start in background in all the cases, by default. |
NO |
| pe-dev-session |
Not sure what you mean by session, please elaborate. |
NO |
| pe-dev-cluster |
This should FAIL. Please see if appropriate message is displayed. Note that this message has to be generic enough. |
NO |
| ? |
Add some test to make sure that glassfish-cluster and pe-cluster provides the in-memory replication. This is accomplished using the dotted name. Contact Vivek for the same. Check the one-pager for in-memory replication, to get an idea of what the configuration is like. Let me know if something is not clear. |
NO |
| ? |
Add a number of tests to make sure that you can use PE installer as a cluster-aware installation. Your current set of tests are good, but they can be enhanced further. |
NO |
| ? |
Add a test for version. Version should ALWAYS contain the information about the build id. It is not enough to get build information as a part of "version" only when "asadmin version --verbose" is invoked. |
NO |
| ? |
Assess the output of the "asadmin start-domain" command when the domain is created in all the three profiles. It is important that it is clear what the capabilities of a domain are. Note that it it NOT required that the output displays the name of the profile. |
NO |
| ? |
Do an extensive testing of ALL the dotted names of the domains in all the profiles. I need this coverage. Have I missed those tests? Are you covering dotted names sufficiently? For example, there was an enhancement to the JDBC connection pool configuration recently. Check the sun-domain_1_3.dtd for the same. |
NO |
| ? |
Take PE installer or GlassFish build. Install NSS and HADB separately. Modify the entries as follows:
* asenv - make AS_NSS and AS_NSS_BIN point to NSS installation
* Make AS_HADB point to HADB installation. After you do this, "asadmin create-domain --profile enterprise" should work on that installation.
This proves that even if we don't bundle everything with a particular distribution, it is possible to download the components and run them so. |
NO |
| ? |
Set up the cluster profile domain for availability using the in-memory replication. |
NO |
| ? |
Test default profile for domain on PE SetupSDK installer is developer profile. |
NO |
| ? |
Test default profile for domain on EE SetupSDK installer is developer profile. |
NO |
| ? |
Should be able to configure the load balancer plugin against PE setupSDK installer. Do we have a test for the same? |
NO |
|
