Spaces:
Paused
Paused
Update testing_guide.md
Browse files- testing_guide.md +1 -45
testing_guide.md
CHANGED
|
@@ -211,28 +211,7 @@ Notes: {additional context}
|
|
| 211 |
|
| 212 |
## 7. Test Schedule
|
| 213 |
|
| 214 |
-
|
| 215 |
-
- Test 2 videos per domain (12 total)
|
| 216 |
-
- Establish baseline scores
|
| 217 |
-
- Identify major issues
|
| 218 |
-
|
| 219 |
-
### Phase 2: Domain Deep Dive (Week 2-3)
|
| 220 |
-
- Focus on underperforming domains
|
| 221 |
-
- Test 5+ videos per weak domain
|
| 222 |
-
- Tune domain presets if needed
|
| 223 |
-
|
| 224 |
-
### Phase 3: Edge Cases (Week 4)
|
| 225 |
-
- Very short videos (<3 min)
|
| 226 |
-
- Very long videos (>30 min)
|
| 227 |
-
- Low quality/audio videos
|
| 228 |
-
- Multiple language content
|
| 229 |
-
|
| 230 |
-
### Phase 4: Regression Testing (Ongoing)
|
| 231 |
-
- After any code changes
|
| 232 |
-
- Run standard test set (1 video per domain)
|
| 233 |
-
- Compare to baseline
|
| 234 |
-
|
| 235 |
-
---
|
| 236 |
|
| 237 |
## 8. Success Criteria
|
| 238 |
|
|
@@ -251,29 +230,6 @@ Notes: {additional context}
|
|
| 251 |
|
| 252 |
---
|
| 253 |
|
| 254 |
-
## 9. Team Responsibilities
|
| 255 |
-
|
| 256 |
-
| Role | Responsibilities |
|
| 257 |
-
|------|------------------|
|
| 258 |
-
| **Tester 1** | Sports, Gaming domains |
|
| 259 |
-
| **Tester 2** | Music, Vlogs domains |
|
| 260 |
-
| **Tester 3** | Podcasts, General domains |
|
| 261 |
-
| **Lead** | Aggregate results, track issues, coordinate fixes |
|
| 262 |
-
|
| 263 |
-
---
|
| 264 |
-
|
| 265 |
-
## 10. Tools Needed
|
| 266 |
-
|
| 267 |
-
- [ ] Test video dataset (18+ videos minimum)
|
| 268 |
-
- [ ] Google Sheet for results tracking
|
| 269 |
-
- [ ] Video player for clip review
|
| 270 |
-
- [ ] Screen recording for bug reports (optional)
|
| 271 |
-
- [ ] Stopwatch for processing time measurement
|
| 272 |
-
|
| 273 |
-
---
|
| 274 |
-
|
| 275 |
-
---
|
| 276 |
-
|
| 277 |
## 11. Experimentation Guide
|
| 278 |
|
| 279 |
This section explains how to systematically test different settings to find optimal configurations.
|
|
|
|
| 211 |
|
| 212 |
## 7. Test Schedule
|
| 213 |
|
| 214 |
+
tentative
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 215 |
|
| 216 |
## 8. Success Criteria
|
| 217 |
|
|
|
|
| 230 |
|
| 231 |
---
|
| 232 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 233 |
## 11. Experimentation Guide
|
| 234 |
|
| 235 |
This section explains how to systematically test different settings to find optimal configurations.
|