Hi Raj,
Are you going to remove the groups?That what we had earlier before we
introduce the test groups.But we should be able to run other test cases
except server restart test in parallel as we have unique artifacts ids.I
think if we had the correct dependency grouping it should work.
Anyway I d
Hi Isuru,
I have tried listing all the classes in testng.xml, but the listed order is
not preserved in execution. I am further investigating it. If we get it to
work, we can follow this approach, IMO. This is a one time task, there is
no overhead. We just need to list our new test classes in testn
Let me have a look at it. We didn't get the timeout issue locally, it only
happens in jenkins builder.
@Akila, +1 to add other groups as dependencies in server restart testcase.
Thanks,
Raj.
On Wed, Nov 25, 2015 at 4:52 PM, Isuru Haththotuwa
wrote:
> I see that we have upgraded TestNG version
I see that we have upgraded TestNG version [1]. Do we still have the issue
where the tests are run in parallel, even if we specify not to?
[1]. https://issues.apache.org/jira/browse/STRATOS-1627
On Wed, Nov 25, 2015 at 4:23 PM, Akila Ravihansa Perera
wrote:
> Hi Gayan,
>
> I don't think timeout
Hi Gayan,
I don't think timeout value is the root cause here. It already has a
timeout value of 30 (5mins). Can you check the stratos-integration.log
and see whether Stratos restart test case was executed in middle of this
test case?
I noticed that Stratos restart test case only depends on
"s
With the release build I found that IaasProviderAttributeTestCase failed
due to the time-out[1]. Seems this is intermittent. I have increased the
timeout of that test case by introducing separate timeout value for that
test case.I will trigger another build with that.
[1]
[INFO]
testIaasProviderA
