Hi Josch, On 07-12-2018 23:11, Johannes 'josch' Schauer wrote: > then further below under "defined features" it says: > >> test-name >> Set an explicit test name for the log heading and the ``summary`` file >> for a ``Test-Command:`` inline test. When not given, these are >> enumerated like ``command1``. > > But this does not explain the syntax of how a test name is actually > specified. Does one just write it in the Features field? Or is it > test-name:thename or does one have to quote something?
I totally agree with you. I have been staring at that line last week when I wanted to use it. The correct syntax is: Features: test-name=blablabla > My use case: I have a test that uses Test-Command but the output becomes > hard to understand if tests are just named command1, command2 and so > forth. Thus I want to give them meaningful names. That is indeed exactly why we have this feature. > Unfortunately under "Test-Command" it also says "This is mutually > exclusive with the ``Tests:`` field". Is there a practical reason why > these fields are mutually exclusive? Naively, I would've expected, that > when Test-Command is given, then it doesn't look for a script but > instead executes the command but that it anyways takes the test name > from the "Tests" field. It seems unnecessarily complicated to require > the test-name feature thing. Well, the practical reason is that this feature was added way later than the original code and there are sanity checks in place. I guess that Martin didn't consider your proposal and just left the old code in place. Paul
signature.asc
Description: OpenPGP digital signature
