Standards: Automation Manifesto

Open
#31 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Domain
documentation, testing-qa

Research direction

Start by finding the Automation Manifesto in Slack, then review the existing contributor documentation for guidance on e2e tests. Determine where the manifesto's guidelines belong and incorporate the relevant guidance there. Done means the QA-authored standards are documented in an appropriate contributor-facing location.

Written by the indexing model from the issue text.

Description

team-wallet-framework wf-documentation

The QA engineers have created an Automation Manifesto which lists guidelines for writing e2e tests. Search Slack for it. We should bake this in.

Dominant language
JavaScript
Stars
86
Forks
42
No merged PRs in 30d

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 MetaMask/contributor-docs

All issues in MetaMask/contributor-docs

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.