From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: Blibbet <blibbet@gmail.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: Unit tests and the EDK2
Date: Sun, 6 Nov 2016 19:03:33 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F564840F01@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <a1bbd75d-bdb0-ba9c-4aaa-06f4dd339a94@gmail.com>
Hi,
A test framework for EDK2 is one of my highest priorities to
complete before the end of the year.
I am evaluating a number of options and hope to put together
a complete proposal as an RFC for consideration in the next
few weeks.
Thanks,
Mike
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Blibbet
> Sent: Sunday, November 6, 2016 9:26 AM
> To: edk2-devel@lists.01.org
> Subject: Re: [edk2] Unit tests and the EDK2
>
> On 11/06/2016 01:57 AM, Matt Lazarowitz wrote:
> > I would like to find out if anyone has experience with an off the shelf
> > unit test framework in the EDK2.[...]
>
> If you haven't looked at it, two months ago Microsoft open-sourced some
> EDK2-centric unit tests.
>
> https://firmwaresecurity.com/2016/09/23/microsoft-uefi-unit-tests/
>
> Lee Fisher
>
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2016-11-06 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 9:57 Unit tests and the EDK2 Matt Lazarowitz
2016-11-06 17:25 ` Blibbet
2016-11-06 19:03 ` Kinney, Michael D [this message]
2016-11-06 19:57 ` Marvin H?user
2016-11-06 21:06 ` Kinney, Michael D
2016-11-07 3:01 ` Matt Lazarowitz
2016-11-06 20:14 ` Blibbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E92EE9817A31E24EB0585FDF735412F564840F01@ORSMSX113.amr.corp.intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox