stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reka Thirunavukkarasu <r...@wso2.com>
Subject Re: One test scenario doesn't need to be tested in multiple test cases
Date Sun, 22 Nov 2015 16:31:05 GMT
Hi Raj,

+1 to remove the validation check in all other test cases except the
specific test case which tested that particular artifacts, if it has
considerable performance issue.

Every test cases were implemented in an isolated manner. We didn't maintain
any order earlier in order to introduce parallel execution for integration
test which our automation framework already supported.. Better to go
through more on this aspect before creating any order for the test cases.

@Lahiru, as Imesh mentioned, we have included the relevant samples for
every integration test based on what that particular test is intended to
do. All the test cases have their own written samples. We have also
implemented the samples and test cases as you have told by writing the
simple test cases and improved it as advance. But i agree that by going
through, we can improve the time taken to complete the integration test.

Thanks,
Reka

On Sun, Nov 22, 2015 at 12:02 PM, Imesh Gunaratne <imesh@apache.org> wrote:

>
>
> On Sun, Nov 22, 2015 at 12:03 AM, Lahiru Sandaruwan <lahirus@wso2.com>
> wrote:
>
>> 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.
>>
>> No, now we have proper test cases which use artifacts packaged in unit
> test resources folder.
>
> @Raj: +1 to remove duplicated test scenarios.
>
> Thanks
>
>
>> 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 <rajkumarr@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: lahirus@wso2.com blog: http://lahiruwrites.blogspot.com/
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> Imesh Gunaratne
>
> Senior Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>



-- 
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007

Mime
View raw message