WordPress / WordPress/secure-custom-fields

Baseline E2E suite to cover primary flows

Open
#100 2 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Type] Code Quality good first issue help wanted
Dominant language
PHP
Stars
131
Forks
64
Avg merge
10m
Merged PRs (30d)
1

Description

Why

The plugin needs a complete set of E2E tests, so contributors can keep implementing features, fixing bugs, and updating the code with the latest standards without the fear of breaking thousands of sites.

Therefore, it needs a list of the main features to be tested.

User stories to test

  • A user can create, fill, and render a custom post type. #98

  • A user can create, fill, and render a Field Group. #103

  • A user can create, fill, and render a Text Field inside a Field Group. #103

  • A user can create, fill, and render a Email Field inside a Field Group.

  • A user can create, fill, and render a Number Field inside a Field Group.

  • A user can create, fill, and render a Password Field inside a Field Group.

  • A user can create, fill, and render a Range Field inside a Field Group.

  • A user can create, fill, and render a Text Area Field inside a Field Group.

  • A user can create, fill, and render a URL Field inside a Field Group.

  • A user can create, fill, and render a Checkbox Field inside a Field Group.

  • A user can create, fill, and render a Radio button Field inside a Field Group.

  • A user can create, fill, and render a Select Field inside a Field Group.

  • A user can create, fill, and render a True/False Field inside a Field Group.

  • A user can create, fill, and render a File inside a Field Group.

  • A user can create, fill, and render a Gallery Field inside a Field Group.

  • A user can create, fill, and render an Image Field inside a Field Group.

  • A user can create, fill, and render an oEmbed Field inside a Field Group.

  • A user can create, fill, and render a Color Picker Field inside a Field Group.

  • A user can create, fill, and render a WYSIWYG Field inside a Field Group.

  • A user can create, fill, and render a Date Field inside a Field Group.

  • A user can create, fill, and render a Date Time Field inside a Field Group.

  • A user can create, fill, and render a Time Field inside a Field Group.

  • A user can create, fill, and render an Accordion Field inside a Field Group.

  • A user can create, fill, and render an Icon Picker Field inside a Field Group.

  • A user can create, fill, and render a Repeater Field inside a Field Group. #134

  • A user can create, fill, and render a Tab Field inside a Field Group.

  • A user can create, fill, and render a Group Field inside a Field Group.

  • A user can create, fill, and render a Flexible Content Field inside a Field Group.

  • A user can create, fill, and render a Post Object Field inside a Field Group.

  • A user can create, fill, and render a Relationship Field inside a Field Group.

  • A user can create, fill, and render a Taxonomy Field inside a Field Group.

  • A user can create, fill, and render a User Field inside a Field Group.

  • A user can create, fill and render a SCF Block.

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.

Research direction

Start by reviewing the completed E2E flows linked in issues #98, #103, and #134, then use the unchecked user stories in this issue as the coverage list. Done means the remaining listed field and SCF Block flows have passing E2E tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.