On Fri, May 8, 2015 at 5:32 PM, Richard Purdie < [email protected]> wrote:
> On Fri, 2015-05-08 at 15:21 +0100, Damian, Alexandru wrote: > > My thinking is that unit tests, that are to be run inside the django > > application, should be in bitbake. > > > > These tests are integration and smoke tests, with a long list of > > dependencies (selenium, browsers, w3c-validator, various other tools) > > and I wouldn't want to bring these dependencies into Bitbake. > > Furthermore, the code structure is not integrated at all with current > > code in Toaster, Bitbake, or oe-selftest framework. It doesn't fit in. > > > > Unit tests that validate individual Toaster features and bug fixes are > > to be implemented in Django unit test framework, and live inside > > Bitbake. > > > I agree they don't belong alongside the existing tests, we could put > them in a contrib style directory though (I'm open to suggestions) and > document that there are certain dependencies needed to use them? > > Yep, this is do-able - they will have no relationship at code level with existing infrastructure though; separate requirements.txt and README will be provided to guide usage. Is this ok? > Cheers, > > Richard > > -- Alex Damian Yocto Project SSG / OTC
-- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
