> >> > achieve the scenario and not try to put everything and the kitchen
> >> > sink in to it. If we see ourselves doing that - we need to break down
> >> > our tests into smaller blocks. They'll still be
> >> > system/integration/live tests only
>> > today.
>> >
>> > On Fri, Jul 19, 2013 at 01:12:14AM +, Alex Huang wrote:
>> > > I disagree. Error handling should be part of our testing.
>> > >
>> > > We should incorporate the simulator into the BVT and regression
>> &g
st the business logic
> > > rather than the provisioning code, the test case should perform all
> > > of the provisioning on the simulator instead. Then simulator can be
> > > programmed to simulate VM stopped failure etc and see how the
> > > business
can be
> > programmed to simulate VM stopped failure etc and see how the
> > business responds to these problems.
> >
> > --Alex
> >
> > > -Original Message-
> > > From: Anthony Xu [mailto:xuefei...@citrix.com]
> > > Sent: Thursday,
and see how the
> business responds to these problems.
>
> --Alex
>
> > -Original Message-
> > From: Anthony Xu [mailto:xuefei...@citrix.com]
> > Sent: Thursday, July 18, 2013 3:02 PM
> > To: dev@cloudstack.apache.org
> > Subject: RE:
rg
> Subject: RE: [rant] stupid test cases
>
> +1 VM can be in "Stopped" state
>
>
> Anthony
>
> -Original Message-
> From: Marcus Sorensen [mailto:shadow...@gmail.com]
> Sent: Wednesday, July 17, 2013 10:47 PM
> To: dev@cloudstack.apache
+1 VM can be in "Stopped" state
Anthony
-Original Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com]
Sent: Wednesday, July 17, 2013 10:47 PM
To: dev@cloudstack.apache.org
Subject: Re: [rant] stupid test cases
I can understand that we may want to test that everythi
essage-
> From: Prasanna Santhanam [mailto:t...@apache.org]
> Sent: Wednesday, July 17, 2013 10:33 PM
> To: CloudStack Dev
> Subject: [rant] stupid test cases
>
> I was just going through one of the automated test cases and I find it really
> silly that there's the followin
I can understand that we may want to test that everything related to the
domain gets cleaned up properly. We have run into all sorts of things when
deleting accounts, for example where resources won't clean up because the
account is gone and we throw null pointers because a bunch of code looks up
a
I was just going through one of the automated test cases and I find it
really silly that there's the following test:
def test_forceDeleteDomain(self):
""" Test delete domain force option"""
# Steps for validations
# 1. create a domain DOM
# 2. create 2 users under
10 matches
Mail list logo
