Testing Documentation
GreenLeaf's internal testing showing software defects with specific error rates and crash data.
⚠️ Treat as Real Client Matter
This is client work product documenting their internal testing. Before using any tool, consider what information you're inputting and whether that use is appropriate.
Tool Selection Opportunity
Task: Analyze technical data, calculate statistics, translate technical concepts for legal arguments
Non-AI Options
- Spreadsheet calculations for statistics (mean, variance)
- Manual creation of evidence summary organized by legal element
- Consultation with technical expert (if retained)
AI Options (Tools You Have)
- CoCounsel/Protégé: Document analysis within privileged platforms
- Gemini/Copilot: Could explain general technical concepts—but would you need to share client-specific data, or could you ask general questions about software testing standards?
Selection Considerations
- The data tables contain client-specific testing results—confidential work product
- Could you ask general questions (e.g., "What is acceptable accuracy for inventory management software?") without sharing the client's specific data?
- For statistical calculations, a spreadsheet may be faster and doesn't raise confidentiality concerns
- Consider: What would you need to verify if AI explained technical concepts?
GREENLEAF TECHNOLOGIES, INC.
Software Testing Documentation
| Prepared by | James Morrison, Operations Manager |
|---|---|
| Date | January 25, 2026 |
Executive Summary
This document summarizes testing conducted on the inventory management software delivered by Vertex Solutions LLC on January 15, 2026. Testing revealed two critical defects that render the software unsuitable for GreenLeaf's business operations.
Test 1: Inventory Count Accuracy
Methodology
We conducted controlled tests entering known quantities of inventory items and comparing the system's recorded values against the actual quantities entered.
Test Protocol
- Clear test environment of all inventory data
- Enter a known quantity of a single SKU
- Record the quantity displayed by the system
- Repeat 10 times per SKU across 5 different SKUs
- Calculate variance between entered and displayed quantities
Results
| SKU | Quantity Entered | System Display | Variance |
|---|---|---|---|
| EP-500 | 100 | 117 | +17% |
| EP-500 | 100 | 84 | -16% |
| EP-500 | 100 | 91 | -9% |
| EP-500 | 100 | 108 | +8% |
| EP-500 | 100 | 82 | -18% |
| BG-200 | 250 | 212 | -15% |
| BG-200 | 250 | 289 | +16% |
| BG-200 | 250 | 271 | +8% |
| BG-200 | 250 | 208 | -17% |
| BG-200 | 250 | 295 | +18% |
| CP-750 | 500 | 423 | -15% |
| CP-750 | 500 | 582 | +16% |
| CP-750 | 500 | 419 | -16% |
| CP-750 | 500 | 574 | +15% |
| CP-750 | 500 | 590 | +18% |
| Average Absolute Variance | 14.8% | ||
Conclusion
The inventory tracking function exhibits consistent and significant inaccuracies. Variance of 15-20% is not within any reasonable definition of "acceptable industry tolerances." Industry standard for inventory management software is accuracy within 1-2%.
Test 2: Reporting Function Capacity
Methodology
We tested the reporting function's ability to generate reports of increasing size to determine the maximum capacity.
Test Protocol
- Populate database with test inventory data
- Generate report with increasing numbers of line items
- Record success/failure and any error messages
- Identify the threshold at which the system fails
Results
| Line Items | Result | Error Message |
|---|---|---|
| 100 | ✓ Success | N/A |
| 250 | ✓ Success | N/A |
| 400 | ✓ Success | N/A |
| 500 | ✓ Success | N/A |
| 550 | ✗ Failure | "System Error: Report generation failed" |
| 600 | ✗ Failure | "System Error: Report generation failed" |
| 750 | ✗ Failure | Application crash, no error message |
| 1000 | ✗ Failure | Application crash, no error message |
| 2000 | ✗ Failure | Application crash, browser unresponsive |
Maximum Functional Capacity: ~500 line items
Conclusion
The reporting function cannot handle reports exceeding approximately 500 line items. GreenLeaf currently has 2,147 active SKUs. The software cannot generate company-wide inventory reports, which is a fundamental requirement for inventory management.
Impact Assessment
Business Impact of Inventory Inaccuracy
- Cannot rely on system for reorder decisions
- Risk of stockouts or overstock situations
- Manual verification required for all inventory data
- QuickBooks integration produces inaccurate financial data
Business Impact of Reporting Limitation
- Cannot generate company-wide inventory reports
- Cannot produce accurate reports for financial audits
- Must continue using manual spreadsheet processes
- Defeats purpose of implementing inventory software
Tester Information
| Primary Tester | James Morrison, Operations Manager (5 years with company) |
|---|---|
| Secondary Tester | Lisa Park, Warehouse Supervisor (3 years with company) |
| Tertiary Tester | Carlos Mendez, IT Specialist (2 years with company) |
All testers followed identical protocols and achieved consistent results.
Attachments
- Exhibit A: Complete test data spreadsheets
- Exhibit B: Error log files from system crashes
- Exhibit C: Screenshots of inventory discrepancies
- Exhibit D: Video recordings of test procedures