Skip to content

Test Design of TestCase Label

Weihua Hu edited this page May 30, 2018 · 31 revisions

The Design of Label Mechanism of Test Case

The Label of test case is used to filter case conveniently.

The Usage

The labels can be added into test case by below way:

start:test_case_name
description: The description of current case 
os:Linux
hcp:openbmc
label:label1,label2,label3,.....
.....
end

Suppose in future developer/FVT can filter expected case list by below way:

# xcattst -s (label1 and label2) or (label3 and label4) or (! label5)

Label Mechanism

There are two primary dimensions of labels, ones are ones are horizontal dimension labels that decides the category of cases.

Vertical Dimension Labels

Vertical dimension labels that decides the running order of cases. As long as follow below order, anyone can finish a whole test against xCAT based on a brand new environment.

| level | Label name|case example| |-------|-----------| |1|xcat_install|install_xCAT_on_rhels_sles| |2|mn_only|lsdef_,xcatd_restart| |3|sn_diskful|SN_setup_case| | |sn_diskless|SN_diskless_setup_case| |4|flat_cn_diskful|reg_linux_diskfull_installation_flat| | |flat_cn_diskless|reg_linux_diskless_installation_flat| | |hierarchy_cn_diskful|reg_linux_diskfull_installation_hierarchy| | |hierarchy_cn_diskless|reg_linux_diskless_installation_hierarchy| |5|cn_bmc_ready|rpower_| | |cn_os_ready|xdcp_*| |6|others|nodeset_cmd|

There are some rules for vertical dimension labels

  • It is mandatory label. That means one cases must have ONE label in above table and belong to one specific level.

  • Level 1,3,4 can be treated as part of test environment setup. That means if need not to setup environment in your case, you can skip some levels.

    For example:

    • If you have set up a MN with expected xcat installed and want to do smoking test, just need to run all cases with mn_only label.
    • If you have a MN with brand new os and connected to a CN, want to test hardware control against CN, just need to filter cases from level 1 and level 5, skip level 2-4.
  • There are more than one labels in level 3/4/5, when create a kind of whole test against xCAT, only one label in these levels can be chosen.

Horizontal Dimension Labels

db,xcatd, hctrl_gen,hctrl_hmc,hctrl_fsp,hctrl_ipmi,hctrl_openbmc provision,go-xcat,statelite invoke_provison

console, discovery docker GPU KIT migration network postscripts restapi Switch PDU HA

go-coserver dhcp dns IB packaging parallel_cmds scaling security updatenode file-sync xcatprobe cumulus virtualization firmware performance

News

History

  • Oct 22, 2010: xCAT 2.5 released.
  • Apr 30, 2010: xCAT 2.4 is released.
  • Oct 31, 2009: xCAT 2.3 released. xCAT's 10 year anniversary!
  • Apr 16, 2009: xCAT 2.2 released.
  • Oct 31, 2008: xCAT 2.1 released.
  • Sep 12, 2008: Support for xCAT 2 can now be purchased!
  • June 9, 2008: xCAT breaths life into (at the time) the fastest supercomputer on the planet
  • May 30, 2008: xCAT 2.0 for Linux officially released!
  • Oct 31, 2007: IBM open sources xCAT 2.0 to allow collaboration among all of the xCAT users.
  • Oct 31, 1999: xCAT 1.0 is born!
    xCAT started out as a project in IBM developed by Egan Ford. It was quickly adopted by customers and IBM manufacturing sites to rapidly deploy clusters.
Clone this wiki locally