Azure / Azure/azure-functions-core-tools
Evaluate tests to remove from `feature/inproc` branch
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 498
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 14
Description
### Description
Capturing some flaky tests (in CI) for `feature/inproc`. These were temporarily skipped today in the` feature/in-proc` branch. We need to evaluate these tests (and other non in-proc tests) are needed in this branch. These use cases are exercised by the oop coretools and we should be running these tests in that branch.
1. Azure.Functions.Cli.Tests.E2E.StartTests.only_run_some_functions
2. Azure.Functions.Cli.Tests.E2E.InitTests.init_with_dotnet7Isolated_dockerfile
3. Azure.Functions.Cli.Tests.E2E.StartTests.start_nodejs
4. Azure.Functions.Cli.Tests.E2E.StartTests.start_loglevel_None_overrriden_in_host_json
Contributor guide
Research direction
Start by locating the four named tests in the Azure.Functions.Cli.Tests.E2E suite and reviewing their temporary skips on the feature/inproc branch. Compare these cases with the in-proc and out-of-process coretools coverage described in the issue. Done means determining which tests are needed for this branch and removing or retaining them accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100