This script was created for flows with SharePoint Online triggers.
The flow under test in this example represents an approval process. In this case the flow triggers when an item is created or modified in the sharepoint list 'demolist'.
Depending on the stored metadata of the list column "requestlevel" the flow runs through different actions. This distinction is implemented by a switch statement. The flow is build like this:
When the flow finished the enduser get a notification to take action. At this point the user has to edit the sharepoint metadata which we do with a button on the sharepoint form. So in this case we know which metadata are modified by the user.
function createTestData{
<#
* ADD YOUR TESTMETADATA
* Customize this part to your system / testdata
* trigger elements of flow runs that are not included to your testdata are not monitored
* alternativ: just return the itemId's of manual created testdata
#>
$i = 0
$testMetadata = @()
do{
$testMetadata += m365 spo listitem add --contentType 'Item' --listTitle $spListTitle --webUrl $spSiteUrl --Title "Test-Item $i" --RequestLevel "Started"
$i++
}until($i -eq 10)
return $testMetadata.id
}# ----------------------------- in my case i need to get the current request level
# based on spColoumn : requestlevel
$currentRequestLevel = $flowRunInformation.triggerInformation.requestlevel.Value
# Here you need to put your different update actions which simulated your user input to the sharepoint item
switch($currentRequestLevel){
'Started'{
m365 spo listitem set --listTitle $spListTitle --id $itemId --webUrl $spSiteUrl --Genehmigungslevel 'Editing'
}
'Editing'{
m365 spo listitem set --listTitle $spListTitle --id $itemId --webUrl $spSiteUrl --Genehmigungslevel 'Approval'
}
'Approval'{
m365 spo listitem set --listTitle $spListTitle --id $itemId --webUrl $spSiteUrl --Genehmigungslevel 'Release'
}
'Release'{
# this is the last step -> so there is nothing to do
}
}Start the script in your editor (VS Studio or PowerShell ISE) or run it from your commandline
.\automate_flowtest.ps1 -environment '<Your Environment ID>' -flow '<FlowID or DisplayName>' -spSiteUrl '<URL of our SharePoint Site' -spListTitle '<DisplayName of your list>'The monitoring of the flow runs are stored in an endless loop. If you finished your test wait a few minutes (get yourself a new coffee) and just end the script run. Execute the following code to "review" your test:
# run this for feedback, when you are finished
Write-Output ("Total flowruns : {0}`n "-f $flowRunsCount)
Write-Output ("succeded flowruns : {0} `n"-f $successFlowRunsCount)
Write-Output ("canceled flowruns : {0} `n"-f $CancelledFlowRunsCount)
Write-Output ("failed flowruns : {0} `n"-f $failedFlowRunssCount)
Since the Version 6.7 CLI for Microsoft 365 the command "m365 flow run get" return all the triggerInformation while using the parameter "-includetriggerInformation". With this command you can directly relate between flowrun and trigger item like a modified sharepoint list item.
npm i -g @pnp/cli-microsoft365More about CLI for Microsoft 365
| Author |
|---|
| Joshua Probst |
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent