Comparison
Folt vs manual VM testing
A single VM gives you one combination. Folt can expand a scan into 216 isolated environment runs and return one report you can compare between releases.
Folt vs manual vm testing
One stack vs repeatable coverage
Your VM covers the stack you configure. Folt can systematically cover 4 PHP versions · current and previous WordPress releases · 7 themes · 20 conflict plugins, with the selected coverage and run total shown before launch.
Folt vs manual vm testing
Serial setup vs parallel execution
Manual coverage grows one setup at a time. Folt provisions selected environments in parallel, applies the same probes, and groups their results into a single scan report.
Folt vs manual vm testing
Inconsistent setup vs identical probes
Manual testing can drift through different core releases, forgotten plugin combinations, or skipped flows. Each selected Folt environment run follows the same activation, crawl, and signal-capture process.
Folt vs manual vm testing
Flexible debugging vs comparable evidence
A hand-built VM is ideal for exploratory debugging. Folt is designed for consistent release checks, with environment labels, captured evidence, and report-to-report comparison.
Decision guide
Choose based on the job
The approaches are complementary: automate broad, repeatable checks, then reproduce a specific failure locally when you need an interactive debugger.
Choose Folt when…
- You need the same coverage applied before each release.
- You want failures tied to an exact PHP, WordPress, theme, or plugin combination.
- You need one report that can be reviewed and compared by a team.
Choose manual vm testing when…
- You are investigating one already-known environment in depth.
- You need interactive access to alter server state while debugging.
- Your target stack depends on infrastructure that cannot be represented by an isolated test environment.
Questions to settle before choosing
- Does one scan mean one environment run?
- No. A scan is the report-producing job you configure; it expands into environment runs. The current full matrix uses 216 runs, while narrower scans use fewer.
- Can the Free plan run the full matrix?
- No. Free includes 100 environment runs per month, so use a smaller evaluation scan or choose a paid plan for broader recurring coverage.
- Should manual testing disappear?
- No. Keep focused manual reproduction for debugging and UX judgment. Use automated matrix testing to decide which combinations deserve that attention.
$ folt scan ./your-plugin.zip
Test the combinations that matter before you ship.
100 environment runs per month on Free. No credit card required.
4 PHP versions · current and previous WordPress releases · 7 themes · 20 conflict plugins