Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Running dotnet test test/FsAutoComplete.Tests.Lsp/FsAutoComplete.Tests.Lsp.fsproj directly on a clean repository fails in gotoTest

Open Beginner friendly
  • Is something wrong?
#1,559 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@rubin55 is already working on this.

Since Oct 12, 2026.

  • #1562 by @rubin55 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp, fsharp
Domain
testing

Research direction

Start with gotoTest and signatureGotoTests in the LSP test project, then inspect how DotnetCli.build is used for TestCases/GoToCSharp/GoToCSharp.csproj. Run dotnet test test/FsAutoComplete.Tests.Lsp/FsAutoComplete.Tests.Lsp.fsproj from a clean checkout. Done means the GoToCSharp assembly exists before gotoTest initializes its workspace and the direct test command succeeds.

Written by the indexing model from the issue text.

Description

bug
Version

v0.85.0

Dotnet Info

.NET SDK:
Version: 10.0.112
Commit: 95017c711e
Workload version: 10.0.100-manifests.63b36e85
MSBuild version: 18.0.11

Runtime Environment:
OS Name: arch
OS Version:
OS Platform: Linux
RID: arch-x64
Base Path: /usr/share/dotnet/sdk/10.0.112/

.NET workloads installed:
There are no installed workloads to display.
Configured to use workload sets when installing new manifests.
No workload sets are installed. Run "dotnet workload restore" to install a workload set.

Host:
Version: 10.0.12
Architecture: x64
Commit: 95017c711e

.NET SDKs installed:
10.0.112 [/usr/share/dotnet/sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 10.0.12 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 10.0.12 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
None

Environment variables:
DOTNET_CLI_TELEMETRY_OPTOUT [1]

global.json file:
Not found

Steps to reproduce

  1. Clear build artifacts in test/FsAutoComplete.Tests.Lsp/TestCases/GoToCSharp/bin/

  2. Run dotnet test test/FsAutoComplete.Tests.Lsp/FsAutoComplete.Tests.Lsp.fsproj

Details

The sample workspace TestCases/GoToTests references TestCases/GoToCSharp/GoToCSharp.csproj, and External.fs uses GoToCSharp.Class1. Currently, signatureGotoTests compiles GoToCSharp.csproj via DotnetCli.build. Because gotoTest runs before signatureGotoTests, the output assembly does not exist when gotoTest initializes its workspace.

I think you need to invoke DotnetCli.build for GoToCSharp before gotoTest initializes the server, or add an MSBuild build target to FsAutoComplete.Tests.Lsp.fsproj that builds GoToCSharp.csproj before running tests.

Logs

No response

Checklist
  • I have looked through existing issues to make sure that this bug has not been reported before
  • I have provided a descriptive title for this issue
  • I have made sure that that this bug is reproducible on the latest version of the package
  • I have provided all the information needed to reproduce this bug as efficiently as possible
  • I or my company would be willing to contribute this fix
Dominant language
F#
Stars
488
Forks
172
Avg merge
2d 19h
Merged PRs (30d)
7

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ionide/FsAutoComplete

All issues in ionide/FsAutoComplete

Similar issues

More Testing & QA issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.