Skip to content

Add E2E tests for Usage API.#1066

Draft
rahulsprajapati wants to merge 1 commit into
developfrom
feature/api-usage-e2e
Draft

Add E2E tests for Usage API.#1066
rahulsprajapati wants to merge 1 commit into
developfrom
feature/api-usage-e2e

Conversation

@rahulsprajapati

@rahulsprajapati rahulsprajapati commented Mar 20, 2026

Copy link
Copy Markdown
Contributor

Description of the Change

E2E Tests for PR #1060

TODO Tests:

  • "Usage Tracking" Feature UI exists and verify admin user role is selected by default.
  • Verify "AI Usage Tracking" settings exists within "Usage Tracking" nav menu.
  • Can save "AI Usage Tracking" settings
  • Verify we can see Dashboard Widget in default stats.
  • Run cron job and verify usage data updated from mock data.
  • Verify widget data shows correct data, from mock data.
  • Verify force refresh button works.
  • Enable soft/hard limit and confirm notice.
  • Verify tts feature can't be used when hard limit reached.

TODO Docs:

Closes #

How to test the Change

Changelog Entry

Added - Add E2E test cases for Usage Tracking Feature

Credits

Props @rahulsprajapati , ...

Checklist:

@github-actions github-actions Bot added this to the 3.8.0 milestone Mar 20, 2026
@github-actions

Copy link
Copy Markdown

✅ WordPress Plugin Check Report

✅ Status: Passed

📊 Report

All checks passed! No errors or warnings found.


🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check

@dkotter dkotter modified the milestones: 3.8.0, 3.9.0 Mar 20, 2026
@dkotter

dkotter commented Jun 1, 2026

Copy link
Copy Markdown
Collaborator

@rahulsprajapati Just following up on this. Is there more you were wanting to get to here or is this ready for review?

@rahulsprajapati

Copy link
Copy Markdown
Contributor Author

@rahulsprajapati Just following up on this. Is there more you were wanting to get to here or is this ready for review?

yes, need to add E2E test for all unchecked todo in description. All checked todo test case are working fine, so if you like we can split this PR in two and you can review this PR for E2E test cases. For remaining ones, we can have another issue/PR which anyone can pickup, If I can't get to it.

@jeffpaul jeffpaul moved this to In Progress in Open Source Practice Jun 2, 2026
@github-actions github-actions Bot added the needs:refresh This requires a refreshed PR to resolve. label Jun 5, 2026
@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown

@rahulsprajapati thanks for the PR! Could you please rebase your PR on top of the latest changes in the base branch?

@dkotter dkotter modified the milestones: 3.9.0, 4.0.0 Jun 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs:refresh This requires a refreshed PR to resolve.

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

3 participants