Thanks very much for your thoughts.
I will do the needful.
Thanks,
Raj.
On Sun, Nov 22, 2015 at 10:01 PM, Reka Thirunavukkarasu
wrote:
> 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
> con
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 par
On Sun, Nov 22, 2015 at 12:03 AM, Lahiru Sandaruwan
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
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 us
+1.We don't need to test the same test case again and again.IMO we can
remove duplicate test cases.
Also we can introduce separate test groups for test cases based on their
test use case.This will provide you the option to run specific test group
based on your modification.
Thanks,
Gayan
On Sat,
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 test
