microsoft / microsoft/VFSForGit
Rework FastFetch tests to run against Published binary, not BuildOutput .dll
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
On MacOS, we run the FunctionalTests out of the Publish folder, so we can easily find the published FastFetch executable. On Windows, we're currently running the FunctionalTests out of the BuildOutput folder. Instead of reworking how we run tests on Windows at this time, I went for the cheap fix of running FastFetch via dotnet. Whenever we move the rest of the project to .NET Core (or extract FastFetch into its own codebase), this can be cleaned up.
In general we've tried to run the functional tests as black-box tests against the final binaries.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the FunctionalTests entry points and the Windows and macOS commands that launch FastFetch from BuildOutput or Publish. Update the test setup to run against the published FastFetch binary, preserving the intended black-box behavior, then verify the functional tests on Windows and macOS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100