Hi Raj, Yes. A good point. I didn't carefully analysed the test cases. But I guess the problem is that we have automated the samples as test cases, where all the samples do basic stuff again and again.
I think the solution should be a master test plan, building a story to start with the simple use-case, and grow that to cover all the use cases, with the same artifacts(with maximum re-usability). Thanks. On Sat, Nov 21, 2015 at 9:58 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> wrote: > Devs, > > We don't need to test the same test scenarios in different test cases. For > example, "testing whether any used policies can be removed or not" should > be tested only in one test case. But we are doing this check in couple of > test cases. This is an unnecessary delay in running integration tests. > > IMO, > > - we need to test a scenario only in one test case > - we need to have an order for test cases (class level) to make sure that > certain scenarios will be executed in an order. For example, policy level > tests should be executed before application level tests. > > It will significantly reduce the time taken for the integration tests. > wdyt? > > Thanks, > Raj. > > > -- > Rajkumar Rajaratnam > Committer & PMC Member, Apache Stratos > Software Engineer, WSO2 > > Mobile : +94777568639 > > > Blog : rajkumarr.com > -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware phone: +94773325954 email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
