Manual tests for Management

Guidelines for documenting the manual tests:

• Summarize the elements covered in the test
• Enumerate the steps (ordered list)
• Call out test points with a TEST bullet
• Include screenshots as appropriate; many of the manual tests will be visual, so screenshots are helpful

Management Dependency

Update Employee Demo within eclipse to include management dependency

Tests confirm:

• zero.management can be added to a project and can be resolved in eclipse

Steps:

1. Check out employee.demo from SVN into eclipse
2. Update all dependencies in eclipse
3. Open the config/ivy.xml for editing
4. add the following line the dependencies stanza:

<dependency name="zero.management" org="zero" rev="1.0+"/>

1. save ivy.xml
2. ensure dependency resolution works

Update Employee Demo on the command line to include management dependency

Tests confirm:

• zero.management can be added to a project and can be resolved in command line

Steps:

1. Download M4 command Line build and untar/unzip
2. Install the employee.demo application using the following command - zero install zero:employee.demo
3. Delete all dependencies in local repository
4. Update employee.demo/config/ivy.xml
5. add the following line the dependencies stanza :

<dependency name="zero.management" org="zero" rev="1.0+"/>

1. save ivy.xml
2. Within the employee.demo directory run: "zero resolve"

Management Commands

Tests confirm:

• Once management has been added to a project, the management command extensions work to control the application

Steps:

1. Ensure employee.demo has been updated with the zero.management dependency per the above instructions, zerohome is in your $PATH, and you are within the employee demo directory
2. execute: zero start
   
   
3. execute: zero restart
   
   
4. execute: zero info
   
   
5. execute: zero status
   
   
6. execute: zero stop
   
   

Zero Socket Opener (ZSO) functional

Tests confirm:

• That the ZSO can be used to front a zero app, so the JVM is only started when a request is received.
• That the idle timeout works for shutting down a JVM when it is not in use.
• These steps only work on Linux -- the only ZSO supported platform for M4.

Steps:

1. Update employee.demo as above, but instead of "zero.management", use the dependency "zero.management.zso"
2. Update the zero.config of employee.demo with "/config/idleTimeout=60". This configures the JVM to stay alive for at least 60 seconds from the last request.
   
   
3. Open a terminal / shell to the root directory of employee.demo. Make sure that zerohome is in your $PATH.
4. Start the application via the ZSO. execute: zero startzso
   
   
5. Confirm that the zso is running. "ps -ef |grep zso" should have 1 entry. "ps -ef |grep java" should have no entries.
6. Connect to the application. Open a browser to "http://localhost:8080" The application should respond as normal.
7. Confirm both the zso and the JVM are running. "ps -ef |grep zso" should have one entry for the zso itself, and one for the java vm. "ps -ef |grep java" should have 1 entry.
   
   
8. Wait 60 seconds or so. The JVM should exit. A "ps -ef |grep java" should be empty, with no entries.
   
   
9. Connect to the application. (Reload the page). The application should response as normal.
10. Stop the application and the ZSO. execute: zero stop
11. "ps -ef|grep zso" and "ps -ef|grep java" should both be empty.