Skip to content

🗃️ Readd testdata#300

Merged
Friedinger merged 1 commit into
mainfrom
chore/testdata
Jul 11, 2026
Merged

🗃️ Readd testdata#300
Friedinger merged 1 commit into
mainfrom
chore/testdata

Conversation

@Friedinger

@Friedinger Friedinger commented Jul 10, 2026

Copy link
Copy Markdown
Member

This pull request adds a comprehensive set of test data for products and scan history to the database migration scripts. The data includes 50 diverse ScannedProduct entries with detailed attributes and corresponding scan history entries for a test user. This will help ensure robust testing and development of product-related features.

Test Data Additions:

  • Added 50 new ScannedProduct entries to the product table, each with realistic names, images, descriptions, scores (overall, environment, social, health), justifications, and timestamps to cover a wide range of scenarios for testing.
  • Inserted 50 corresponding entries into the scan_history table, linking the test user to each product with appropriate timestamps, simulating real user scan activity.

Reverts removal in 7f71e93

@coderabbitai

coderabbitai Bot commented Jul 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Friedinger, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c65ac380-c83f-4858-8d1e-564389a54c6c

📥 Commits

Reviewing files that changed from the base of the PR and between 80656a7 and 3649ae2.

📒 Files selected for processing (1)
  • ecoscan_backend/src/main/resources/db/migration/testdata/R__Products.sql
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/testdata

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added the 🛠️ Maintenance General maintenance and updates label Jul 10, 2026
@Friedinger Friedinger merged commit 84e7c2a into main Jul 11, 2026
10 checks passed
@Friedinger Friedinger deleted the chore/testdata branch July 11, 2026 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🛠️ Maintenance General maintenance and updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants