patternfly / patternfly/patternfly-react

chore: update component unit tests to meet new standards with RTL

Open
#7,594 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

PF Team Pinned
Dominant language
TypeScript
Stars
862
Forks
392
Avg merge
4d 8h
Merged PRs (30d)
9

Description

Describe the issue. What is the expected and unexpected behavior?
This Epic will track the work of updating the test suites for our components to meet our new RTL testing standards and methodology. Please create issues as you pick up tasking.

NOTE: As part of this effort console statements should be mocked in revamped tests rather than actually printing the console

  • #7605

  • #7665

  • #7670

  • #9524

  • #7835

  • #7812

  • #7813

  • #8189

  • #9525

  • #7994

  • #8094

  • #9526

  • #7860

  • #9527

  • #9528

  • #9529

  • #9530

  • #9531

  • #9532

  • #9533

  • #9534

  • #9634

  • #9685

  • #9673

  • #9684

  • #9686

  • #7964

  • #9688

  • #9689

  • File upload

  • File upload - multiple

  • Form

  • Form control

  • Form select

  • #9760

  • #7616

  • Inline edit

  • Input group

  • Jump links

  • Label

  • Label group

  • #8400

  • Login page

  • Masthead

  • Menu

  • Menu toggle

  • Modal

  • Navigation

  • Notification Badge

  • Number input

  • Overflow menu

  • Page

  • Pagination

  • #8247

  • Popover

  • Progress

  • #8345

  • Radio

  • Search input

  • #8302

  • Simple list

  • Skeleton

  • Skip to content

  • Slider

  • Spinner

  • Switch

  • Tab content

  • #8173

  • Text

  • #7976

  • Text input

  • #7169

  • Tile

  • Time picker

  • #8007

  • Toggle group

  • #7687

  • #9768

  • #7643

The following components are expected to change significantly in the near future. Updates to their tests should be delayed until those changes are completed.

  • About modal

  • Card

  • Composable table

  • Drawer

  • Dual list selector

  • Notification drawer

  • Toolbar

  • Wizard


Jira Issue: PF-179

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.

Research direction

Start with the linked React Testing Library standards and the unchecked component entries in this epic. Create or select a focused component task, then inspect that component's existing test suite. Done means its tests follow the stated RTL methodology and mock console statements instead of printing them.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend, testing
Issue type
Refactor
Difficulty
4/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.