You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been using the govim tests for regression testing, which creates unnecessary load on @myitcv in filing and reproducing issues. It also places too much reliance on one specific editor client. We should develop our own regression tests that use a fake client.
Activity
gopherbot commentedon Feb 4, 2020
Change https://golang.org/cl/217598 mentions this issue:
internal/lsp/fake: add fakes for testing editor interaction
gopherbot commentedon Feb 6, 2020
Change https://golang.org/cl/218278 mentions this issue:
internal/lsp/lsprpc: add test for empty diagnostics in deleted files
gopherbot commentedon Feb 6, 2020
Change https://golang.org/cl/218322 mentions this issue:
internal/lsp/lsprpc: add test for definition outside of workspace
gopherbot commentedon Feb 9, 2020
Change https://golang.org/cl/218698 mentions this issue:
internal/lsp/lsprpc: add an LSP forwarder and regtest environment
internal/lsp/fake: add fakes for testing editor interaction
internal/lsp/lsprpc: add test for empty diagnostics in deleted files
internal/lsp/lsprpc: add test for definition outside of workspace
gopherbot commentedon Feb 10, 2020
Change https://golang.org/cl/218777 mentions this issue:
internal/jsonrpc2/servertest: support both TCP and pipe connection
27 remaining items