[Toaster] toaster automated testing

[Damian, Alexandru]

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.

Cheers,
Alex

On Fri, May 8, 2015 at 2:52 PM, Richard Purdie <
richard.purdie at linuxfoundation.org> wrote:

> On Fri, 2015-05-08 at 14:47 +0100, Damian, Alexandru wrote:
> > I've been progressing a bit on the automated Toaster testing. We need
> > to get this step in a reasonable shape in order to help with the
> > massive refactoring that we planned for 1.9 M1.
> >
> > As part of this effort, I moved the existing automated UI testing from
> > a poky-branch to yocto-TTS, as it stand no chance for successful
> > merging upstream in Poky.
>
> Why wouldn't we want to merge automated tests for toaster somewhere like
> bitbake?
>
> Cheers,
>
> Richard
>
>
>


-- 
Alex Damian
Yocto Project
SSG / OTC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/toaster/attachments/20150508/dfa12018/attachment.html>