/test-live

/project:test-live - Live Basic Memory Testing Suite

Execute comprehensive real-world testing of Basic Memory using the installed version. All test results are recorded as notes in a dedicated test project.

Usage

/project:test-live [phase]

**Parameters:**

• `phase` (optional): Specific test phase to run (`recent`, `core`, `features`, `edge`, `workflows`, `stress`, or `all`)
• `recent` - Focus on recent changes and new features (recommended for regular testing)
• `core` - Essential tools only (Tier 1: write_note, read_note, search_notes, edit_note, list_memory_projects, recent_activity)
• `features` - Core + important workflows (Tier 1 + Tier 2)
• `all` - Comprehensive testing of all tools and scenarios

Implementation

You are an expert QA engineer conducting live testing of Basic Memory. When the user runs `/project:test-live`, execute comprehensive test plan:

Tool Testing Priority

**Tier 1: Critical Core (Always Test)**

1. **write_note** - Foundation of all knowledge creation 2. **read_note** - Primary knowledge retrieval mechanism 3. **search_notes** - Essential for finding information 4. **edit_note** - Core content modification capability 5. **list_memory_projects** - Project discovery and session guidance 6. **recent_activity** - Project discovery mode and activity analysis

**Tier 2: Important Workflows (Usually Test)**

7. **build_context** - Conversation continuity via memory:// URLs 8. **create_memory_project** - Essential for project setup 9. **move_note** - Knowledge organization 10. **delete_project** - Project lifecycle management

**Tier 3: Enhanced Functionality (Sometimes Test)**

11. **view_note** - Claude Desktop artifact display 12. **read_content** - Raw content access 13. **delete_note** - Content removal 14. **list_directory** - File system exploration 15. **edit_note** (advanced modes) - Complex find/replace operations 16. **POSIX & schema** - `ls`, `find`, `grep`, `cat`, `tail`, `man`, `list_workspaces`, `schema_validate`/`schema_infer`/`schema_diff`

**Tier 4: Specialized (Rarely Test)**

17. **MCP Prompts** - Enhanced UX tools (ai_assistant_guide, continue_conversation)

Stateless Architecture Testing

**Project Discovery Workflow**

Test project selection:

1. **Initial Discovery**

• Call `list_memory_projects()` without knowing which project to use
• Verify the footer explains routing: pass a project name (or `[external_id]` as `project_id`); calls without one use the session's active project, then the configured default
• Confirm no scripted "ask the user" lines and no CLI-specific references

2. **Activity-Based Discovery**

• Call `recent_activity()` without project parameter (discovery mode)
• Verify the summary names the most active project: `Suggested project: '<name>' (most active with N items)`
• With no activity anywhere, verify it reports "No recent activity found in any project." and adds no scripted question

3. **Session Tracking Validation**

• Verify tool responses include `[Session: Using project 'name']`

4. **Single Project Constraint Mode**

• Test MCP server with `--project` parameter
• Verify all operations constrained to specified project
• Test project override behavior in constrained mode

**Explicit Project Parameters**

All tools must require explicit project parameters:

1. **Parameter Validation**

• Test all Tier 1 tools require `project` parameter
• Verify clear error messages for missing project
• Test invalid project name handling

2. **No Session State Dependencies**

• Confirm no tool relies on "current project" concept
• Test rapid project switching within conversation
• Verify each call is truly independent

Pre-Test Setup

1. **Environment Verification**

• Verify basic-memory is installed and accessible via MCP
• Check version and confirm it's the expected release
• Test MCP connection and tool availability

2. **Recent Changes Analysis** (if phase includes 'recent' or 'all')

• Run `git log --oneline -20` to examine recent commits
• Identify new features, bug fixes, and enhancements
• Generate targeted test scenarios for recent changes
• Prioritize regression testing for recently fixed issues

3. **Test Project Creation**

Run the bash `date` command to get the current date/time.

   Create project: "basic-memory-testing-[timestamp]"
   Location: ~/basic-memory-testing-[timestamp]
   Purpose: Record all test observations and results

Make sure to use the newly created project for all subsequent test operations by specifying it in the `project` parameter of each tool call.

4. **Baseline Documentation** Create initial test session note with:

• Test environment details
• Version being tested
• Recent changes identified (if applicable)
• Test objectives and scope
• Start timestamp

Phase 0: Recent Changes Validation (if 'recent' or 'all' phase)

Based on recent commit analysis, create targeted test scenarios:

**Recent Changes Test Protocol:** 1. **Feature Addition Tests** - For each new feature identified:

• Test basic functionality
• Test integration with existing tools
• Verify documentation accuracy
• Test edge cases and error handling

2. **Bug Fix Regression Tests** - For each recent fix:

• Recreate the original problem scenario
• Verify the fix works as expected
• Test related functionality isn't broken
• Document the verification in test notes

3. **Performance/Enhancement Validation** - For optimizations:

• Establish baseline timing
• Compare with expected improvements
• Test under various load conditions
• Document performance observations

**Example Recent Changes (Update based on actual git log):**

• Watch Service Restart (#156): Test project creation → file modification → automatic restart
• Cross-Project Moves (#161): Test move_note with cross-project detection
• Docker Environment Support (#174): Test BASIC_MEMORY_HOME behavi