Post by ahartmann on Dec 8, 2013 13:30:36 GMT -5
Hi Martin,
I have a list of suggestions that would make TestApe even
more useful for me (and I hope for others too).
Please let me know what you think about these feature requests:
1. Add __FILE__ and __LINE__ information to the VALIDATE macros
2. Support the @\path\to\objects.file syntax for MSVC link.exe
3. Display a test summary at the end of all tests
4. Add more integer formating options to VALIDATE
1. Add __FILE__ and __LINE__ information to the VALIDATE macros
Failed test cases can display this to information
to allow direct jump to the source in an editor.
For automatic evaluation, it would be best to display
this in one line, e.g.:
../HelloTestApe/main.c:13: FAILED verify res: (expected 1, was 2)
Maybe the output could be adjustable by a command line option.
Later, one could think about a callback function that does the
output formating according to the users needs (which could be
very different).
2. Support the @\path\to\objects.file syntax for MSVC link.exe
Microsoft link.exe allows to specify the list of objects through
a (temporary) file, which is useful for long object lists.
Qmake uses this feature to pass the builded object files to link.exe.
The objects are separated by whitespaces and/or newlines.
In the examples I tested it was always a one-line text file with
the list of objects separated by spaces.
If TestApe detects such a file starting with "@", it should simply
pass it to link.exe the same way. If TestApe needs to inspect the
list, it should open the specified file and treat it like the
arguments at the command line.
3. Display a test summary at the end of all tests
I think this is a great feature when writing new tests. You know,
for example, you have 43 passing tests and add another one. You now
suppose to have 44 passing tests. This is a nice hint if you forgot
to register your new test with EXECUTE().
The summary could look like this (see Unity or CppUTest for example):
OK 43 tests, 43 passed, 0 errors, 0 skipped
4. Add more integer formating options to VALIDATE
Some test frameworks like Unity or CppUTest support different
formatings for integers.
Especially for embedded developers, the hexadecimal output is important:
- format as 8 bit hexadecimal: expected 0x55 was 0xAA
- format as 16 bit hexadecimal: expected 0x0123 was 0x0321
- format as 32 bit hexadecimal: expected 0x00C00FEE was 0xDEADBEEF
Best regards,
André
I have a list of suggestions that would make TestApe even
more useful for me (and I hope for others too).
Please let me know what you think about these feature requests:
1. Add __FILE__ and __LINE__ information to the VALIDATE macros
2. Support the @\path\to\objects.file syntax for MSVC link.exe
3. Display a test summary at the end of all tests
4. Add more integer formating options to VALIDATE
1. Add __FILE__ and __LINE__ information to the VALIDATE macros
Failed test cases can display this to information
to allow direct jump to the source in an editor.
For automatic evaluation, it would be best to display
this in one line, e.g.:
../HelloTestApe/main.c:13: FAILED verify res: (expected 1, was 2)
Maybe the output could be adjustable by a command line option.
Later, one could think about a callback function that does the
output formating according to the users needs (which could be
very different).
2. Support the @\path\to\objects.file syntax for MSVC link.exe
Microsoft link.exe allows to specify the list of objects through
a (temporary) file, which is useful for long object lists.
Qmake uses this feature to pass the builded object files to link.exe.
The objects are separated by whitespaces and/or newlines.
In the examples I tested it was always a one-line text file with
the list of objects separated by spaces.
If TestApe detects such a file starting with "@", it should simply
pass it to link.exe the same way. If TestApe needs to inspect the
list, it should open the specified file and treat it like the
arguments at the command line.
3. Display a test summary at the end of all tests
I think this is a great feature when writing new tests. You know,
for example, you have 43 passing tests and add another one. You now
suppose to have 44 passing tests. This is a nice hint if you forgot
to register your new test with EXECUTE().
The summary could look like this (see Unity or CppUTest for example):
OK 43 tests, 43 passed, 0 errors, 0 skipped
4. Add more integer formating options to VALIDATE
Some test frameworks like Unity or CppUTest support different
formatings for integers.
Especially for embedded developers, the hexadecimal output is important:
- format as 8 bit hexadecimal: expected 0x55 was 0xAA
- format as 16 bit hexadecimal: expected 0x0123 was 0x0321
- format as 32 bit hexadecimal: expected 0x00C00FEE was 0xDEADBEEF
Best regards,
André