Automated testing

Open
#79 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php, wordpress
Domain
testing

Research direction

The issue names no files or existing tests. Start by locating the package-to-JSON handling and the Composer package-installation flow, then identify the current test setup; done means functional and platform tests cover the two stated regression scenarios.

Written by the indexing model from the issue text.

Description

enhancement

We ought to create some tests to help prevent regressions. Some functional tests such as "this package DB record should result in this package JSON file" and some platform tests such as "running this composer file should result in these packages installed".

Dominant language
PHP
Stars
768
Forks
69
Avg merge
3h 52m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

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 wpengine/wpackagist

All issues in wpengine/wpackagist

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.