You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 20, 2024. It is now read-only.
Introduce "OR" function in Tagging test cases while execution as compared to
"AND" and "NOT".
In Current implementation while tagging the test cases we have only "AND" and
"NOT" options available to include or exclude. But we need "OR" Function as
well.
Analogy:
Suppose, I have bunch of test cases with Tags have "Tag1, Tag2, Tag3....Tag10".
Now my requirement is whichever test cases having "Tag1, Tag3, Tag5, Tag7",
should be excluded from the execution.
With current implementation I can execute above requirement as
"Pybot -i Tag* -e Tage1ANDTag3ANDTag5ANDTag7 Exmple.txt".
In this case test cases which have all "Tag1, Tag3, Tag5, Tag7" will exclude
from test, since "AND" combination.
In real time all the test cases may not contain all tags, i.e., Testcase 1
contains Tag1, and TestCase 2 contains Tag3. So in this case above command will
not exclude these tests, even though I asked to exclude. since above "exclude
Options" will not match (AND).
So in order solve this problem we should have "OR" functions.
SO now if command has "Pybot -i Tag* -e Tage1ORTag3ORTag5ORTag7 Exmple.txt".
Then above case illustrates in whole test cases which is having any of these
tags will be excluded.
However with existing implementation I can exclude test cases with "Tag1, Tag3,
Tag5, Tag7" tags in include options itself using "NOT" operator. Like.
"Pybot -i Tag*NOTTage1NOTTag3NOTTag5NOTTag7 Exmple.txt".
But its not worth solution, even we have exclude option. According to me as
long has "OR" functions not available "Exclude" option is not user friendly.
Original issue reported on code.google.com by bm.gurus...@gmail.com on 28 Oct 2013 at 10:07
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
bm.gurus...@gmail.com
on 28 Oct 2013 at 10:07The text was updated successfully, but these errors were encountered: