Create test.spec.js

[wpscholar]

Proposed changes

copilot:summary

Type of Change

• [] Bugfix (non-breaking change which fixes an issue)
• [] New feature (non-breaking change which adds functionality)
• [] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [] Documentation Update (if none of the other choices apply)

Checklist

• [] Linting and tests pass locally with my changes
• [] I have added tests that prove my fix is effective or that my feature works
• [] I have added necessary documentation (if appropriate)

Further comments

[wpscholar]

copilot:summary

[wpscholar]

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

[wpscholar]

@copilot Add 5 intentional bugs to this PR

[Copilot]

@wpscholar I've opened a new pull request, #25, to work on those changes. Once the pull request is ready, I'll request review from you.

[wpscholar]

Summary:

• Test structure looks good; suggested using Cypress each for more predictable command sequencing.
• Performance marks/measures can accumulate across visits; consider clearing or using unique marks to avoid stale entries.

[wpscholar]

Consider using cy.wrap(entries).each(...) instead of forEach. Cypress recommends each for command sequencing; forEach can make command ordering and failures harder to reason about when iterating.

[wpscholar]

Since this runs multiple cy.visit calls, the performance entries will accumulate. Either clear marks/measures before each visit (performance.clearMarks()/clearMeasures()), use unique mark names per URL, or grab the last entry from getEntriesByName instead of [0] to avoid stale measurements.