[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fwts-devel
Subject:    [FWTS][uefirtauthvar] Test case 12 passed even if UEFI doesn't support authenticated variable
From:       Heyi Guo <heyi.guo () linaro ! org>
Date:       2015-03-16 3:05:50
Message-ID: CAE3ZECp6CQnO-hHzX9WADQ7EYHE808UsprtbvXGbiQUQZxfchg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi all,

Test case 12 of uefiauthvar will pass even if UEFI doesn't support
authenticated variable, while all other cases in this suite will be
skipped.

Test case 12 is to test invalid parameter processing of auth var,
however, if UEFI doesn't support auth var, it will always return
invalid parameter.

Below is the log:
uefirtauthvar  ;INF Test 11 of 13: Authenticated variable test with invalid
uefirtauthvar  ;INF attributes.
uefirtauthvar  ;INF Return status: EFI_INVALID_PARAMETER. A parameter was
uefirtauthvar  ;INF incorrect.
uefirtauthvar  ;INF Test 12 of 13: Test with both authenticated attributes
are
uefirtauthvar  ;INF set.
uefirtauthvar  ;INF Test 13 of 13: Set and delete authenticated variable
created
uefirtauthvar  ;INF by different key test.
uefirtauthvar  ;INF Return status: EFI_INVALID_PARAMETER. A parameter was
uefirtauthvar  ;INF incorrect.

uefirtauthvar  ;SUM 1 passed, 0 failed, 0 warning, 0 aborted, 12 skipped, 0
info
uefirtauthvar  ;SUM only.

I think it is more reasonable to have a basic test before any further
test to make sure UEFI supports auth var, otherwise all test cases
should be skipped. Test 12 being passed is a little confusing.

Thanks.

Heyi Guo

[Attachment #5 (text/html)]

<div dir="ltr"><div class=""><div class="h5"><div dir="ltr"><div class="gmail_quote">Hi all,<br>
<br>
Test case 12 of uefiauthvar will pass even if UEFI doesn&#39;t support<br>
authenticated variable, while all other cases in this suite will be<br>
skipped.<br>
<br>
Test case 12 is to test invalid parameter processing of auth var,<br>
however, if UEFI doesn&#39;t support auth var, it will always return<br>
invalid parameter.<br>
<br>
Below is the log:<br>
uefirtauthvar   ;INF Test 11 of 13: Authenticated variable test with invalid<br>
uefirtauthvar   ;INF attributes.<br>
uefirtauthvar   ;INF Return status: EFI_INVALID_PARAMETER. A parameter was<br>
uefirtauthvar   ;INF incorrect.<br>
uefirtauthvar   ;INF Test 12 of 13: Test with both authenticated attributes are<br>
uefirtauthvar   ;INF set.<br>
uefirtauthvar   ;INF Test 13 of 13: Set and delete authenticated variable created<br>
uefirtauthvar   ;INF by different key test.<br>
uefirtauthvar   ;INF Return status: EFI_INVALID_PARAMETER. A parameter was<br>
uefirtauthvar   ;INF incorrect.<br>
<br>
uefirtauthvar   ;SUM 1 passed, 0 failed, 0 warning, 0 aborted, 12 skipped, 0 info<br>
uefirtauthvar   ;SUM only.<br>
<br>
I think it is more reasonable to have a basic test before any further<br>
test to make sure UEFI supports auth var, otherwise all test cases<br>
should be skipped. Test 12 being passed is a little confusing.<br>
<br>
Thanks.<br>
<span><font color="#888888"><br>
Heyi Guo<br>
</font></span></div><br></div>
</div></div></div>


-- 
fwts-devel mailing list
fwts-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/fwts-devel


[prev in list] [next in list] [prev in thread] [next in thread]