From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Mon, 4 Jan 2016 15:23:25 -0700 Subject: [U-Boot] [PATCH V2 1/7] test/py: Implement pytest infrastructure In-Reply-To: References: <1449094708-14784-1-git-send-email-swarren@wwwdotorg.org> Message-ID: <568AF0DD.7030109@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 12/19/2015 03:24 PM, Simon Glass wrote: > Hi Stephen, > > On 2 December 2015 at 15:18, Stephen Warren wrote: >> This tool aims to test U-Boot by executing U-Boot shell commands using the >> console interface. A single top-level script exists to execute or attach >> to the U-Boot console, run the entire script of tests against it, and >> summarize the results. Advantages of this approach are: >> >> - Testing is performed in the same way a user or script would interact >> with U-Boot; there can be no disconnect. >> - There is no need to write or embed test-related code into U-Boot itself. >> It is asserted that writing test-related code in Python is simpler and >> more flexible that writing it all in C. >> - It is reasonably simple to interact with U-Boot in this way. >> >> A few simple tests are provided as examples. Soon, we should convert as >> many as possible of the other tests in test/* and test/cmd_ut.c too. >> >> In the future, I hope to publish (out-of-tree) the hook scripts, relay >> control utilities, and udev rules I will use for my own HW setup. >> >> See README.md for more details! > I think it would be worth adding a test that checks for the banner and > the prompt, so we know that other test failures are not due to this > problem. test_000_version.py already does this. It should always be the first test run, hence its odd filename.