Difference between revisions of "Test Standards"

From eLinux.org
Jump to: navigation, search
(Terminology and Framework)
Line 10: Line 10:
 
Here are some things we'd like to standardize in open source automated testing:
 
Here are some things we'd like to standardize in open source automated testing:
 
= Terminology and Framework =
 
= Terminology and Framework =
* test nomenclature (test glossary)
+
* test nomenclature - See the [[Test Glossary]]
 
* CI loop diagram
 
* CI loop diagram
  

Revision as of 12:42, 15 November 2018

This page will be used to collect information about test standards.

meta-documents

A survey of existing test systems was conducted in the Fall of 2018. The survey and results are here: Test Stack Survey


Here are some things we'd like to standardize in open source automated testing:

Terminology and Framework

Test Definition

  • fields
  • file format (json, xml, etc.)
  • meta-data
  • visualization control
    • ex: chart_config.json
  • instructions
    • what tests can be skipped etc.

Test dependencies

  • how to specify test dependencies
    • ex: assert_define ENV_VAR_NAME
    • ex: kernel_config
  • types of dependencies

See Test_Dependencies


Test Execution API (E)

  • test API
  • host/target abstraction
    • kernel installation
    • file operations
    • console access
    • command execution
  • test retrieval, build, deployment
    • test execution:
      • ex: 'make test'
  • test phases

Build Artifacts

  • test package format
    • meta-data for each test
    • test results
    • baseline expected results for particular tests on particular platforms


Run Artifacts

  • logs
  • data files (audio, video)
  • monitor results (power log, trace log)
  • snapshots


Results Format

One aspect of the result format is the result or status code for individual test cases or the test itself. See Test Result Codes

Pass Criteria

  • what tests can be skipped (this is more part of test execution and control)
  • what test results can be ignored (xfail)
  • min required pass counts, max allowed failures
  • thresholds for measurement results
    • requires testcase id, number and operator