Skip to content

Releases: VirtQE-S1/ESX-LISA

ESX-LISA 2.1

27 Feb 08:09
@VirtQE-S1 VirtQE-S1
2.1
fb22e3b
Compare
Choose a tag to compare
ESX-LISA 2.1 Latest
Latest

ESX-LISA 2.1 is a minor release, which does not need any case code change.

New

  1. ESX host version, kernel and firmware version are visible in XML result.
  2. add test runing date in result XML

Improved

  1. remove iteration feature and related code

Fixed

  1. resolve an issue the running time cannot be calculated when case exited at ForceShutdown status.
Assets 2
Loading

ESX-LISA 2.0

27 Feb 02:51
@henrywang henrywang
2.0
becb725
Compare
Choose a tag to compare
ESX-LISA 2.0

ESX-LISA 2.0 is a milestone for ESX automation testing. New 2.0 release has a lot of new features which are not included in LISA framework. If you're working on ESX automation case developing, please pay more attentions on this release notes because some of fields or settings changed since 2.0 release.

New

  1. Add JUnit XML result file support.
    • this'll be the biggest change for 2.0 release.
    • there'll be a new Report-.xml file in the case result folder.
    • result xml file follows JUnit rules and is acceptable by Jenkins and other CI applications.
  2. Add case running time support.
    • this feature is amazing for us to find how long the test case will last.
    • the running time will be included in result XML file for each test case.
    • the running time will be calculated from system down to system down if case needs reboot, or from system up to determinreboot if case doesn't need reboot.
  3. Add "Skipped" result status support.
    • we really need a new result mark to mark some cases which are not failed at some scenarios but not supported by some scenarios.
    • "Skipped" means not Passed and Failed, but not supported.

Imporved

  1. Non-SUT will not be supported by framework.
    • Non-SUT VM will be controlled by you own, not by framework any more.
    • it's complicated and not convenience for case developer to put some of Non-SUT configurations in framework.
  2. No "Success" result status.
    • after some research on how to mark test result, success is not a good marker for test result.
    • test result will be marked as Passed not Success in most of example.
    • there'll be four result marker in framework, including Passed, Failed, Skipped, Aborted.
  3. all of $True and $False parts of code have been replaced with $true and $false, since there's no $True and $False constant in Powershell but $true and $false instead.
  4. remove Test-Admin function from framework because it's not useful any more.
Assets 2
Loading