-
Notifications
You must be signed in to change notification settings - Fork 0
[WIP] Add unit tests to achieve 100% coverage for text.js #57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
Copilot
wants to merge
352
commits into
master
Choose a base branch
from
copilot/increase-test-coverage-text-js
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
…P-57 description tag
…ck to static responses
…er name format for redaction
…stability and structure
- Created a test suite for the plugin-nostr entrypoint to verify the plugin object and its services. - Added checks for the existence of the NostrService and its static properties. - Configured Vitest with a custom configuration file to include test files and set the testing environment.
…tability and structure
…proved functionality and structure
… replies and add corresponding tests
…proved functionality and structure
- Added reference to main monorepo https://github.com/anabelle/pixel - Updated character.json and character.ts to include monorepo info - Pixel now knows about the complete ecosystem structure - Individual repos still available as submodules
- Added line about being proudly open source to character bio - Reflects Pixel's philosophy of transparency and community - Updated both character.ts and regenerated character.json - 'Transparency is survival; closed source is just expensive coffin polish'
- Add multi-round search strategy that continues until quality interactions achieved - Implement adaptive quality gates with configurable strictness levels (normal/strict/relaxed) - Add topic expansion for fallback searches when initial topics yield no results - Introduce DiscoveryMetrics class for tracking success rates and adaptive behavior - Add progressive search expansion with broader time ranges and increased limits - Add configuration options for discovery quality settings - Ensure guaranteed minimum quality interactions per discovery run - Maintain backward compatibility while significantly improving discovery reliability New env vars: - NOSTR_DISCOVERY_MIN_QUALITY_INTERACTIONS (default: 1) - NOSTR_DISCOVERY_MAX_SEARCH_ROUNDS (default: 3) - NOSTR_DISCOVERY_STARTING_THRESHOLD (default: 0.6) - NOSTR_DISCOVERY_THRESHOLD_DECREMENT (default: 0.05) - NOSTR_DISCOVERY_QUALITY_STRICTNESS (default: normal)
- Add NOSTR_DISCOVERY_MIN_QUALITY_INTERACTIONS to .env.example - Add NOSTR_DISCOVERY_MAX_SEARCH_ROUNDS to .env.example - Add NOSTR_DISCOVERY_STARTING_THRESHOLD to .env.example - Add NOSTR_DISCOVERY_THRESHOLD_DECREMENT to .env.example - Add NOSTR_DISCOVERY_QUALITY_STRICTNESS to .env.example - Update .env with default values for new discovery settings These new environment variables allow fine-tuning of the quality-first discovery algorithm to balance interaction quality vs quantity.
- Add detailed logging for topic expansion (primary vs fallback) - Log search parameter expansion for each round - Track quality strictness changes (normal -> relaxed) - Log adaptive threshold activations and adjustments - Add round-by-round metrics tracking (quality, replies, avg score) - Log early termination when quality target is reached - Warn when discovery fails to meet quality requirements - Add debug logging for threshold comparisons and skip reasons These logs will help monitor and debug the new multi-round quality-first discovery behavior.
- Add WebSocketWrapper class to set maxListeners on WebSocket instances - Add NOSTR_MAX_WS_LISTENERS setting to .env.example - Prevent memory leak warnings when multiple pong listeners are added
- Add ElizaOS architecture and framework integration details - Add platform-specific setup guides (Telegram, Discord, Twitter, Nostr) - Add character development and customization section - Add plugin system documentation with examples - Add testing strategy and deployment instructions - Add comprehensive troubleshooting with platform-specific solutions - Add monitoring and analytics section - Expand from 114 to 400+ lines of professional documentation
- Add comprehensive server monitoring documentation - Include monitoring commands and configuration details - Document log management and troubleshooting procedures - Update performance monitoring strategies
…mework - Added socket.io-client to package.json for WebSocket support. - Created basic tests for bridge validation, rate limiting, and input validation in test-basic.js. - Implemented comprehensive tests for Nostr service and listener in test-comprehensive.js. - Developed integration tests for ElizaOS memory patterns in test-eliza-integration.js. - Added external post testing functionality in test-external-post.js. - Created integration test for LNPixels event processing in test-integration.js. - Developed listener tests with mock WebSocket in test-listener.js. - Implemented memory creation tests in test-memory.js. - Updated character configuration to include LNPIXELS_WS_URL. - Created lnpixels-listener.ts service file for future implementation.
…gement improvements
…ts using memory locks
…nd memory recording
…events and interactions
…ng for events and interactions
…ive insights (#11) * Initial plan * Add historical context to timeline lore generation Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Add tests for timeline lore historical context feature Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Add integration test and documentation for timeline lore context Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Update plugin-nostr/lib/narrativeMemory.js Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
#12) * Initial plan * Implement novelty-based candidate scoring system Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Remove temporary test scripts from repository Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Fix .gitignore formatting Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com>
* Initial plan * Add mute list filtering in homefeed realtime event handler Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Update plugin-nostr/test-mute-filtering.js Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Initial plan * Add storyline advancement detection and integration Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Fix checkStorylineAdvancement to be synchronous Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Add comprehensive documentation for storyline advancement feature Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Update plugin-nostr/test-storyline-advancement-integration.js Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update plugin-nostr/test-storyline-advancement-integration.js Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update plugin-nostr/lib/service.js Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Initial plan * Add longitudinal analysis feature to self-reflection engine Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Add documentation and demo for longitudinal analysis feature Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Add integration tests and prompt examples for longitudinal analysis Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com>
* Initial plan * Redesign LLM prompts with evolution-aware analysis - Updated _screenTimelineLoreWithLLM with evolution-focused prompts - Added recent narrative context to screening prompt - Added evolution metadata (evolutionType, noveltyScore) to screening - Updated _generateTimelineLoreSummary with narrative progression focus - Added evolutionSignal field to timeline lore digest - Prompts now prioritize developments over static topics - Updated token limits to accommodate richer prompts Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Add comprehensive tests and demonstration for evolution-aware prompts - Created service.evolutionAwarePrompts.test.js with full test coverage - Tests verify recent context inclusion in prompts - Tests verify evolution metadata in responses - Tests verify default values for backward compatibility - Created demo-evolution-aware-prompts.js showing before/after comparison - Demo clearly illustrates improved focus on narrative progression Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Add comprehensive documentation for evolution-aware prompts - Created EVOLUTION_AWARE_PROMPTS.md with complete documentation - Explains problem solved and key improvements - Documents evolution metadata (evolutionType, noveltyScore, evolutionSignal) - Provides detailed examples for all evolution types - Includes testing, monitoring, and troubleshooting guidance - Shows before/after comparisons and expected impacts Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Add implementation summary documenting all changes - Created IMPLEMENTATION_SUMMARY.md with complete overview - Documents all modified and new files - Lists all acceptance criteria met - Explains key features and expected impact - Provides testing recommendations and success metrics - Ready for production deployment Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> * Update plugin-nostr/lib/service.js Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Update plugin-nostr/lib/service.js Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jorparad <108901404+jorparad@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…on (Closes #4) (#21) * feat(nostr): topic evolution contextual scoring + narrative memory clusters; fix: digest lookback handling, case-insensitive storyline detection, stable storyline boost rounding; tests all green (32/32). Closes #4 * plugin-nostr: strengthen topic evolution and narrative context - Use sha256-based cache key (truncated) for TopicEvolution to reduce collisions - Introduce MAX_CONTENT_FOR_PROMPT constant to bound LLM prompt size - Bound topic cluster timeline via TOPIC_CLUSTER_MAX_ENTRIES env (default 500) - Normalize subtopic/angles to kebab-case and cap length for predictability - Skip neutral/stable evolution section in context summary to reduce noise - Harden narrative memory _loadRecentNarratives to handle sync getMemories mocks - Switch tests to static ESM imports for stability All plugin-nostr tests: 32 files, 182 tests passed locally * Update plugin-nostr/lib/narrativeMemory.js Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * feat(nostr): enhance saveInteractionMemory with context ID computation and legacy event ID handling * feat(nostr-topic-evolution): exclude just-recorded event from recency when scoring evolution\n\n- Prevents artificial +0.2 boost by removing current entry from recency window\n- Keeps diversity calc on last 10 minus latest\n- Add README Testing section to run plugin tests from plugin dir\n\nVerified: plugin-nostr tests pass (32 files, 182 tests) * Update plugin-nostr/lib/service.js Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --------- Co-authored-by: Anabelle Handdoek <git@huellaspyp.com> Co-authored-by: jp <108901404+jorparad@users.noreply.github.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
#23) * feat(nostr): adaptive trending algorithm with velocity/novelty/baseline; integrate into context accumulator and service; expose trending in current activity; add tests (Closes #6) * Update plugin-nostr/lib/adaptiveTrending.js Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * chore(nostr): log adaptive trending snapshot in trend detection to surface score/velocity/novelty/development * adaptiveTrending: fix created_at unit detection, maintain sorted history on insert, guard intensity denom; tests: import vitest, clarify baseline hours --------- Co-authored-by: Anabelle Handdoek <git@huellaspyp.com> Co-authored-by: jp <108901404+jorparad@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…avioral adjustments and mandatory changes
… for posts analysis
…etection (Issue #7) (#29) * feat: Implement adaptive storyline progression and emerging-pattern detection (Issue #7) - Add hybrid rule-based/LLM storyline detection system - Implement storyline lifecycle tracking through regulatory→technical→market→community phases - Add confidence-calibrated scoring boosts for engagement prioritization - Create online learning system for pattern recognition - Include comprehensive testing and backward compatibility verification - Add debug tools for batch analysis and validation All acceptance criteria from Issue #7 have been met with full backward compatibility. * fix: implement CodeRabbit AI review fixes for adaptive storyline progression - Fix debug-storyline-tracker.js constructor to use mock runtime - Correct analyzePost method calls to pass content, topics array, and timestamp - Fix stats field access to use getStats() method - Fix narrativeMemory.js constructor to use options object - Fix primaryTopic variable scope in service.js - Rename community phase from 'discussion' to 'conversation' to avoid collision - Update test assertions and comments for accuracy - Convert adaptiveTrending.test.js from CommonJS to ES modules - All 202 tests now passing * Update plugin-nostr/lib/storylineTracker.js Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * Update plugin-nostr/test-storyline-tracker.js Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * feat: enhance storyline context retrieval and analysis for improved narrative progression detection * refactor: remove redundant setup code for known phase detection tests --------- Co-authored-by: Anabelle Handdoek <git@huellaspyp.com> Co-authored-by: jp <108901404+jorparad@users.noreply.github.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
* Fix home feed interaction probabilities (Issue #24) - Increase homeFeedReactionChance from 0.05 to 0.15 (15%) - Increase homeFeedRepostChance from 0.005 to 0.01 (1%) - Increase homeFeedQuoteChance from 0.001 to 0.005 (0.5%) - Total interaction probability now ~16.5% vs previous 5.6% - Maintains 'like' reactions as most common to prevent spam * fix(nostr): update home feed interaction probabilities and add reply functionality * fix(nostr): refactor home feed reply handling and integrate image processing * fix(nostr): enhance reply handling by adding thread context retrieval --------- Co-authored-by: Anabelle Handdoek <git@huellaspyp.com>
* Initial plan * Implement content freshness decay algorithm with tests Co-authored-by: anabelle <445690+anabelle@users.noreply.github.com> * Fix storyline advancement detection to require content indicators Co-authored-by: anabelle <445690+anabelle@users.noreply.github.com> * Add comprehensive freshness decay documentation Co-authored-by: anabelle <445690+anabelle@users.noreply.github.com> * Freshness decay: remove extra advancement keyword gating; allow zero lookback; fix tests; update docs (fences + logic) * Tests: extract recurring theme constant; no functional change * Tests: isolate config cases from similarity bump/clamping; green suite for freshness decay * Refactor NarrativeMemory constructor for improved readability; remove unnecessary whitespace and comments * Update plugin-nostr/lib/service.js Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: anabelle <445690+anabelle@users.noreply.github.com> Co-authored-by: Anabelle Handdoek <git@huellaspyp.com> Co-authored-by: Anabelle Handdoek <github@huellaspyp.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* ci: run plugin-nostr vitest on all PRs (Fixes #34) * ci: finalize workflow trigger and caching * fix: Make logger calls safe in handleMention and handleDM to prevent test failures - Wrap all module-level logger calls with optional chaining (logger?.method?.()) - Add try-catch blocks around logger calls to prevent throwing in test environment - Initialize missing service properties in test setup (dmEnabled, dmReplyEnabled, dmThrottleSec) - Enhance @elizaos/core mock with createUniqueUuid, ChannelType, and ModelType exports - All 12 handlerIntegration tests now pass * fix: Add missing node-fetch dependency for image-vision module - Adds node-fetch ^2.7.0 to dependencies - Updates bun.lock - Fixes CI test failure: 'Cannot find module node-fetch' - Required by lib/image-vision.js for image URL processing * fix: Add node-fetch dependency to package.json and package-lock.json * fix: Update package-lock.json with node-fetch dependency - Regenerate package-lock.json to include node-fetch and its dependencies - Fixes npm ci error: 'Missing: node-fetch@2.7.0 from lock file' - Required for CI/CD pipeline compatibility * Update package.json Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --------- Co-authored-by: Anabelle Handdoek <git@huellaspyp.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
- Install @vitest/coverage-v8@^1.6.1 as dev dependency - Configure coverage in vitest.config.mjs with v8 provider - Add coverage scripts to package.json (test:coverage, test:coverage:watch) - Update .gitignore to exclude coverage reports (.nyc_output, *.lcov) - Add comprehensive coverage documentation to README - Configure coverage thresholds: 80% for lines/functions/branches/statements - Generate reports in text, html, json, and lcov formats Resolves #37 Co-authored-by: Anabelle Handdoek <git@huellaspyp.com>
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
Co-authored-by: anabelle <445690+anabelle@users.noreply.github.com>
Co-authored-by: anabelle <445690+anabelle@users.noreply.github.com>
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.
✅ COMPLETE: Text.js Test Coverage Implementation
Achievement: 100% Function Coverage
Successfully implemented comprehensive test coverage for the
text.jsmodule with 136 passing tests covering all 9 exported functions.Files Created
Coverage Summary
Test Results
Coverage Improvement
Testing Capabilities
Run Tests
Impact
Original prompt
Fixes #52
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.