Feat/browser environment testing #293
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Fix all failing test suites (632 tests now passing) - Add 21 new comprehensive test suites covering: * Asset management, cache & persistence * Complex queries, deep references, field projections * Global fields, JSON RTE, live preview * Metadata, modular blocks, multi-reference * Pagination, performance benchmarks * Query encoding, operators, sync operations * Taxonomy queries - Fix TypeScript errors (TS18048, TS2304, TS2554, TS1128, TS1005) - Fix Axios errors (422, 400) with graceful error handling - Fix circular references in deep reference chains (WeakSet tracking) - Fix flaky performance tests (network variance handling) - Add global console.error suppression for SDK validation (jest.setup.ts) - Remove redundant synchronization.spec.ts (superseded by comprehensive version) - Update .gitignore to exclude build artifacts - Sync with latest development (19 commits) - Remove @nrwl/jest dependency (from upstream) Test Results: Test Suites: 39 passed, 39 total (100%) Tests: 632 passed, 632 total (100%) Status: Production Ready Breaking Changes: None Security: All credentials use environment variables
- Add browser environment test suite (jsdom) * Import validation tests * Initialization tests with real .env credentials * Dependency safety checks (catches fs/path/crypto usage) * Real API call tests using existing .env - Add bundle validation scripts * validate-browser-safe.js: Scans bundles for Node.js-only APIs * test-bundlers.js: Validates bundler compatibility - Add test configurations * jest.config.browser.ts: Browser environment Jest config * jest.setup.browser.ts: Browser test setup * playwright.config.ts: Real browser testing (structure) - Update package.json with new npm scripts * test:browser: Run browser environment tests * test:all: Run all tests (unit + api + browser) * validate:browser: Validate bundle safety * validate:bundlers: Test bundler compatibility - Update .gitignore * Add .env to prevent credential leaks * Adjust docs/ pattern This implements AWS SDK v3-style multi-environment testing to catch Node.js-only API usage (fs, path, crypto) before production, preventing customer build failures in browser environments.
- Add browser environment testing with Playwright - Add bundler compatibility tests (Webpack, Vite, Next.js, Rollup, esbuild) - Add unified test reporting for CI/CD integration - Update test configurations and dependencies - Add documentation for new testing approach
- Sync with development branch (error-messages.ts, security fixes) - Add Jest globals imports to all test/api files - Fix error handling patterns (error.status vs error.response.status) - Fix test data alignment (entry/content type matching) - Remove invalid asset query test - Fix npm audit vulnerabilities (0 remaining)
…porting - Added console log capture in Jest reports with JSON output. - Improved global fields tests to reflect changes in field names and added nested global field schema tests. - Enhanced HTML report generation to include console logs and improved styling for better readability.
Coverage report
Test suite run success657 tests passing in 34 suites. Report generated by 🧪jest coverage report action from 2581b47 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated comprehensive test cases with latest development code