Skip to content

Configuration #11

@JoranHonig

Description

@JoranHonig

Currently vertigo leverages a range of command line parameters to configure mutation testing runs.
With a decently sized projects one might end up using +10 command line parameters, which is-- not ideal.

To solve this vertigo should be extended with the ability to use configuration files.

Example of what this could look like:

vertigo run -c vertigo.yml

Example configuration:

networks:
    - development 1

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions