Adding Azure.Functions.Cli.TestFramework.csproj to have E2E tests run on
#4363
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Honesty you can probably just drop |
aishwaryabh
changed the base branch from
aibhandari/func-start-abstractions
to
main
aishwaryabh
changed the title
Func.TestFramework to have E2E tests run onFunc.TestFramework to have E2E tests run on
liliankasem
reviewed
Apr 15, 2025
test/Cli/Func.TestFramework/Assertions/CommandResultAssertions.cs
Outdated
Show resolved
Hide resolved
test/Cli/Func.TestFramework/Assertions/CommandResultAssertions.cs
Outdated
Show resolved
Hide resolved
aishwaryabh
force-pushed
the
aibhandari/func-start-framework
branch
from
ddcbf35 to
79519d1
Compare
liliankasem
reviewed
Apr 18, 2025
test/Cli/Func.TestFramework/Assertions/CommandResultExtensions.cs
Outdated
Show resolved
Hide resolved
aishwaryabh
force-pushed
the
aibhandari/func-start-framework
branch
from
79519d1 to
736bc81
Compare
aishwaryabh
changed the title
Func.TestFramework to have E2E tests run onAzure.Functions.Cli.Test.Framework to have E2E tests run on
liliankasem
approved these changes
Apr 21, 2025
aishwaryabh
force-pushed
the
aibhandari/func-start-framework
branch
from
6046327 to
29792f9
Compare
…zure.Functions.Cli.TestFramework
aishwaryabh
force-pushed
the
aibhandari/func-start-framework
branch
from
29792f9 to
c398ff4
Compare
aishwaryabh
changed the title
Azure.Functions.Cli.Test.Framework to have E2E tests run onAzure.Functions.Cli.TestFramework.csproj to have E2E tests run on
satvu
approved these changes
Apr 21, 2025
soninaren
approved these changes
Apr 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue describing the changes in this PR
resolves #4327
This PR is the second part of a series of PRs to set up a new testing framework for the Azure Functions CLI. This is the larger PR, which contains all the changes for the testing framework and the updated func start E2E test, if you would like to take a look at how it all fits in! I just decided to split it up since it would be easier to review and get feedback this way.
Func.TestFramework.csprojcontains the new test framework that can be used for the E2E tests or even unit tests.FuncCommandis the base class that implementsCommanddefined in the abstractions project. For debugging purposes, I also create a file for eachFuncCommandcreated and dump the logs that are defined into the file. These logs are then published as an artifact in a folder called TestLogs, which can be useful for debugging in the future (the last step of publishing the logs will be in the final PR)!Pull request checklist