-
-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Condition blocking the manual execution #2161
Comments
I'm launching my test case on type APK Application and it's trigger with condition 'IfElementVisible' but it's not with all conditions (e.g. working correctly with IfPropertyExists') which makes me believe it's only happening with condition related to webdriver |
…tor information for manual execution (step / action / control) Still need to define which condition need to be evaluated by an operator and implement the rest of the messageEvent for CONDITIONEVAL_TRUEMANUAL...
…to be evaluated + 3 new conditions are available for manual execution
@Nouxx I have finished implementing this feature, you can test it on QA env. Since you told me you would do the TNR yesterday, I'll let you do that.
An information message with the condition that needs to be evaluated is added to the step/action/control description |
Feature covered by test case: ENGINE : Action / 0031A |
Hello,
I'm trying to launch a test case that contains a step with a condition (verifyElementVisible) manually but I'm getting this error :
It doesn't make sense to me.
Can make this behave like there is no condition as a first step?
As a second step, I'd be great to handle the condition in a better way. We already brought this topic: #1861
Cerberus4.7-1491
The text was updated successfully, but these errors were encountered: