Verify test case description

The verify test case is always executed at the start of any test and is not configurable.

If any of the described checks fail, then none of the test cases are executed. xbtest application software (xbtSW) automatically detects the xbtest hardware IP (xbtIP) present in Alveo Versal Example Design (AVED). The verify test case cross-checks the contents of xbtest metadata for the following:

• Its compatibility with xbtest application software (xbtSW).

• The content of the test JSON file.

xbtest hardware design verification

The SW checks:

• Card setup: PCI link/lane, AMC version (when applicable)

  • E.g. Critical warning (message ID ITF_138) are reported when the current setup is not matching the AVED Management Interface (AMI) expected one.

xbtest hardware IP verification

Once uniquely identified, each xbtest hardware IP (xbtIP) present in the Alveo Versal Example Design (AVED) is checked for:

• Compatibility with xbtest application software (xbtSW) version.

• Basic communication where multiple read/write data transfers to each xbtIP scratch register are performed.

Test JSON file verification

An initial sanity check of the Test JSON file is performed when xbtest application software (xbtSW) starts. All JSON members are checked for validity and compatibility (value type and range) with xbtSW and Card definition JSON file. This also includes a check of the test_sequence parameters for each test case.

• If a test case is described in the test JSON file, but Alveo Versal Example Design (AVED) does not contain the associated xbtIP, then the Verify test case fails.

• If a test case is not described in the test JSON file, the associated xbtIP will stay in its idle state, and it is not considered to be a Verify test case failure.