Azure / Azure/bicep

Test framework research effort

Open
#1,343 23 comments 1 reaction 1 assignee Claimed by @MarcusFelling View on GitHub
enhancement story: test-framework
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

What type of testing should we focus on?

### Types of tests:
1. **Static analysis** - test code without deploying it
- compiler
- linter: will be covered by Issue #428
- dry run: can be accomplished via [what-if](https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-deploy-what-if)

2. **Unit tests** - test a single unit of code in isolation
- test single module in isolation from Azure

**Note:** what value is this when infra code is all about talking to Azure?

1. **Integration tests** - deploy real infrastructure and run validations
- test single, deployed, module
- examples: check outputs against expected values. Verify HTTP request returns 200.

4. **End to end tests** - test entire infra works together
- test all modules deployed together

**Note:** Can be slow and flaky, would need to be incremental somehow (dedicated environment). Can get expensive to deploy all resources.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.