Skip to content

πŸ—ƒ A schema for mutation testing results with the web components to visualise it πŸ“Š

License

Notifications You must be signed in to change notification settings

stryker-mutator/mutation-testing-elements

Folders and files

NameName
Last commit message
Last commit date
Nov 22, 2024
Feb 22, 2024
Mar 15, 2024
Aug 23, 2022
Jan 13, 2025
Jan 18, 2025
Jul 22, 2024
Dec 22, 2020
Oct 28, 2020
Jun 21, 2024
Jun 6, 2024
Nov 16, 2023
Apr 30, 2021
Nov 25, 2024
Nov 16, 2023
Apr 5, 2019
Feb 17, 2023
Nov 25, 2024
Sep 14, 2024
Jan 18, 2025
Jan 18, 2025
Oct 30, 2020
Feb 22, 2024
Nov 16, 2023
Feb 22, 2024
Feb 27, 2024

Repository files navigation

Mutation testing badge Build Status

Mutation testing elements

Welcome to the mutation testing elements mono repo.

It is a lernajs mono repository. Please see the packages directory to navigate to a sub package.

Versioning

The mutation-testing-report-schema and mutation-testing-elements versions will be kept in sync.

The schema can have major and minor releases, as well as patch releases. A bug or documentation update will mean a patch release. Backward compatible changes mean a minor release, breaking changes will mean a major release.

The mutation-testing-elements major and minor version will be in sync with the schema, however it can have patch releases for changes of the elements without a schema update.

Note that this is not strict semver 2.0.0. See #5 for the reasoning behind it.

An example (just for clarification, versions are not based on reality):

Schema version Supported mutation-testing-elements implementations
1.0.0 1.0.0, 1.0.1
1.1.0 1.0.0, 1.0.1, 1.1.0, 1.1.1
2.0.0 2.0.0, 2.0.1
2.0.1 2.0.0, 2.0.1

Releasing

Releasing is done with from the travis build server. Perform the following steps:

  • Clone the repo and run npm install.
  • Run npm run lerna:version:patch, npm run lerna:version:minor or npm run lerna:version:major (based on the release you want). Lerna will figure out which packages need to be released and prompt to ask if it is OK.
  • After the new tag is pushed to the master branch, it should be released via a github workflow.