✨ Specify Config File To Use For Running Mutation Tests At Project Level #108
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- `IMutationTest` component no longer implements `IUnitTest` but only `IHaveTests` - Refactoring of `IMutationTest` component to improve maintenability : the way CLI options required by Stryker are computed is now centralized.
Makes `IReportCoverage` inherits `IRequireNuGetPackage` to inform that a nuget package is required to be present
candoumbe
changed the title
candoumbe
deleted the
feature/specify-config-file-to-use-for-running-mutation-tests-at-project-level
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚀 New features
• Added IDoHotfixWorkflow component which represents the hotfix workflow
• Added IDoFeatureWorkflow component which represents the feature workflow
• Added IDoColdfixWorkflow component which represents the coldfix workflow
• ICreateGithubRelease.Assets property can be used to specify which artifacts to associate with a Github release (#103)
• IMutationTest component can send --config-file option to Stryker CLI (#90)
🚨 Breaking changes
• Removed Github.IPullRequest.Token property. This property was previously used by GitHub.IGitFlowWithPullRequest and GitHub.IGitFlowWithPullRequest when finishing a feature/coldfix is.
• Refactored IWorkflow component and removed inheritance from IHaveMainBranch component
• Refactored ICompile component to no longer extend IRestore component
• Refactored IPack component to no longer extend ICompile component
• Refactored IMutationTest.MutationTestsProjects type from (Project SourceProject%2C IEnumerable TestsProjects) to IEnumerable:
this new type allows to specify the path to the configuration file to use during each mutation test run.
• IMutationTest component no longer implements IUnitTest but only IHaveTests
🛠️ Fixes
• Removed nofetch option (when calling gitversion tool) in order to compute semver version number more accurately (#96).
🧹 Housekeeping
• Refactoring of IMutationTest component to improve maintenability : the way CLI options required by Stryker are computed is now centralized.
• Added GitHubToken value in parameters.local.json : this value will be consumed directly to interact with the github repository.
• IGitflow%2C IGithubflow components extends IDoHotfixWorkflow component
• IGitflow%2C IGithubflow components extends IDoHotfixWorkflow component
• Added NugetApi valuen in parameters.local.json to interact directly with NuGet from local environment
• Added documentation for IMutationTest classes
Full changelog at https://github.com/candoumbe/Pipelines/blob/feature/specify-config-file-to-use-for-running-mutation-tests-at-project-level/CHANGELOG.md
Resolves #90