Now that we’ve constructed a ‘RSAT connector for Microsoft Flow’ in Part I of this Series, we have lots of new opportunities offered by the Microsoft Power Platform to push our Test Automation in D365 to a new level.
In below video I’ll demonstrate how toggling the State of an Azure DevOps Test Suite to “Run RSAT” triggers MS Flow to iterate through the Test Cases in the Test Suite and let RSAT execute the Test Cases (D365 Task Guides) in the background. MS Flow will wait until RSAT execution is finished to send an e-mail to notify that RSAT execution is done. The e-mail will have the logs from the RSAT execution as attachments.
See my OneDrive for the Flow which is used in the video.
Note: I didn’t manage to import this Flow package into another tenant than the tenant where the Flow was originally built – MS Flow complaints about a problem with the authorisation against Azure DevOps – So you may have to amend the packaged (zipped) json definition of the Flow to allow import. Please share an updated .zip file if you manage to make amendments to the packaged .json definition which allows import.
november 19, 2019 @ 12:25
Looks great. But I have a problem in getting the Zipped Flow guide from your repository. What do I do ?
februari 4, 2020 @ 22:14
Hi Thomas,
Apologies for the late response.
I re-exported the package and moved it to my OneDrive: https://patrickmouwen-my.sharepoint.com/:f:/p/contact/Es5ssvKymQxMjQ_4vmt8c0oB2tJkK4t6qnaW79rMtfkt2g?e=D6uwy1
Patrick
mei 18, 2020 @ 03:37
Greetings! Very helpful advice within this article! It’s the little changes that produce the biggest
changes. Thanks a lot for sharing!
oktober 9, 2020 @ 03:33
Hi Patrick,
When i tried to execute more than 1 cases in the test suite. I am facing below issues.
1. If the test case count is more than 10 in the test case parsing step i am getting below error.
{
“message”: “Invalid type. Expected Object but got Null.”,
“lineNumber”: 0,
“linePosition”: 0,
“path”: “value[10].pointAssignments[0].tester”,
“schemaId”: “#/properties/value/items/properties/pointAssignments/items/properties/tester”,
“errorType”: “type”,
“childErrors”: []
}
]
2. If i reduce the count to 9 this step is getting executed. Test case IDs are extracted and sent to VM machine. Cases are not getting executed and seeing this message in logs
125586 125585 124964 124951 124948 124946 124944 124942 124936 must to be Unsigned long type
Kindly assist in resolving the issue.
Thanks,
Siva.S
oktober 10, 2020 @ 19:21
Hi Siva,
Construct the Flow to iterate through the Test Suite and execute each test case individually (so in a sperate file).
Patrick