testing-assistant
Manages testing lifecycle including unit tests, integration tests, validation, and quality assurance.
What this skill does
# Testing Assistant Skill
Expert system for testing and validating the Claude Patent Creator.
**FOR CLAUDE:** Test scripts in scripts/ directory.
- Go directly to running appropriate test
- Run from project root
- Tests require active venv
- Only run diagnostics if tests fail
## When to Use
Running test suites, validating new features, testing after changes, debugging failures, creating tests, setting up CI/CD, performance testing, E2E validation, regression testing.
## Testing Pyramid
```
/\
/ \ E2E (Manual + Automated)
/----\
/ API \ Integration Tests
/--------\
/ Unit \ Unit Tests
/----------\
```
**Strategy:** More unit tests (fast, isolated), fewer integration (moderate), minimal E2E (slow).
## Test Suite Overview
```bash
scripts/
+-- test_install.py # Complete installation validation
+-- test_gpu.py # GPU detection and CUDA
+-- test_bigquery.py # BigQuery connection
+-- test_analyzers.py # Claims, spec, formalities
+-- test_embedding_speed.py # Performance benchmarks
+-- test_checkpoint.py # Index checkpoint system
```
**Quick Test:**
```bash
python scripts/test_install.py
```
## Manual Testing via Claude
Test MCP tools through Claude Code interface.
### Quick Test Examples
```
1. MPEP Search: "Search MPEP for claim definiteness requirements"
2. Patent Search: "Search for patents about neural networks filed in 2024"
3. Claims Review: "Review these claims: [paste test claims]"
4. Full Review: "/full-review" (with test application)
5. Diagrams: "Create a flowchart for this process: [describe]"
```
### Validation Checklist
```bash
[OK] MPEP search returns relevant results
[OK] BigQuery search finds patents
[OK] Claims analyzer identifies issues
[OK] Specification analyzer checks support
[OK] Formalities checker validates format
[OK] Diagrams generate successfully
[OK] Full review workflow completes
[OK] All MCP tools accessible
[OK] Error messages clear and helpful
[OK] Performance acceptable (<2s most ops)
```
## Creating New Tests
### Quick Start
```python
# Unit test template
def test_basic_functionality():
from mcp_server.your_module import YourClass
instance = YourClass()
result = instance.method("test input")
assert result is not None
print("[OK] test_basic_functionality passed")
```
**Test Categories:**
1. Basic functionality
2. Edge cases
3. Performance
4. Error handling
## Performance Testing
### Quick Benchmark
```python
from mcp_server.mpep_search import MPEPIndex
import time
index = MPEPIndex()
index.search("test", top_k=5) # Warm up
start = time.time()
result = index.search("claim definiteness", top_k=5)
duration = time.time() - start
print(f"Search took: {duration:.3f}s")
```
### Performance Thresholds
| Operation | Threshold | Notes |
|-----------|-----------|-------|
| MPEP search (first) | <3s | Model loading |
| MPEP search (subsequent) | <500ms | Cached models |
| BigQuery search | <2s | Network dependent |
| Claims analysis | <3s | 20 claims |
| Spec analysis | <10s | 10 pages |
| Diagram generation | <1s | SVG output |
## Troubleshooting Test Failures
| Problem | Solution |
|---------|----------|
| Import errors | Activate venv, `pip install -r requirements.txt` |
| GPU tests fail | Check `nvidia-smi`, reinstall PyTorch, or skip |
| BigQuery fails | Re-auth: `gcloud auth application-default login` |
| Index not found | Rebuild: `patent-creator rebuild-index` |
| Too slow | Check GPU usage, first run slower, check system load |
## Best Practices
1. Test after every change
2. Automated testing
3. Test pyramid (more unit, fewer E2E)
4. Fast tests (<5 min suite)
5. Isolated tests (no dependencies)
6. Clear assertions
7. Document tests
8. Version control tests
9. Regular execution (weekly)
10. Monitor performance
## Quick Reference
### Run All Tests
```bash
python scripts/test_install.py
python scripts/test_gpu.py
python scripts/test_bigquery.py
python scripts/test_analyzers.py
python scripts/test_embedding_speed.py
```
### Regression Test
```bash
python scripts/test_install.py || exit 1
python scripts/test_bigquery.py || exit 1
python scripts/test_analyzers.py || exit 1
echo "[OK] All regression tests passed!"
```
### Manual Checklist
```
□ Ask Claude to search MPEP
□ Ask Claude to search patents
□ Ask Claude to review claims
□ Run /full-review command
□ Generate a diagram
□ Verify all tools work
□ Check performance (<2s)
```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.