[Automated-testing] conventions for test invocation/execution, etc.

Tim.Bird at sony.com Tim.Bird at sony.com
Thu Sep 5 11:59:22 PDT 2019



> -----Original Message-----
> From: Veronika Kabatova 
> 
> ----- Original Message -----
> > From: "Tim Bird" <Tim.Bird at sony.com>
> > Sent: Thursday, September 5, 2019 3:40:59 AM
...

> > If I recall correctly, doesn't CKI support a specific name for the test
> > program: runtest.sh?
> >
> 
> CKI uses Beaker [0] so we are forced to use the invocation Beaker uses. This
> means having a Makefile with a "make run" target (which can call build if
> needed) that executes the test. The test file is called runtest.sh as you
> mentioned. I don't think this naming is enforced by Beaker and you should
> be
> able to put a different file to be executed into the Makefile if you want to
> but I've never seen a different name used in practice so far.
> 
> [0] https://beaker-project.org

OK - thanks.
 -- Tim



More information about the automated-testing mailing list