Entities

Entities#

  • Test suites generated data which are organized around 4 entities: boards, suites, observations, unitary tests and references

  • The content of each entity is described in the entity model

  • Technically the content of each entity is store in a Parquet file

Parquet files organisation#

  • Each run of a test suite generated data according to the following structure:

        top directory/
        part number/
            board.parquet
            yymmdd1_hhmm1_functional_suite_failed.parquet
            yymmdd1_hhmm1_functional_observations.parquet
            yymmdd1_hhmm1_functional_unitary_tests.parquet

            yymmdd2_hhmm2_collect_suite_passed.parquet
            yymmdd2_hhmm2_collect_observations.parquet
            
        references/
            part_number_version.parquet

  • The top directory is defined by the user. We recommend to use the default values p400 and devkit

  • All files in a top directory can be merged. In that case the files structure is the following:

        merged/
        MERGED
        boards.parquet
        observations.parquet
        suites.parquet
        unitary_tests.parquet

  • The MERGED contain input and output paths as well as the list of serial numbers which have been merged.

file Naming conventions#

Naming convention for entity files is given in the table below. Values between {} are mandatory while those between [] are optional.

entity

grammar

boards

board.parquet

observations

{yymmdd}_{hhmm}_{suite type}_observations.parquet

suites

{yymmdd}_{hhmm}_{suite type}_suite_{outcome}.parquet

unitary_tests

{yymmdd}_{hhmm}_{suite type}_unitary_tests.parquet

references

{part_number}_{version}.parquet

field

definition

example

{yymmdd}_{hhmm}

date and time

251231_1430

{suite type}

type of the suite

functional
collect

{outcome}

test suite outcome

passed
failed

{part number}

see naming board

p400x101x

{version}

semantic versioning without dot

102 for 1.0.2
Contents