public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Supreeth Venkatesh" <supreeth.venkatesh@arm.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Jeff Brasen (jbrasen@nvidia.com)" <jbrasen@nvidia.com>
Cc: "Jin, Eric" <eric.jin@intel.com>
Subject: Re: [edk2-test] Location of tests for vendor/edk2 specific protocols
Date: Sun, 14 Apr 2019 17:24:44 +0000	[thread overview]
Message-ID: <VE1PR08MB51651EEB8C2E190C6340CA59802A0@VE1PR08MB5165.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <BL0PR12MB2818F88C7A4000705103973DCB280@BL0PR12MB2818.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2059 bytes --]

+ Eric
Thanks Jeff for bringing this up.
As mentioned during our discussion on this topic briefly @ UEFI Plugfest 2019, I definitely like to see these non-standard protocol tests become part of test suite.
However, there has been no proposal yet, though there were proposals related to SBBR (Arm's Server Base Boot Requirements).

Currently, any new platform tests added have to be added to UEFI SCT description files and build scripts for it to be included as part of test suite.
May I request you to create Bugzilla Feature Request @ https://bugzilla.tianocore.org/ under "edk-test" product and "UEFI-SCT" component, as well expand on how you like this to be implemented?

Supreeth

From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Jeff Brasen via Groups.Io
Sent: Friday, April 12, 2019 5:53 PM
To: devel@edk2.groups.io
Subject: [edk2-devel] [edk2-test] Location of tests for vendor/edk2 specific protocols


Now that we have the edk2-test repo with the SCT infrastructure, has there been any thought for where tests that use this for non-standardized protocols should live? My initial thought is along with the protocols in edk2/edk2-platforms. For example if you had Silicon/NVIDIA/Include/Procotol/x.h you would have Silicon/NVIDIA/TestCase/x/ for this. Has there been any thoughts/plans on this?

Thanks,
Jeff

________________________________
This email message is for the sole use of the intended recipient(s) and may contain confidential information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
________________________________

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[-- Attachment #2: Type: text/html, Size: 5492 bytes --]

  reply	other threads:[~2019-04-14 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BL0PR12MB28180D4563D68B32A0181E32CB2E0@BL0PR12MB2818.namprd12.prod.outlook.com>
2019-04-12 22:52 ` [edk2-test] Location of tests for vendor/edk2 specific protocols jbrasen
2019-04-14 17:24   ` Supreeth Venkatesh [this message]
2019-04-30  2:03     ` Eric Jin
2019-05-23 16:55       ` Jeff Brasen

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=VE1PR08MB51651EEB8C2E190C6340CA59802A0@VE1PR08MB5165.eurprd08.prod.outlook.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