sveltejs/language-tools

Add performance tests

Open

#676 opened on Nov 17, 2020

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)TypeScript (247 forks)auto 404
good first issue

Repository metrics

Stars
 (1,437 stars)
PR merge metrics
 (PR metrics pending)

Description

It would be good to have some kind of performance tests to get a better understanding of how well the extension performs, and to keep track of it to not overlook accidental performance decreases when adding new things.

The performance tests as a start could consist of:

  • One autocompletion inside script (means svelte2tsx and the TS service are tested)
  • One diagnostic run on a file that needs no preprocessing
  • One diagnostic run on a file with TypeScript that needs script preprocessing

Contributor guide

Research direction
Identify key performance metrics, set up a benchmarking tool (e.g., Jest with performance reporters), and write tests for autocompletion and diagnostics as described.
Tech stack
typescript
Domain
testing qaperformance
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TypeScriptSvelte
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70