Manual tests for the Zero Installer

Preparation

In order to have the installer resolve the correct artifacts you must create an installer.properties file with the following contents: ZERO_REPO_URL=http://aeneis.raleigh.ibm.com/zero/silverstone/latest/repo/ Place the installer.properties file in the same directory as sMash_Installer_1_x_x_x.(exe | bin) and it will be picked up automatically. If you are unable to place the installer.properties file in the same directory as the intaeller (for instace when running from a cd), execute the installer with the -f /path/to/installer.properties option. Setting ZERO_REPO_URL ensures that the installer will resolve the correct modules when testing.

If your are testing a sMash fixpack release then the above ZERO_REPO_URL should become ZERO_REPO_URL=http://aeneis.raleigh.ibm.com/sMash/1.0.x/repo/ . Also, all URLs in the form http://aeneis.raleigh.ibm.com/zero/silverstone/latest/ <rest of path> should become http://aeneis.raleigh.ibm.com/sMash/1.1.x/ <rest of path>

Verify install and create for Windows

1. On a windows box, browse to http://aeneis.raleigh.ibm.com/zero/silverstone/latest/installers/zero.installer/Web_Installers/install.htm and push the button to download the installer
2. Place the installer.properties file in the same directory that you downloaded the installer to and double click the installer to execute it.
3. Click Ok to the Intro and proceed to License Agreement.
4. TEST Verify that the license agreement contains the content of these two attachments: LA_en , LI_en - pay particular attention to the program name (e.g. Program Name: IBM WebSphere sMash V1.0) to make sure it is appropriate for the current release
5. Now proceed through the rest of the panels.
6. TEST Verify that there is a success or congratulations message on the last panel and that no errors or warnings are indicated.
7. Open a new command-line
8. TEST Right click on My Computer icon on Desktop and select Properties>Advanced>Environment Variables to verify that the installation directory has been added to the front of the user's PATH env variable.
9. Type 'zero create myapp'
10. TEST There should be no indication that the resolver is needing to download the dependencies remotely
11. TEST You should receive a success type of message and no errors.
12. cd 'myapp', and type 'zero start'
13. TEST you should some indication that the application was started successfully and the port number on which it is running
14. TEST Verify that there is only one directory named "stable" under $install_location/zero-repository
15. TEST the CLI should be set for "stable"; verify by executing "zero version" and confirming the value of the module group property in the response

Verify Upgrade for Windows

1. Without uninstalling sMash from the above "Verify install and create for Windows" install steps, run the installer again.
2. After the License Agreement make sure that you are prompted to uninstall the previous version of sMash. Click the Uninstall button.
3. Verify that the rest of the install steps complete successfully.
4. Verify steps 6-15 again, to test that the upgrade went successfully.

Verify install and create for Linux

1. On a linux box, browse to http://aeneis.raleigh.ibm.com/zero/silverstone/latest/installers/zero.installer/Web_Installers/install.htm and push the button to download the installer
2. Place the installer.properties file in the same directory that you downloaded the installer to adn run the .bin to start the installer and proceed through the panels
3. TEST Verify that there is a success or congratulations message on the last panel and that no errors or warnings are indicated.
4. TEST Logout of the machine and log back in and type export to verify that the installation directory has been added to the front of the PATH env variable.
5. Open a terminal
6. Type 'zero create myapp'
7. TEST There should be no indication that the resolver is needing to download the dependencies remotely
8. TEST you should receive a success type of message and no errors.
9. cd 'myapp', and type 'zero start'
10. TEST you should some indication that the application was started successfully and the port number on which it is running
11. TEST Verify that there is only one directory named "stable" under $install_location/zero-repository
12. TEST the CLI should be set for "stable"; verify by executing "zero version" and confirming the value of the module group property in the response

Verify Upgrade for Linux

1. Without uninstalling sMash from the above "Verify install and create for Linux" install steps, run the installer again.
2. After the License Agreement make sure that you are prompted to uninstall the previous version of sMash. Click the Uninstall button.
3. Verify that the rest of the install steps complete successfully.
4. Verify steps 3-12 again, to test that the upgrade went successfully.

Repeat for console mode

1. Repeat above steps for "Verify install and create for Linux" in console mode. Use '-i console' arg when launching installer to run in console mode. Make sure to have an installer.properties file present in the same directory as the installer or use the '-f /path/to/installer.properties' arg.

Test CD version without network connectivity (local only)

1. Download http://aeneis.raleigh.ibm.com/zero/silverstone/latest/installers/zero.installer/C1P52ML.tar.gz and save it in an empty directory (to be called [cdromroot]).
2. Expand the C1P52ML.tar.gz into a local directory and cd to [cdromroot]/[platform you are on]. Copy the installer.properties file to the same directory as the installer executable.
3. Disable network connectivity for your local host
4. Run the install executable and proceed through the panels.
5. TEST After selecting the user install directory, you should receive a message that indicates that a local snapshot of the repository will be installed and asks you if you intend to connect to the "remote repository" later or if you want to configure a "local only" installation.
6. Choose Local only installation and proceed through the panels to the end
7. TEST Verify that there is a success or congratulations message on the last panel and that no errors or warnings are indicated.
8. Open a command-line
9. TEST Type set command to verify that the 'zero' directory is the first entry in the PATH env variable
10. TEST Look at /zero-repository/stable/site.xml and verify that there ARE NOT URLs included in the file. See examples below:

    <?xml version="1.0" encoding="UTF-8"?><!-- default from zero.cli.tasks --><ivysettings>
      <typedef classname="zero.cli.tasks.repo.management.ZeroUrlResolver" name="zerourlresolver"/>
      <typedef classname="zero.cli.tasks.repo.management.ZeroIBiblioResolver" name="zeroibiblioresolver"/>
      <resolvers>
        <chain name="remote" returnFirst="true"/>
      </resolvers>
    </ivysettings>

11. Type 'zero create myapp'
12. TEST you should receive a success type of message and no errors.
13. cd 'myapp', and type 'zero start'
14. TEST you should some indication that the application was started successfully and the port number on which it is running
15. Reconnect to the network
16. Run 'zero search zero:employee.demo -remote"
17. TEST You should get no hits on the search (note currently the search command states success even though it could not connect)

C:\temp\zero>zero search zero:employee.demo -remote
CWPZT0600I: Command search was successful

Test CD version without network connectivity (remote later)

1. Download http://aeneis.raleigh.ibm.com/zero/silverstone/latest/installers/zero.installer/C1P52ML.tar.gz and save it in an empty directory (to be called [cdromroot]).
2. Expand the C1P52ML.tar.gz into a local directory and cd to [cdromroot]/[platform you are on].
3. Place a copy of installer.properties in the same directory as the installer executable.
4. Disable network connectivity for your local host
5. Run the install executable and proceed through the panels.
6. TEST After selecting the user install directory, you should receive a message that indicates that a local snapshot of the repository will be installed and asks you if you intend to connect to the "remote repository" later or if you want to configure a "remote later" installation.
7. Choose Use remote repository and proceed through the panels to the end
8. TEST Verify that there is a success or congratulations message on the last panel and that no errors or warnings are indicated.
9. Open a command-line
10. TEST Type set command to verify that the 'zero' directory is the first entry in the PATH env variable
11. TEST Verify that /zero-repository/stable/site.xml does not exist
12. Type 'zero create myapp'
13. TEST you should receive a success type of message and no errors.
14. cd 'myapp', and type 'zero start'
15. TEST you should some indication that the application was started successfully and the port number on which it is running
16. Reconnect to the network
17. Run 'zero search zero:employee.demo -remote"
18. You should get a search hit similar to the output below

C:\temp\zero>zero search zero:employee.demo -remote
zero:employee.demo:1.0.17368.M7

CWPZT0600I: Command search was successful

Test CD version of RTE installer

1. You must first have installed the Project Zero CLI using the installer with a working network connection and you must currently be connected to the network.
2. Download http://aeneis.raleigh.ibm.com/zero/silverstone/latest/installers/zero.rte.installer/C1P55ML.tar.gz and save it in an empty directory (to be called [cdromroot]).
3. Expand the C1P55ML.tar.gz into a local directory and cd to [cdromroot]/[platform you are on]
4. Place the installer.properties file in the same directory as the installer executeable.
5. Run the install exe and click Ok to the Intro and proceed to License Agreement.
6. TEST Verify that the license agreement contains the content of these two attachments: LA_en , LI_en - pay particular attention to the program name (e.g. Program Name: IBM Reliable Transport Extension for WebSphere sMash V1.0) to make sure it is appropriate for the current release
7. Proceed through the rest of panels.
8. TEST Verify that there is a success or congratulations message on the last panel and that no errors or warnings are indicated.
9. Open a command-line
10. TEST Look at /zero-repository/stable/site.xml and verify that there is an RTE url added to the site.xml. See examples below where rte.repo.latest was added:

    <?xml version="1.0" encoding="UTF-8"?><!-- default from zero.cli.tasks --><ivysettings>
      <typedef classname="zero.cli.tasks.repo.management.ZeroUrlResolver" name="zerourlresolver"/>
      <typedef classname="zero.cli.tasks.repo.management.ZeroIBiblioResolver" name="zeroibiblioresolver"/>
      <resolvers>
        <zerourlresolver name="zero.1">
          <ivy pattern="http://aeneis.raleigh.ibm.com/zero/silverstone/latest/repo/${ivy.local.default.ivy.pattern}"/>
          <artifact pattern="http://aeneis.raleigh.ibm.com/zero/silverstone/latest/repo/${ivy.local.default.artifact.pattern}"/>
        </zerourlresolver>
        <zeroibiblioresolver checkconsistency="false" m2compatible="true" name="maven.2" root="http://repo1.maven.org/maven2/"/>
        <zerourlresolver name="zero.3">
          <ivy pattern="http://aeneis.raleigh.ibm.com/zero/silverstone/latest/repo/${ivy.local.default.ivy.pattern}"/>
          <artifact pattern="http://aeneis.raleigh.ibm.com/zero/silverstone/latest/repo/${ivy.local.default.artifact.pattern}"/>
        </zerourlresolver>
        <chain name="remote" returnFirst="true">
        <resolver ref="zero.1"/>
          <resolver ref="maven.2"/>
        <resolver ref="zero.3"/>
        </chain>
      </resolvers>
    </ivysettings>
    

11. Type 'zero create myapp'
12. cd to myapp/config and edit ivy.xml to include zero.messaging.broker and save
13. cd back to myapp root and type 'zero resolve'
14. TEST you should receive a success type of message and no errors and no unresolved dependency messages

running

• LA_en: Licenase Agreement

• LI_en: License