Introduction and wiki changes

[Colin Ian King]

On 05/03/13 20:12, John Brier wrote:
> On 03/04/2013 05:44 PM, Colin Ian King wrote:
>> Hi John,
>>
>> Welcome to fwts-devel!
>
> thank you!
>
>> I've created a UEFI subsection in the main fwts reference guide and
>> linked them to that.
>
> That looks good, thanks.
>
>> Many thanks for your contribution to the documentation, feel free to
>> make edits and updates - and let us know if there are any features that
>> need extending, improving or adding.
>
> no problem.
>
> One thing that would be nice but isn't required:
>
> in results.log when a test is reported on the report starts with the
> test description:
>
>
> Check sane DMA Remapping (VT-d).
> ----------------------------------------------------------------------------------------------------
> Test 1 of 1: Check DMA Remapping.
> FAILED [MEDIUM] DevScopeDevNotFound: Test 1, Device scope device not found.
> PASSED: Test 1, Found no DMAR errors in kernel log.
>
> ====================================================================================================
> 1 passed, 1 failed, 0 warnings, 0 aborted, 0 skipped, 0 info only.
> ====================================================================================================
>
>
> What I think would be nice is if in results.log it started out with the
> test name before the description, or at least included it *somewhere* so
> if it fails you can grep for it and find the reasons, kind of like:
>
>
> dmar - Check sane DMA Remapping (VT-d).
> ----------------------------------------------------------------------------------------------------
> Test 1 of 1: Check DMA Remapping.
> FAILED [MEDIUM] DevScopeDevNotFound: Test 1, Device scope device not found.
> PASSED: Test 1, Found no DMAR errors in kernel log.
>
> ====================================================================================================
> 1 passed, 1 failed, 0 warnings, 0 aborted, 0 skipped, 0 info only.
> ====================================================================================================
>
> otherwise if you aren't really familiar with what the test does and
> you've run fwts with a lot of tests you have to review the order you
> passed the tests to fwts in and then count through all the tests reports
> in results.log to find the output you're looking for.

Good idea!

Thanks

Colin
>
>
>