Four Test Rounds Answer Four Different Questions
| Round | Keep Constant | Deliberately Change | Question It Answers |
|---|---|---|---|
| A: Same-File Repeats | Audio Bytes & System Version | Repeat Submission Only | Whether the Computation Is Consistent |
| B: Re-Record Under Same Conditions | Device, Text, Distance, Room | Say It Again | How Much Natural Expression Varies |
| C: Single-Variable Test | All Other Conditions | Change Only One of Distance, Device, or Environment | The Direction of One Variable’s Effect |
| D: Cross-Version Regression | Fixed Audio Sample | System Version | Whether an Update Changes the Result |
Mixing these tests together collapses natural human variation, recording conditions, and program changes into one vague “stable/unstable” conclusion.
Make a Minimal Record Before You Start
Record the device and browser, selected microphone, room, approximate mouth-to-microphone distance, whether system noise reduction is enabled, the text used, recording date, and page version. For file-based tests, keep the original file rather than a copy forwarded through a messaging app, because forwarding may re-encode it.
Choose a natural, complete sentence rather than sustaining a single vowel. It should include normal pauses and multiple articulation positions, while being read as similarly as possible each time. Make one practice recording before the formal comparison to reduce changes caused by first-time microphone tension.
Do Not Compare Only the Final Label
The primary label may emerge from competition among several close candidates. Even a small change in underlying pitch, brightness, or stability can swap the order of two similar templates. Compare whether the recording passed quality checks, changes in primary dimensions, the order of the top three candidates, and the final label together, rather than treating every wording difference as a total failure.
CVoice processes the same file deterministically and uses the file digest to keep minor presentation details consistent for identical input. Re-recording creates a new file, changing both real acoustic features and the digest, so reasonable variation in the result is expected.
How to Write an Honest Test Conclusion
- If A is inconsistent, first check the system version, asynchronous failures, random processes, or cache behavior.
- If A is consistent but B varies, focus on expressive state and recording control.
- If C shifts noticeably only on one device type, investigate automatic gain, noise reduction, and frequency response.
- If D changes, explain why in the update log and retain samples that can be retested.
A Ready-to-Use Record Template
Test purpose:Same-file consistency / re-recording variation / single variable / cross-version.
Fixed conditions:Device, browser, text, distance, environment.
Changed condition:Write only one at a time.
What to observe:Quality status, primary dimensions, candidate order, anomaly notices.
Conclusion boundary:What this result can support, and what it cannot be generalized to.