[marvin tests] interpreting results

2015-04-24 Thread Abhinandan Prateek
Have been trying to run some marvin test cases. Need to know how to interpret the result. On running test cases I see several success and failure messages. Lets take example of each from output of /root/cloudstack/test/integration/component/test_acl_isolatednetwork.py on ACS 4.5, taking a samp

Re: [marvin tests] interpreting results

2015-04-24 Thread Gaurav Aradhye
Hi Abhi, FAILED indicates it’s an assertion error. Even if the test case is expecting a failure, it must have been written in such a way that when an operation fails, test case passes. Here it indicates that operation which should have failed has succeeded, might be a product issue. Exception

Re: [marvin tests] interpreting results

2015-04-24 Thread Gaurav Aradhye
Abhi, went through the logs. The tests which have FAILED have failed because product behavior is not as expected in the test. Tests with Exception seem have issue in test code. Regards, Gaurav Aradhye On Apr 24, 2015, at 4:47 PM, Abhinandan Prateek wrote: > Attaching the logs. This is with la

Re: [marvin tests] interpreting results

2015-04-24 Thread Abhinandan Prateek
Hi Gaurav, Your réponse will definitely help us in focusing in the right direction. Thanks a lot ! -abhi > On 24-Apr-2015, at 7:11 pm, Gaurav Aradhye wrote: > > Abhi, went through the logs. The tests which have FAILED have failed because > product behavior is not as expected in the test.

Re: [marvin tests] interpreting results

2015-04-28 Thread sebgoa
-catching up on email after a break- This is great to see guys, definitely we need to understand our tests better and expand the coverage. With ASF purchasing more resources on Travis, this is still a very valuable infrastructure to run our CI/BVT until we have a different type of infra. Speed