Bug 9921

Write a set of guides for naming tests for mainly 2 reasons: to facilitate a filtering feature at test listing & execution and to have a more consistent test list.

Currently, filtering would be highly ineffective due to the repetition of the fields in the test name. i.e. "wic.Wic.test_wic_image_type" this allows no differentiation of module/submodule. Another example: recipetool.RecipetoolAppendsrcTests.test_recipetool_appendsrcfile_srcdir_basic

This guide should be written at the QA wiki and should also trigger a modification of the existing tests.

Test naming guide proposal for oe-selftest:

Test name composition: <Module>.<submodule>.<testname> (as currently implemented).

  - Module: the python library where the classes/tests live. Name it after the component you are applying tests to: i.e. bitbake, wic, sstates, etc. 

  - Submodule: a division within the library (usually the class)that tests a specific part of the module. i.e. from bitbake, test memres.

  - test name: the function that implements the test, named after the feature that it tests. several tests can exist for the same feature (negative, boundary, etc) so it can be name<consecutive> like name01, name02.