cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Will Stevens <wstev...@cloudops.com>
Subject Re: ACS Testing
Date Thu, 21 Apr 2016 02:16:51 GMT
Ok, to keep things reasonable to start with, I am going to try to build
suites specifically to test different PRs and then start consolidating them
once I can validate the tests that are working into a 'full' test run.

If anyone has a list of tests which they think is a complete list of
working tests, I would happily review it.  :)

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Wed, Apr 20, 2016 at 6:17 PM, Daan Hoogland <daan.hoogland@gmail.com>
wrote:

> I think we want to test both, but we will have to consider and judge each
> test on it's own merits.
>
> We can start a run with everything from both directories as a parallel
> track and then see what to do with the failing ones.
>
> On Wed, Apr 20, 2016 at 11:52 PM, Will Stevens <williamstevens@gmail.com>
> wrote:
>
> > This is going to be a stupid question, but I don't know the answer, so I
> > would like some guidance on this.
> >
> > Under 'cloudstack/test/integration/' there are the following folders:
> > - component
> > - smoke
> > - plugins
> > - testpaths
> >
> > Looking specifically at 'components' and 'smoke', there seems to be a lot
> > of overlap in test cases.  Why would you test one vs the other?  Should
> we
> > be testing both?
> >
> > Thanks,
> >
> > Will
> > - The n00b RM -
> >
>
>
>
> --
> Daan
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message