Skip to content

test: add missing coverage for CellRenderMask.numCells() and equals() - #59460

Open
saiyam-jain-dev wants to merge 1 commit into
react:mainfrom
saiyam-jain-dev:test/cell-render-mask-missing-coverage
Open

saiyam-jain-dev wants to merge 1 commit into
react:mainfrom
saiyam-jain-dev:test/cell-render-mask-missing-coverage

Conversation

@saiyam-jain-dev

@saiyam-jain-dev saiyam-jain-dev commented Oct 24, 2026 •

Copy link
Copy Markdown

Summary

\CellRenderMask\ exposes two public methods —
umCells()\ and \equals()\ — that had zero test coverage. This adds 9 new test cases:

numCells() (3 tests)

  • Returns 0 for an empty mask
  • Returns the size passed to the constructor
  • Is unaffected by addCells() mutations

equals() (6 tests)

  • Returns true for two identical fresh masks
  • Returns false when masks have different sizes
  • Returns true after applying identical addCells operations
  • Returns false when regions differ
  • Returns false when one mask has more regions than the other
  • Is reflexive (a mask equals itself)

All new tests follow the exact style of existing tests in the file.

Test Plan

yarn jest packages/virtualized-lists/Lists/tests/CellRenderMask-test.js

Changelog

[INTERNAL] [ADDED] - Add unit tests for CellRenderMask.numCells() and equals() methods which previously had no test coverage

The CellRenderMask class exposes two public methods — numCells() and
equals() — that had no test coverage at all. This commit adds:

- numCells(): 3 tests covering empty mask, constructor size, and
  stability after addCells mutations
- equals(): 6 tests covering identical masks, size mismatch,
  identical operations, differing regions, differing region counts,
  and reflexivity
@meta-cla

meta-cla Bot commented Oct 24, 2026

Copy link
Copy Markdown

Hi @saiyam-jain-dev!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla

meta-cla Bot commented Oct 24, 2026

Copy link
Copy Markdown

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Oct 24, 2026
@meta-cla

meta-cla Bot commented Oct 24, 2026

Copy link
Copy Markdown

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@facebook-github-tools facebook-github-tools Bot added the Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team. label Oct 24, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants