<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="ProgId" content="Word.Document"> <meta name="Generator" content="Microsoft Word 15"> <meta name="Originator" content="Microsoft Word 15"> <link rel="File-List" href="cid:filelist.xml@01D67601.2ECFBF20"><link rel="Edit-Time-Data" href="cid:editdata.mso"><style></style> </head> <body lang="EN-US" link="blue" vlink="#954F72" style="tab-interval:.5in"> <div class="WordSection1"> Hi,<o:p></o:p> <o:p> </o:p> I would also like to add that UEFI SCTs and Unit Testing are different scopes of testing.<o:p></o:p> <o:p> </o:p> The UEFI SCTs are system level conformance tests that require and entire platform FW image to execute on a platform and they focus on measuring if a conformant set of UEFI interfaces are present. The UEFI SCTs need to run correctly no matter what the underlying implementation is, so these are black box tests and do not have a large number of test cases against each API. We can only implement test cases based on the API definitions in the UEFI Specifications.<o:p></o:p> <o:p> </o:p> The UnitTestFrameworkPkg provide both host and target based testing environment, and the scope of a unit test is a single C/ASM function, and that single function can either be public APIs or internal worker functions. It supports both black box and white box testing. The white box testing approach allows all code paths to be exercised with different input data patterns to verify that a function works as expected for all inputs. The host based tests run as an application and do not require a full platform FW image. This allows the unit test to test code paths that may be very rare in full system testing or require HW to be broken to be seen in full system testing. This means the UnitTestFrameworkPkg has the potential to provide much greater code coverage than UEFI SCTs.<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> <o:p> </o:p> Mike<o:p></o:p> <o:p> </o:p> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Bret Barkelew via groups.io Sent: Tuesday, August 18, 2020 11:00 PM To: devel@edk2.groups.io; tigerliu@zhaoxin.com Subject: Re: [edk2-devel] question about UnitTest Framework<o:p></o:p> </div> </div> <o:p> </o:p> Correct. It’s possible that we can have some sort of test reunion at some point, but SCT is largely for interfaces and spec compliance, and the UnitTest Framework is for implementation business logic, CI, and code coverage.<o:p></o:p> <o:p> </o:p> - Bret<o:p></o:p> <o:p> </o:p> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: <a href="mailto:tigerliu=zhaoxin.com@groups.io">Tiger Liu(BJ-RD) via groups.io</a> Sent: Tuesday, August 18, 2020 10:17 PM To: <a href="mailto:devel@edk2.groups.io">devel@edk2.groups.io</a>; <a href="mailto:TigerLiu@zhaoxin.com"> Tiger Liu(BJ-RD)</a> Subject: [外部] Re: [edk2-devel] question about UnitTest Framework<o:p></o:p> </div> <o:p> </o:p> Hi, After studying previous discuss mail, UnitTest Framework is work for Continuous Integration mechanism. Code writer will provide some unit test functions, maybe they could also do code coverage test. Thanks -----邮件原件----- 发件人: <a href="mailto:devel@edk2.groups.io"> devel@edk2.groups.io</a> <<a href="mailto:devel@edk2.groups.io">devel@edk2.groups.io</a>> 代表 Tiger Liu(BJ-RD) 发送时间: 2020年8月13日 16:03 收件人: <a href="mailto:devel@edk2.groups.io"> devel@edk2.groups.io</a> 主题: [edk2-devel] question about UnitTest Framework Hi, Experts: I have a question about UnitTest Framework. UEFI Code has included some test infrastructure, such as: PI-SCT / SCT / FWTS etc. So, why we introduce a new UnitTest Framework? Is it mainly for Code Coverage test? Thanks 保密声明： 本邮件含有保密或专有信息，仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。 CONFIDENTIAL NOTE: This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited. 保密声明： 本邮件含有保密或专有信息，仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。 CONFIDENTIAL NOTE: This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.<o:p></o:p> <o:p> </o:p> <div> </o:p> </div> </div> </body> </html> <div width="1" style="color:white;clear:both">_._,_._,_</div> <hr> Groups.io Links: You receive all messages sent to this group. <a target="_blank" href="https://edk2.groups.io/g/devel/message/64446">View/Reply Online (#64446)</a> | | <a target="_blank" href="https://groups.io/mt/76163664/1813853">Mute This Topic</a> | <a href="https://edk2.groups.io/g/devel/post">New Topic</a> <a href="https://edk2.groups.io/g/devel/editsub/1813853">Your Subscription</a> | <a href="mailto:devel+owner@edk2.groups.io">Contact Group Owner</a> | <a href="https://edk2.groups.io/g/devel/unsub">Unsubscribe</a> [edk2-devel-archive@redhat.com] <div width="1" style="color:white;clear:both">_._,_._,_</div>