Vesta Test

TestCases for Vesta. Bundled installer.

  1. Platform dependence. It is expected that there will be different installers for linux, intel-S2, sparc-S2
    1. Linux
      1. RHEL 5 x64 (64-bit)
      2. SLES 10 x64 (64-bit)
      3. * RHEL 5 x86 (32bit) - sanity check
      4. * SLES 10 x86 (32bit) - sanity check
      5. * Ubuntu LTS 8.04 - sanity check
      6. * CentOS 5.1 (or followup) - sanity check
    2. Solaris 10, SPARC and x86/x64 (32- and 64-bit)
    3. OpenSolaris 5/08 (will switch to 11/08 when available)
    4. Indiana
    5. not Linux or Solaris. Should correctly exit.
  2. Java existence on the host
    1. yes, of version Java J2SE JDK 6 Update 3 (or later). Should perform everything
    2. yes, but version lower Java J2SE JDK 6 Update 3. Most of actions could be performed
    3. no java. Warning window suggesting to install latest Java
  3. Installer Wizard
    1. System Analysis window: CPU Type, Administrator rights, SunStudio package, push More Info, Next, Back, Cancel buttons
    2. License Agreement step: verify text, accept/not accept license, push back/next/cancel
    3. Full or custom install screen(Choose different types), check buttons
    4. Customize screen(choose different combination of components)
    5. Installation directory screen. Choose directories with different rights for writing
    6. Other optional screens(?)
    7. Netbeans screen (if full install or IDE chosen in custom).
      1. old version of NB found. Should recommend to renew NB from ss-installer
      2. current version of NB found. Should recommend to use it
      3. different NB's found. Should suggest by default the latest one.
      4. no NB were found. Install NB from ss-installer
    8. Chosen options screen
    9. install process screen. Just check the progress bar and the possibility to interrupt the process.
    10. Finish screen
  4. Service Tags.
    1. yes. Should verify new servicetag through stclient -x.
    2. no. Should verify the silence mode of impossibility to create new servicetag.
    3. yes, but user has no rights to change ST(?)
  5. User rights
    1. root. All installation should complete.
    2. non-root(if the possibility will be provided then with different writing rights in other case just to check impossibility to install message on very beginning steps)
  6. Previous version of SS installed
    1. installed previous version and registered in ST only. Verify new servicetag and old one. Verify uninstallation of both product versions
    2. installed previous version and registered in SysNet only. Verify the both records in BD. Verify uninstallation. Verify uninstallation of both product versions
    3. installed previous version and registered in both ST and SysNet. Verify both records in BD and both servicetags. Verify uninstallation of both product versions
    4. installed previous version, but not registered. Verify new record in SysNet and ServiceTag. Verify uninstallation of older product version
  7. The same version of SS installed
    1. installed the same version and registered in ST only. Installer should notify user about it, if user confirm the installation verify ServiceTag does not change(or change the date?). SysNet record created.
    2. installed the same version and registered in SysNet only. Verify SysNet record does not change(or change the date?). ST if exists created.
    3. installed the same version and registered in both ST and SysNet. Installer should notify user about it, if user confirm the installation verify ServiceTag and SysNet record does not change(or change the date?)
    4. installed the same version, but not registered. Verify new ST(if exists) created and new SysNet record is created.
  8. Upgrade SS
    1. installation of some new components
    2. upgrade of some components
    3. uninstall of some components
  9. Whole uninstallation
    1. Check servicetags
    2. Check with different user rights
  10. Remote installation
    1. ssh with local display. Should complete the installation, but registration page should point to the remotely created html file.
    2. ssh without display. Should complete the installation and suggest to visit created registration page later
    3. vncviewer. Should complete the installation.
  11. The Postponed Registration. Should suggest the registration page when IDE is used or some silent registration if any command line tool were used after some time(?)
    1. Installed before during Solaris installation.
    2. Registered Later were chosen before
  12. Registration environment
    1. Browsers (list of supported browsers should be provided)
      1. browser from list in the path. Verify that after installation complete browser with registration page appers.
      2. browser from list, not in the path. Installer should ask the user the path to the browser(list of browsers should be provided)
      3. browser is not in the list or no browser at all. Installer should ask the user the path to the browser(list of browsers should be provided). After user can't do it, to suggest to register later and give information about successful installation.
    2. Internet connection
      1. direct connection. From local registration page user should connect to the global registration.
      2. firewall. From local registration page user should connect to the global registration. Verify when SysNet servers are not accessible due to security. Maybe SysNet servers are in suspected list.
      3. non-global zone(use sqa22-zone{1-3}, and sqao23-zone{1-3} machines for the testing)
      4. no connection. After user can't connect to the registration server, to suggest to register later and give information about successful installation.
    3. SysNet record
      1. Verify data on inventory server
  13. launch not from bash (sh or ksh). Installation should complete
  14. broken archive. Not completely downloaded, installer should report about this.
  15. xVM installation(use sqao54 machine: change "default 0" to "default 1" in /boot/grub/menu.lst, and just reboot ( bash$ reboot <Enter> ). )
  16. presence of installed components
    1. check the absence of non-installed
    2. check the absence of uninstalled
    3. check the versions of installed components
    4. verify the correct work of installed components.
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo