Create a manual test plan for releases

Open
#1,419 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation, release, testing

Research direction

Read the existing contributing guide and release steps to find where the manual test plan belongs. Add a markdown plan with simple release checks, then update the release steps to reference it; the work is done when a release manager can follow the plan before releasing.

Written by the indexing model from the issue text.

Description

documentation VSCode

This issue is about creating a simple and easy to follow manual test plan that any release manager will perform before the release.

  • come up with the plan
  • add it as a markdown file in this repo (either directly in the contributing guide, or as a separate file)
  • update the release steps to include the manual test plan

It might be overkill, but we can write tests semi-formally in a Gherin style.

My initial thoughts are that we just create a simple set of steps that are easy to follow, but are expressed informally. We can formalize later if we have any need.

Dominant language
TypeScript
Stars
539
Forks
240
Avg merge
2d 6h
Merged PRs (30d)
29

Contributor guide

Open the contributing guide

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 github/vscode-codeql

All issues in github/vscode-codeql

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.