From mboxrd@z Thu Jan 1 00:00:00 1970 From: Philippe REYNES Date: Mon, 6 Jan 2020 11:51:33 +0100 (CET) Subject: [PATCH V2 4/4] pytest: aes: add test for aes192 and aes256 In-Reply-To: References: <1572370173-17178-1-git-send-email-philippe.reynes@softathome.com> <1572370173-17178-5-git-send-email-philippe.reynes@softathome.com> <2012146541.1132041.1572528791781.JavaMail.zimbra@softathome.com> Message-ID: <743863291.594131.1578307893745.JavaMail.zimbra@softathome.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Simon, > Hi Philippe, > > On Thu, 31 Oct 2019 at 07:33, Philippe REYNES > wrote: >> >> Hi Simonn >> >> > Hi Philippe, >> > >> > On Tue, 29 Oct 2019 at 11:29, Philippe Reynes >> > wrote: >> >> >> >> This commit update the aes tests to check the >> >> aes192 and aes256. >> >> >> >> Signed-off-by: Philippe Reynes >> >> --- >> >> test/py/tests/test_aes.py | 118 +++++++++++++++++++++++++++++++++++----------- >> >> 1 file changed, 91 insertions(+), 27 deletions(-) >> > >> > Any way we could write these tests in C? >> >> I'm not sure to understand. Do you mean >> - write this code in C and then call it from python (in pytest) ? >> - write this test in C to implement a ut command (like UT_TIME) ? > > I think I mean both. Write the test in C as a 'ut ae' command, for > example, then call it from a pytest. It should be much faster. Sorry for this late answer, and thanks for the clarification. I've sent a V3 few weeks ago with a test using ut command. Then, this test is automaticaly executed in pytest when runnning ut_subtest. > Regards, > Simon Regards, Philippe