Version 6 (modified by Gedare Bloom, on 09/12/18 at 19:45:40) (diff) |
---|
Unit Test Names
Table of Contents
This project about renaming the old names in the testsuite to new ones that are more descriptive.
Directions for Students
To edit names see the google document below:
The tasks will contain the range number you need to edit for example lines 2-10
.
As you can see for some the examples provided (2-4) the old names were:
- tar01
- tar02
- tar03
These names aren't useful as they do not say what the test is about. The new way we are doing it lets us have better names.
If you click on the URL for tar01
it takes you to the test directory that has a few files. The only files you will care about end in *.doc
or *.c
. Sometimes you can read the document to see what the test is about if it does not exist you must look at the C file.
tar01
tests the functions to load a Tar file From various areas.
tar02
is about Loading Tar files and tar03
is loading a Tar file as the root image of RTEMS.
Some Simple Rules To Follow
- Do not make the names long, 3 words maximum.
- We use MashedUpWords, capitalised words with no spaces.
- Do not worry too much about duplicate names for other tests.
- If you are stuck ask in the task instance we will help you.
Help! There are no .c or .doc files!
Some of these tests are virtual in the sense they only have output. This is the .scn
file you may see in there. If this is the case use the old test name and the .scn file to decide what the test is doing.
Directions for Mentors
Verify the patch changes the file names and references to the test name. If you have rights to commit, you may do so, otherwise post the patch to the devel mailing list.