Skip to content

Coverage#8

Merged
suranig merged 18 commits intomasterfrom
coverage
Jun 8, 2025
Merged

Coverage#8
suranig merged 18 commits intomasterfrom
coverage

Conversation

@suranig
Copy link
Copy Markdown
Owner

@suranig suranig commented Jun 8, 2025

No description provided.

suranig added 14 commits June 7, 2025 00:46
…exports (fetchWithCache, cacheHandler, createCacheHandler) - Verify type exports and backend utilities - Test instrumentation utilities exports - Improves coverage for src/index.ts to 100%
…DefaultBackend function with various configurations - Environment variable handling (REDIS_HOST, REDIS_PORT, etc.) - Global Redis client reuse functionality - Error handling for invalid configuration values - Improves coverage for src/backends/index.ts to 100%
…d interfaces - Verify interface completeness and optional properties - Test all log event types coverage - Ensures TypeScript type exports are properly accessible - Improves overall type safety coverage
… Add tests for all Redis operations (get, set, del, lock, unlock, clear) - Test serialization/deserialization error scenarios - Test prefix handling and configuration edge cases - Test non-Error object handling in Redis operations - Improves coverage for src/backends/redis.ts to 100%
…- Add extensive error handling tests for backend operations - Test stale cache error scenarios (set/get failures) - Test polling during lock wait with error conditions - Test various prefix/version combinations and edge cases - Improves coverage for src/cache/createCacheHandler.ts
…ests for default handler path vs custom backend path - Test temporary handler creation with custom backend - Add error scenarios and edge cases - Improves coverage for src/cache/fetchWithCache.ts to 100%
…tests for items without options, with only TTL, with only staleTtl - Test invalid input handling (null, undefined, empty arrays) - Enhanced clearCache error scenarios - Improves coverage for src/instrumentation/index.ts to 100%
…atterns for coverage - Exclude test files, examples, node_modules, coverage reports - Include only src/**/*.ts files for accurate coverage reporting
…rom 'npx c8 vitest run' to 'npx vitest run --coverage' - Ensures proper coverage configuration from vitest.config.ts is used - Fixes coverage reporting accuracy
…r' branch (main repository branch) - Add 'coverage' branch to push triggers - Maintain compatibility with 'main' and 'feature/*' branches - Fixes Codecov integration by ensuring CI runs on correct branches
…4 to 3.2.2 for better coverage reporting - Includes related package-lock.json updates
… 'master' branch in Codecov badge URL - Ensures badge shows correct coverage status for the actual main branch
@suranig suranig self-assigned this Jun 8, 2025
…er type assertions - Fix unused parameter warnings - Remove unused type imports - Ensure all tests pass linting requirements
cursor[bot]

This comment was marked as outdated.

suranig added 3 commits June 9, 2025 01:50
…t timeouts in fetchWithCache.test.ts to prevent CI failures - fix package.json coverage script to use vitest instead of c8 - add explicit testTimeout configuration to vitest.config.ts
@suranig suranig merged commit 65dc26b into master Jun 8, 2025
2 of 3 checks passed
Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: CI Trigger Mismatch Causes Integration Failures

The CI workflow was updated to trigger on the master branch instead of main. If main is the repository's default branch, this will prevent CI from running on pushes/PRs, breaking continuous integration for the primary development branch. The README's Codecov badge URL was similarly updated.

.github/workflows/ci.yml#L4-L7

push:
branches: [master, feature/*]
pull_request:
branches: [master, feature/*]

Fix in Cursor


Was this report helpful? Give feedback by reacting with 👍 or 👎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant