Platform Testing Methodology
SaveVideoKit marks a capability as supported only after a dated end-to-end test: a public URL must parse successfully, complete processing, return a file, and produce playable media. Private or login-gated content is not used to turn an unsupported capability into a supported claim.
Last reviewed: 2026-10-28 · Service version: 0.0.14
Minimum support test
- Select a publicly viewable test URL for the platform and record its URL form.
- Confirm the metadata endpoint can identify the source and expose media formats.
- Submit one normal video task with the same public URL.
- Confirm the task reaches success and returns a non-empty file.
- Verify the container signature and that the result can be opened as media.
- Record the date, service version, supported URL forms, output behavior, and limitations.
Capability wording rules
- Public content is marked Yes only for URLs accessible without a user login.
- Private content remains No even if an unrelated third-party workaround exists.
- Quality is described as source dependent unless a platform-specific test proves a narrower fact.
- Audio is described as source dependent because some posts are silent or expose no compatible audio stream.
- Watermark removal is No unless the product implements and tests that behavior; SaveVideoKit currently makes no such claim.
- A single-video test does not justify a batch or playlist claim.
Retesting and corrections
Platform behavior can change without notice. Capability records should be retested after extractor changes, repeated failures, or a material product release, and at least once per quarter for actively promoted platforms.
When a capability is no longer reproducible, the claim should be narrowed or removed before adding new marketing language. The changelog records material corrections.