browserify / browserify/wzrd.in
Integration tests for CORS headers on both expected and 404 routes
Open
- Dominant language
- JavaScript
- Stars
- 637
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
One of the big failure modes for wzrdin deploys in the past have been around accidentally breaking cors headers.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name files, existing tests, or an entry point. Start by locating the integration-test setup and the routes that serve expected and 404 responses; done means tests verify CORS headers on both route types without relying on a deploy-specific failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100