Skip to content
This repository was archived by the owner on Oct 16, 2020. It is now read-only.
This repository was archived by the owner on Oct 16, 2020. It is now read-only.

Unit tests #105

@felixfbecker

Description

@felixfbecker

Currently all we have is a test suite for the TypeScriptService, testing the top-level interaction between a language client and the language server. This makes it really hard to make changes and fix bugs, because a test failure does not give any information about what component broke by the change. All you get is something like Expected a definition location, got nothing. You are going down a rabbit hole stepping through the code trying to find out where the bug is.

In addition, our code coverage is at a worrying codecov

What I would like to add are tests for most classes, for most methods so it's easy to identify the broke component. Dependencies can be mocked easier than in any other language with sinon.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions