Test definition survey

From eLinux.org
Revision as of 18:16, 9 January 2019 by Tim Bird (talk | contribs) (add page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Here is a list of test definition fields, attributes, file formats, operations, instructions, functions, etc. (I won't know what even what they consist of until I see them).

This is the object in your test system that "defines" what a test is. It likely has meta-data about the program to run, how to get the program started, maybe what things are required for the program to run, how the results should be interpreted, etc.

Survey - link to test definitions

Here is a link to test definitions in different systems: One simple, one characteristic, and link to repository containing lots of them:

Fuego

* (simple) Functional.hello_world: https://bitbucket.org/tbird20d/fuego-core/src/master/engine/tests/Functional.hello_world/
* (characteristic) Benchmark.bonnie: https://bitbucket.org/tbird20d/fuego-core/src/master/engine/tests/Benchmark.bonnie/
* (repository) https://bitbucket.org/tbird20d/fuego-core/src/master/engine/tests/

files:

* fuego_test.sh
* spec.json
* parser.py
* criteria.json
* test.yaml
* chart_config.json
* reference.json
* docs
* (test program source)

fields:

* (to be filled out)