feat: add manual testing infrastructure with example applications#20
Merged
Conversation
Add instruction to run manual tests with example apps before submitting PRs, ensuring integration changes are properly tested
Document available manual testing commands and framework support for testing the data layer integration with example applications
Add examples folder to ESLint ignore patterns as example apps may have their own linting configurations
- Add examples/* to npm workspaces - Create dev/start scripts for framework integration - Add test:manual command for testing specific frameworks - Filter turbo commands to only run on packages by default
Configure manual testing task as persistent with no caching to support continuous development testing with example apps
Add minimal NextJS application for manual testing of data layer integration with framework-specific features
Add dev and start scripts to run example frameworks alongside package development for integrated testing
Update scripts to use @examples/ prefix matching the actual package names in workspace
Update dev/start scripts to run both packages and examples when --with-framework is used, allowing simultaneous development
- Load user configuration from config files - Support configurable port, host, and endpoint - Add validation for port number - Improve startup messages with GraphQL/GraphiQL URLs
Document the addition of example applications and testing scripts as a minor version bump for the core package
Closed
- Add dedicated test-manual.js script to handle framework argument - Fix npm run test:manual command to properly accept framework parameter - Now supports: npm run test:manual nextjs
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Changes
This PR introduces a manual testing infrastructure that allows developers to test the data layer packages with real framework integrations. The setup enables running both the core packages and example applications simultaneously for integrated development and testing.
Key Features
dev-with-framework.jsandstart-with-framework.jsscripts for running packages + examplesnpm run test:manual nextjsto test specific frameworksUsage
Test Plan
npm run dev -- --with-framework=nextjsnpm run devstill works (packages only)Related Issues
Closes #16