Interface MutationPass

one rewrite, applied to every counterexample it fits

interface MutationPass {
    adds?: boolean;
    apply(
        program: MutationProgram,
    ): MutationTarget | Promise<MutationTarget | undefined> | undefined;
    category: MutationCategory;
    description: string;
    keepsGraph?: boolean;
    name: string;
}

Index

Properties

adds? category description keepsGraph? name

Methods

Properties

`Optional` `Readonly`adds

adds?: boolean

the rewrite adds code of its own, about which the linter may say more, but never less

`Readonly`category

category: MutationCategory

`Readonly`description

description: string

what the pass does, with an example, as the wiki lists it

`Optional` `Readonly`keepsGraph

keepsGraph?: boolean

the rewrite only moves code around or renames it, so the graphs flowR builds keep their shape

`Readonly`name

name: string

what the mutants of this pass are named after

Methods

apply

apply(
program: MutationProgram,
): MutationTarget | Promise<MutationTarget | undefined> | undefined
the mutated program, or undefined if the pass does not apply
Parameters
- program: MutationProgram
Returns MutationTarget | Promise<MutationTarget | undefined> | undefined
- Defined in test/functionality/_helper/mutation/mutation-passes.ts:49