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
When select a business flow stage using "I select the 'xx' stage of the business process flow', it does not actually open the dialogue window on the screen during auto-testing.
Although "I click next stage on the the 'xx' stage of the business process flow" passes the test, it actually did not go to the next stage when manually checking on the record that having the flow afterwards.
When using " I pin the 'xx' stage of the business process flow" after "I select the 'xx' stage of the business process flow" statement, errors out as "error: Pin button for stage xx not found." - this may be due to the No.1 bug with the select stage statement since the dialogue is not opened and not visible for displaying the pin button.
When using assertion statement such as "Then I can see a value of 'false' in the 'xx' boolean field on the business process " errors out as no source found. - this may be due to the same bug No.1 that no dialogue is opened so not visible for displaying the field values.
When using editing fields statements such as "I enter 'true' into the 'xx' boolean field on the business process flow" errors out as no source found. - may be due to the similar reasons as No.4 and No.3.
To reproduce
after logging in the powerapp, on any of the grid record that has a business flow with a stage containing one field value.
open a record in the grid : "I open the record at position '0' in the grid"
select the business flow stage : "And I select the 'xx' stage of the business process flow" (should see the stage is clicked and the stage dialogue should be opened, see pic 2)
"I pin the 'xx' stage of the business process flow" (should open the side window)
use any assertion statement that matches the field value in the flow stage. such as "Then I can see a value of 'false' in the 'xx' boolean field on the business process " (should see the stage dialogue is opened and the field with values are displaying in the dialogue, see pic 2)
use any editing field values statement that matches the field values in the flow stage, such as "I can see a value of 'false' in the 'xx' boolean field on the business process" (should see the stage dialogue is opened and the field with values are displaying in the dialogue, and the values is being edited when the statement is being executed)
Expected behaviour
See "To reproduce" section No.2-5
Screenshots
the auto-tester only display the pic 1 during the statement of "I select the 'xx' stage of the business process flow', and "I click next stage on the the 'xx' stage of the business process flow"
although it should display the opened dialogue window as pic 2, where displaying the pin button and the field with values, that allowing the other statements to be executed. (this screenshot is achieved by manually click on the stage and not successfully achieved by the auto-tester)
Environment (please complete the following information):
Test framework [MSTest]
Browser [chrome]
Version [not sure]
Power Apps environment version: [Server version: 9.2.21123.00176]
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
To reproduce
after logging in the powerapp, on any of the grid record that has a business flow with a stage containing one field value.
Expected behaviour
See "To reproduce" section No.2-5
Screenshots
the auto-tester only display the pic 1 during the statement of "I select the 'xx' stage of the business process flow', and "I click next stage on the the 'xx' stage of the business process flow"
although it should display the opened dialogue window as pic 2, where displaying the pin button and the field with values, that allowing the other statements to be executed. (this screenshot is achieved by manually click on the stage and not successfully achieved by the auto-tester)
Environment (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: