Add blog post: testing-in-2026-a-practical-guide.mdx#150
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
CodeAnt AI is reviewing your PR. |
📝 WalkthroughWalkthroughA new MDX blog post file is added at Blog Post: Testing in 2026
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
content/blog-post-2026-06-28/testing-in-2026-a-practical-guide.mdxParsing error: Invalid left-hand side in prefix operation. (1:2) 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. Comment |
codeant-ai
Bot
added
the
size:M
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@content/blog-post-2026-06-28/testing-in-2026-a-practical-guide.mdx`:
- Around line 1-8: The post file is outside the collection and route
expectations, so it will not be discovered or rendered. Move the MDX post to
match the velite posts pattern used by the collection (the blog/**/*.mdx glob),
and make sure the Next.js slug lookup in app/posts/[slug]/page.tsx points to the
same content shape instead of a hardcoded .md path. Use the existing
velite.config.ts posts collection and the app/posts/[slug]/page.tsx slug
resolution as the symbols to align.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 1e856913-cee5-4cb2-bf4b-b718185b41a9
📒 Files selected for processing (1)
content/blog-post-2026-06-28/testing-in-2026-a-practical-guide.mdx
| --- | ||
| title: 'Testing in 2026: A Practical Guide' | ||
| description: 'A comprehensive guide to testing for modern frontend development in 2026.' | ||
| date: '2026-06-28' | ||
| tags: ['Testing', 'Frontend', '2026'] | ||
| published: true | ||
| image: './images/post-image.png' | ||
| --- |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🔴 Critical | 🏗️ Heavy lift
File path does not match velite collection pattern.
The file is located at content/blog-post-2026-06-28/testing-in-2026-a-practical-guide.mdx, but velite.config.ts defines the posts collection with pattern blog/**/*.mdx. The content/blog-post-2026-06-28/ prefix will not match blog/**, so velite will not discover this file.
Additionally, app/posts/[slug]/page.tsx reads from posts/${slug}.md (hardcoded .md extension), so the Next.js route handler won't find this .mdx file either.
Move the file to content/blog/testing-in-2026-a-practical-guide.mdx (or update the velite pattern and route handler to match the intended structure).
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/blog-post-2026-06-28/testing-in-2026-a-practical-guide.mdx` around
lines 1 - 8, The post file is outside the collection and route expectations, so
it will not be discovered or rendered. Move the MDX post to match the velite
posts pattern used by the collection (the blog/**/*.mdx glob), and make sure the
Next.js slug lookup in app/posts/[slug]/page.tsx points to the same content
shape instead of a hardcoded .md path. Use the existing velite.config.ts posts
collection and the app/posts/[slug]/page.tsx slug resolution as the symbols to
align.
|
CodeAnt AI finished reviewing your PR. |
1 participant
User description
Blog post about Testing for Frontend Junction
CodeAnt-AI Description
Publish a new guide on testing for modern frontend development in 2026
What Changed
Impact
✅ New testing guidance for readers✅ Clearer onboarding to modern frontend testing✅ More published content for the blog💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.
Summary by CodeRabbit