DeeplyDiligent / logic-app-testing-approaches

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

From a requirements perspective, Microsoft aims to empower developers with the ability to execute "Unit Tests" seamlessly on their local machines and within DevOps Pipelines for Logic Apps. This article explores the necessary steps to achieve this goal, primarily focusing on the crucial aspects of mocking dependencies such as Triggers, ServiceBus, External Connections, and APIs. Additionally, the article considers the potential benefits of automating the execution of logic app workflows in UAT/TESTING environments, acknowledging the value of integration testing in the development process.

Reviewing the options below:

OPTION Name / Links Owner / Creator Pros / Cons
(1) Logic App Sample Test Framework
Code: GitHub
Microsoft Pros:
- Microsoft owned
Cons:
- Limited support for triggers other than HTTP
- Is it being maintained, not much activity?
- Tests require logic app to be deployed
- No mocking
(2) Microsoft – Testing workflows with mock data in Azure Logic Apps (Preview) Microsoft Pros:
- Good start
Cons:
- Limited activity support (http only so far)
(3) Michael Stephensen (integration-playbook.io)
Code: GitHub
Michael Stephensen Pros:
- Good approach for targeting Integration Testing requiring workflows to be deployed
Cons:
- Not Microsoft
- No Mocking, therefore no "Unit Testing"
- Targets Integration testing only
(4) LogicApp Unit Testing
Code: GitHub
Mark Abrams Pros:
- Seems to align with what we are trying to achieve: Unit Testing, Mocking, Pipelines
- Recent git activity
Cons:
- Not Microsoft

Other Resources:

About