You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As next-yak continues to grow in complexity and feature set, we need to ensure that the CSS generation and application works correctly across various contexts. (e.g: dev, prod app-router, pages-router and soon turbopack)
E2E tests will allow us to:
Verify compiled CSS is correctly applied to DOM elements
Test cross-file mixins and selectors
Catch regressions that might occur with Next.js version updates
Testing Strategy
The idea would be to:
Start a Next.js dev or production server with test components
Navigate to specific test pages
Verify that elements have the expected computed styles
Test interactive behavior where applicable
Test Cases
Core Functionality
Basic Styling
Test static styles with the styled API
Verify correct CSS class generation and application
Check specificity and inheritance patterns
Dynamic Styles
Test conditional class toggling based on props
Verify correct style application when props change
Test style override behavior
Dynamic Properties
Test CSS variable generation for dynamic props
Verify correct application of custom properties
Test updates to dynamic values
Keyframes Animations
Test keyframe animation definitions
Verify correct animation application
Test animation name generation
Advanced Patterns
Cross-File Mixins
Test importing and using mixins from different files
Verify correct CSS generation and application
Test nested mixins across files
Cross-File Selectors
Test targeting components defined in other files
Verify selector specificity and cascade
Test complex cross-file selector patterns
CSS Prop
Test inline css prop usage
Verify composition with className and style props
Test dynamic values in css props
Tailwind/Atomic CSS Integration
Test atoms API with Tailwind classes
Verify correct class application
Test conditional Tailwind class application
Nested Selectors
Test parent-child relationships in styled components
Verify correct nesting of selectors
Test pseudo-class and pseudo-element behavior
Component Targeting
Test targeting styled components within other components
Verify hover, focus, and other interactive states
Test complex component selector patterns
Edge Cases
Media Queries
Test responsive styles with media queries
Verify correct application at different viewport sizes
Test media query prioritization and cascade
Build-Time Constants
Test .yak.ts constant resolution
Verify correct constant usage in styles
Test complex constant value patterns
Class Minification
Test production builds with minified class names
Compare development and production class patterns
Verify correct style application with minified classes
Theming Support
Test theme context and application
Verify theme value propagation to styled components
Test theme switching behavior
The text was updated successfully, but these errors were encountered:
As next-yak continues to grow in complexity and feature set, we need to ensure that the CSS generation and application works correctly across various contexts. (e.g: dev, prod app-router, pages-router and soon turbopack)
E2E tests will allow us to:
Testing Strategy
The idea would be to:
Test Cases
Core Functionality
Basic Styling
styled
APIDynamic Styles
Dynamic Properties
Keyframes Animations
Advanced Patterns
Cross-File Mixins
Cross-File Selectors
CSS Prop
Tailwind/Atomic CSS Integration
atoms
API with Tailwind classesNested Selectors
Component Targeting
Edge Cases
Media Queries
Build-Time Constants
Class Minification
Theming Support
The text was updated successfully, but these errors were encountered: