From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Damian, Alexandru" <alexandru.damian@intel.com>
Cc: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: toaster automated testing
Date: Fri, 08 May 2015 17:32:49 +0100 [thread overview]
Message-ID: <1431102769.8074.294.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ2CSBtN+on15wbMZcM2Zxqhe4m-xFwya8Br7jCNXAqBdCXiaw@mail.gmail.com>
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?
Cheers,
Richard
next prev parent reply other threads:[~2015-05-08 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 13:47 toaster automated testing Damian, Alexandru
2015-05-08 13:52 ` Richard Purdie
2015-05-08 14:21 ` Damian, Alexandru
2015-05-08 16:32 ` Richard Purdie [this message]
2015-05-08 16:41 ` Damian, Alexandru
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1431102769.8074.294.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexandru.damian@intel.com \
--cc=toaster@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.