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
[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request
Current behavior
When I test run a flow with a branch having false condition, it marks the tiles under the branch as run though it did not run them in actual case.
Expected behavior
The test flow run should not mark the activities under the branch with false condition as run.
Minimal reproduction of the problem with instructions
Open a flow which has a branch with "false" condition in it as shown in the above screenshot.
Select any tile (Activity or Trigger) and click on "Run from Trigger" button from the right hand side details panel.
Notice that even the branch condition is set to false, the activities under the branch marked as run state.
Flogo version: 0.3.4
The text was updated successfully, but these errors were encountered:
apandura-tibco
changed the title
Flow test run executing the branch which is under false condition
Flow test run marks the activities under a branch whose condition is set to false
Jun 5, 2017
The steps API call is responding with the taskState for each step which defines which steps are skipped. Closing the issue as the problem is solved now.
Also checked that the string comparison check issue (issue 1) in flogo/issues/#54 is also fixed in flogo-web / engine
I'm submitting a ... (check one with "x")
Current behavior
![image](https://cloud.githubusercontent.com/assets/23206463/26770541/6cc2e1aa-49d5-11e7-91a2-ac9c56effd7f.png)
When I test run a flow with a branch having false condition, it marks the tiles under the branch as run though it did not run them in actual case.
Expected behavior
The test flow run should not mark the activities under the branch with false condition as run.
Minimal reproduction of the problem with instructions
The text was updated successfully, but these errors were encountered: