From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=pass header.i=@nxp.com header.s=selector1 header.b=tVULRUiW; spf=pass (domain: nxp.com, ip: 40.107.8.71, mailfrom: prakriti.chauhan@nxp.com) Received: from EUR04-VI1-obe.outbound.protection.outlook.com (EUR04-VI1-obe.outbound.protection.outlook.com [40.107.8.71]) by groups.io with SMTP; Tue, 30 Apr 2019 05:27:49 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nxp.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/Z4X4d3d/bMPGbPCxBLq86n73RNHD5xUU29bKD95h8A=; b=tVULRUiWZjqE9gO9OC6ii2i9WKCdBWd6HtSHg1BkYyJ6fNq8/44d+hpSNT5ffsFwJdVz+lDcGvi9QiX5xn1B2rQjCM93nG4HjQfo/WxuvHh1ppQdULaIOunSW3NE61CMZI+IGKIZsBJKi55T2D8iE8+Qts910rQpRkky9ih3dTQ= Received: from DB7PR04MB4331.eurprd04.prod.outlook.com (52.135.131.150) by DB7PR04MB5548.eurprd04.prod.outlook.com (20.178.106.93) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1856.10; Tue, 30 Apr 2019 12:27:46 +0000 Received: from DB7PR04MB4331.eurprd04.prod.outlook.com ([fe80::5900:ebf8:67b8:c0ca]) by DB7PR04MB4331.eurprd04.prod.outlook.com ([fe80::5900:ebf8:67b8:c0ca%2]) with mapi id 15.20.1835.018; Tue, 30 Apr 2019 12:27:46 +0000 From: "Prakriti Chauhan" To: Supreeth Venkatesh , "devel@edk2.groups.io" Subject: Re: [EXT] RE: [edk2-test]Regarding using any shell command in SCT Thread-Topic: [EXT] RE: [edk2-test]Regarding using any shell command in SCT Thread-Index: AdT6xzZ9xMdFIZKHQc+V4ozjAMt4LQBH/i+wAHZ+4LAAK3ElUA== Date: Tue, 30 Apr 2019 12:27:46 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=prakriti.chauhan@nxp.com; x-originating-ip: [92.120.0.3] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: b478be33-05d7-48ab-1d1d-08d6cd67406d x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0;PCL:0;RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(4618075)(2017052603328)(7193020);SRVR:DB7PR04MB5548; x-ms-traffictypediagnostic: DB7PR04MB5548: x-ms-exchange-purlcount: 1 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:9508; x-forefront-prvs: 00235A1EEF x-forefront-antispam-report: SFV:NSPM;SFS:(10009020)(396003)(376002)(346002)(39860400002)(136003)(366004)(189003)(199004)(40434004)(229853002)(26005)(102836004)(186003)(53546011)(486006)(6506007)(44832011)(5660300002)(476003)(446003)(11346002)(66066001)(6436002)(71200400001)(71190400001)(55016002)(316002)(478600001)(110136005)(97736004)(2501003)(5024004)(14444005)(256004)(52536014)(33656002)(74316002)(7736002)(76176011)(14454004)(7696005)(966005)(99286004)(25786009)(606006)(76116006)(8676002)(81166006)(81156014)(8936002)(68736007)(86362001)(3846002)(66476007)(6116002)(6306002)(6246003)(53936002)(64756008)(66446008)(790700001)(66556008)(73956011)(2906002)(9686003)(54896002)(66946007)(236005);DIR:OUT;SFP:1101;SCL:1;SRVR:DB7PR04MB5548;H:DB7PR04MB4331.eurprd04.prod.outlook.com;FPR:;SPF:None;LANG:en;PTR:InfoNoRecords;MX:1;A:1; received-spf: None (protection.outlook.com: nxp.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: GuNyt9CtSl0aiHpbpBM96K0NXoPeoRrjue1lSK7OBYOQB8PKMLa658wRcWW6rt2yC9vQRgza2GUQqaahyYuskxN7SpkVN+d8zZUKG/DHAelC1P917ddl59QoxmzR7WWbRcCQDpXvaoYBgHrqOjOT1RjXVSnf1P09AL03k0YrPlRwe6eaKiCxY6geDoLU8qYlD4QJaUVTtISJHQbN0XxppE6VUEtN6BpppOY0lj8gQmgUzsRY5+Aik8Ns58XfqpTt9Y5zIRmp5ptwLEDis422Q+QSf4AIcYOY8uU7kxEiYaM4M1JmMZVeBXaEEJZH/fwpgKeN2rwsz0Jk2gcdGinMFjDbQExJj4TdqR+a4g9v5sYQwYgmkknJBz+5gGYwm7Uga+FtFeK5U2bo0eQXGjLJSrX6u9VrGebjdVhi5PjEeso= MIME-Version: 1.0 X-OriginatorOrg: nxp.com X-MS-Exchange-CrossTenant-Network-Message-Id: b478be33-05d7-48ab-1d1d-08d6cd67406d X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Apr 2019 12:27:46.5481 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR04MB5548 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_DB7PR04MB43318EE5425726FE92A67EC18B3A0DB7PR04MB4331eurp_" --_000_DB7PR04MB43318EE5425726FE92A67EC18B3A0DB7PR04MB4331eurp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Supreeth, Can you tell how to compile Specific test case of SCT instead of compiling = whole SCT. Thanks, Prakriti From: Prakriti Chauhan Sent: Sunday, April 28, 2019 6:56 PM To: Supreeth Venkatesh ; devel@edk2.groups.io; = Jin, Eric Subject: RE: [EXT] RE: [edk2-test]Regarding using any shell command in SCT Hi, I was asking about how to test EFI_SHELL_PROTOCOL. Thanks, Prakriti From: Prakriti Chauhan Sent: 26 April 2019 10:30 To: Supreeth Venkatesh > Subject: RE: [EXT] RE: [edk2-test]Regarding using any shell command in SCT Supreeth, I was asking about how to test EFI_SHELL_PROTOCOL. Thanks, Prakriti From: Supreeth Venkatesh > Sent: Wednesday, April 24, 2019 11:54 PM To: Prakriti Chauhan >; devel@edk2.groups.io Cc: Jin, Eric > Subject: [EXT] RE: [edk2-test]Regarding using any shell command in SCT Caution: EXT Email Changing subject line to include [edk2-test]. + Eric Prakriti, With the disclaimer that UEFI SCT is intended for testing against UEFI spec= ification, I will try to answer your question in the way I interpreted it. I am not sure whether you are asking how to test EFI_SHELL_PROTOCOL or is i= t related to a non uefi standard device interface you want to test? Assuming it as the latter and with the limited information you mentioned ab= out your requirement, I am assuming you will have a non-standard Protocol/D= river for your device and want to test those APIs. With the above assumption, you can follow any of the standard test cases as= reference for implementing your own test. Example below: https://github.com/tianocore/edk2-test/tree/master/uefi-sct/SctPkg/TestCase= /UEFI/IHV/Protocol/DeviceIo/BlackBoxTest Eric can provide more information based on detailed explanation of your req= uirements. Thanks, Supreeth From: Prakriti Chauhan > Sent: Wednesday, April 24, 2019 4:28 AM To: Supreeth Venkatesh >; devel@edk2.groups.io Subject: Regarding using any shell command in SCT Hi, I want to test if my interface is working or not using SCT framework, like = give IP address to interface and then run ping command. Any pointers how can I achieve same? Thanks, Prakriti IMPORTANT NOTICE: The contents of this email and any attachments are confid= ential and may also be privileged. If you are not the intended recipient, p= lease 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. --_000_DB7PR04MB43318EE5425726FE92A67EC18B3A0DB7PR04MB4331eurp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Supreeth,

 

 

 

Can you tell how to compile Specific test case of SC= T instead of compiling whole SCT.

 

 

Thanks,

Prakriti

 

From: Prakriti Chauhan
Sent: Sunday, April 28, 2019 6:56 PM
To: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>; devel@edk= 2.groups.io; Jin, Eric <eric.jin@intel.com>
Subject: RE: [EXT] RE: [edk2-test]Regarding using any shell command = in SCT

 

Hi,

 

 

 

I was asking about how to test EFI_SHELL_PROTOCOL.

 

 

 

Thanks,

Prakriti

 

From: Prakriti Chauhan
Sent: 26 April 2019 10:30
To: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>
Subject: RE: [EXT] RE: [edk2-test]Regarding using any shell command = in SCT

 

Supreeth,

 

 

 

I was asking about how to test EFI_SHELL_PROTOCOL.

 

 

Thanks,

Prakriti

 

 

From: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>
Sent: Wednesday, April 24, 2019 11:54 PM
To: Prakriti Chauhan <prakriti.chauhan@nxp.com>; devel@edk2.groups.io
Cc: Jin, Eric <eric.jin@int= el.com>
Subject: [EXT] RE: [edk2-test]Regarding using any shell command in S= CT

 

Caution: EXT Email

Changing subject line to include [edk2-test].

+ Eric

 

Prakriti,

With the disclaimer that UEFI SCT is intended for te= sting against UEFI specification, I will try to answer your question in the= way I interpreted it.

 

I am not sure whether you are asking how to test EFI= _SHELL_PROTOCOL or is it related to a non uefi standard device interface yo= u want to test?

Assuming it as the latter and with the limited infor= mation you mentioned about your requirement, I am assuming you will have a = non-standard Protocol/Driver for your device and want to test those APIs.

With the above assumption, you can follow any of the= standard test cases as reference for implementing your own test. Example b= elow:

https://github.com/tianocore/edk2-test/tree/master/uefi-sct/SctPkg/= TestCase/UEFI/IHV/Protocol/DeviceIo/BlackBoxTest

 

Eric can provide more information based on detailed = explanation of your requirements.

 

Thanks,

Supreeth

 

From: Prakriti Chauhan <prakriti.chauhan@nxp.com>
Sent: Wednesday, April 24, 2019 4:28 AM
To: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>; devel@edk2.groups.io
Subject: Regarding using any shell command in SCT

 

Hi,

 

 

&nb= sp;

I want t= o test if my interface is working or not using SCT framework, like give IP = address to interface and then run ping command.

 

Any poin= ters how can I achieve same?

 

 

 

Thanks,

Prakriti

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

--_000_DB7PR04MB43318EE5425726FE92A67EC18B3A0DB7PR04MB4331eurp_--