Changes
The two most recent releases in full, then the version history. The
distribution's Changes file is the authoritative record.
0.49 — November 2026
Enhancements
- Surviving mutants feed harness generation.
fuzz-harness-generator --mutation-results(ormutation_resultstogenerate()) readstest-generator-mutate's JSON report. Each surviving numeric-boundary mutant is traced to the comparison it mutated and becomes aminormaxon the matching input field. Existing constraints are never replaced, and survivors that need a hand-written test are listed. Details. - Documented constraints are checked, not assumed. A
bound, member list or pattern that came only from POD is probed from
outside. A routine that contradicts its documentation is reported at
the end of the run, and
fuzz-harness-generator --strict-documentedturns each finding into a failing test for CI. - Element schemas. An arrayref or hashref parameter
can describe its elements with a nested
schema, which can nest again and build objects fromisaorcan. Details. - Transforms can have their own input fields. One
hand-written schema can cover two call shapes, such as
NameCase([...])andNameCase('A', 'B'). - Regex-based strings are deterministic and bounded.
The schema's
seeddrives them, generation is limited by the newregex_timeoutconfig key (default 5 seconds), and a pattern that hangs or cannot be satisfied falls back or skips its cases instead of failing the run. A failing case names the seed and the input that was sent. - An
existing_filesemantic. A routine that only tests that a path exists (-e/-f) is no longer skipped: the harness creates a temporary file for it. Only routines that read the file's contents stay skipped. - Portable, repeatable schema YAML. A
matchespattern is written as a plain string rather than a!!perl/regexpobject, and maps and analysis notes are sorted, so repeated runs are byte-identical. - One provenance marker. Each parameter carries a
single
_sourcevalue, replacing_type_checked,_bounds_unverifiedand_from_input_spec; provenance is also tracked per constraint. The allowed values live inApp::Test::Generator::Provenance. demo_extractoris no longer installed. It ships asexamples/demo_extractor. The bug tracker in the distribution metadata is now GitHub issues.
Bug fixes
- Generated values stay inside declared bounds. Random
integers, numbers and strings respect a maximum, pattern-generated
strings honour
min/maxlength, and a pattern-constrained field is never given the fixed whitespace, newline or BOM samples its own pattern excludes. - Length guards are read correctly.
croak ... if length < 5used to be read asmax: 4; it now givesmin: 5, the same ascroak ... unless length >= 5. A formal Input spec's bounds are compared with the inferred ones, so an impossible range is reported instead of emitted. importis called as a class method,Module->import(...), the wayuseinvokes it.- Extraction reads a single documented parameter as
the first positional argument when the routine reads no hash of
arguments, keeps the value list from
=itemprose for a parameter named only by a formal spec, and drops a reference used as a parameter name instead of emittingHASH(0x...). - File descriptors. An object that opens a file on first use and keeps it, such as a logger, is no longer reported as a leak; a descriptor is reported when the same target is opened again.
generate()is documented as returning 1, which is what it has always returned.
0.48 — 11 November 2026
Enhancements
- Harnesses check what a call leaves behind. Every call
is checked for changes to the caller's globals (
$_,$/,$,and$;), for files left in the working directory and for leaked file descriptors. The last two have config keys,check_filesandcheck_fds, for routines whose job is to write a file or hand a handle back. - Accessors are tested for damage to their object. A
getter must not change the object it was given, and a getset must change
nothing but its own property. Memoised values and lazy initialisation are
not reported. The config key is
check_accessors. - Unbuildable classes are skipped, not failed. When a
constructor refuses — an abstract base class, for example —
extract-schemasmarks the class so that its routines are skipped. - A
directorysemantic. A parameter the routine tests with-dis given a real temporary directory instead of an invented string.
Bug fixes
- Coverage-guided fuzzing now gets coverage. The fuzzer
was reading the names of the coverage criteria rather than the counters,
so every run was random-only. The program must be started under
Devel::Cover. Dies on hashref inputs with
propertiesare now recorded as bugs, and corpus files are UTF-8. - BenchmarkGenerator quotes and escapes every name and
constructor value, so the generated script always compiles, and no longer
dies on
input: undef. - Extraction recognises accessors that guard on
defined($arg), no longer takes a getter driven by%ENVfor a getset, types a wrapping setter asany, gives a wrapper that forwards@_the target's input schema, emitsmatchespatterns as Regexp objects, and no longer types a return built from$1as an integer. - Harnesses now pass scalar inputs to positional
routines, compare numeric getset round trips with
==, and only assert that a wrong-typed argument dies when the routine's own validator enforces the type. deploy-workflowsships the current workflow files again; the embedded copies had fallen behind.- Prerequisites. The modules a generated harness loads (Test::Most, Test::Returns, Test::LectroTest) are now runtime prerequisites.
Earlier releases
| Version | Date | Highlights |
|---|---|---|
| 0.47 | 7 October 2026 | extract-schemas --function NAME for isolating one routine, a self-fuzz summary that lists every routine and why it was skipped, and $pkg, $proto and $klass recognised as invocants. |
| 0.46 | 18 August 2026 | Duplication drill-down pages, sortable and reorderable dashboard tables with saved state, and the domain, path, data-flow and transaction test suites. |
| 0.45 | 10 August 2026 | Bug fixes and test-suite work. |
| 0.44 | 21 July 2026 | Schema extraction and dashboard refinements. |
| 0.43 | 11 July 2026 | The version required by t/fuzz.t's Test::Needs guard. |
| 0.42 | 7 July 2026 | POD example extraction, benchmark generation, portable workflow deployment, CPAN Testers reproduction scripts, corpus minimisation. |
| 0.41 | 28 June 2026 | In-place mutation strategy: mutants are written to the project's own lib/ so use lib in test files cannot load the original code. |
| 0.40 | 25 June 2026 | A large release; see Changes. |
| 0.39 | 24 May 2026 | See Changes. |
| 0.38 | 18 May 2026 | See Changes. |
Full history:
MetaCPAN's
changelog, or the Changes file in
the repository.
Upgrading
cpanm App::Test::Generator
Schemas are compatible across releases: a schema that works with 0.49 has
worked since the transform syntax settled. Generated harnesses are
regenerated by tooling, so a stale one is replaced rather than migrated.
If you keep generated .t files in version control, regenerate
them after upgrading — an older harness may not know about a type or a
config key that the new version accepts.