Azure / Azure/azure-functions-core-tools
Design how to re-enable core tools E2E tests that provision azure resources
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 498
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 14
Description
Today the[ E2E deployment tests ](https://github.com/Azure/azure-functions-core-tools/blob/main/test/Azure.Functions.Cli.Tests/E2E/DeploymentTests.cs)and [list-functions tests](https://github.com/Azure/azure-functions-core-tools/blob/main/test/Azure.Functions.Cli.Tests/E2E/ListFunctionsTests.cs#L19) are disabled since they require provisioning azure resources. We need to investigate and re-design how the tests are run and re-enable them to use the new E2E test framework
Contributor guide
Research direction
Start by reading test/Azure.Functions.Cli.Tests/E2E/DeploymentTests.cs and test/Azure.Functions.Cli.Tests/E2E/ListFunctionsTests.cs, including the referenced list-functions test location. Investigate how these tests are currently disabled and how the new E2E test framework handles Azure resource provisioning. Done means agreeing on a provisioning and execution design and re-enabling both test suites under that framework.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- cli, cloud, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100