ProjectComponents

Stryker.NET uses custom classes to keep track of folders and files.

These FolderComponents and FileLeafs have readonly variants, this is done to ensure the mutated sourcecode and Mutants are not changed after the mutation is placed.

UML of the classes in the namespace Stryker.Core.ProjectComponents

Folder Components

Old Design

The global structure was as follows:

  • FolderComponent
  • FileLeaf

With the abstract class they both implement:

  • ProjectComponent

New Design

When implementing F# the old structure showed it's disadvantages since F# uses a different type to indicate syntaxtrees.

To solve this ProjectComponent was made generic ProjectComponent<T>.

However many parts of stryker use FolderComponent and FileLeaf without needing access to the syntaxtrees or to know what language is used. For this purpose the Interface IProjectComponent is used.

IParentComponent and IFileLeaf are implemented for the same reason. This enables code to ask for an IFileLeaf so It can access the elements that do not depend on the language, that being the syntaxtrees.

IFileLeaf<T> is needed to have languageagnostic notation for the syntaxtrees.

ReadOnly variants

Not al code is created equaly, and not all parts of stryker need write access to the ProjectComponents. This is why a IReadOnyProjectcomponent was created.

When expanding into F# we found the implementation lacking and expanded upon it. There are ReadOnly variants of FolderComponent and FileLeaf:

  • ReadOnlyFolderComponent
    • ReadOnlyFileLeaf

The readonly variants do not need access to the syntaxtrees so they are languageagnostic which improves the expandability of Stryker.NET

FolderComponent and FileLeaf both contain the functions ToReadOnly() and ToReadOnlyInputComponent(). ToReadOnly() returns the ReadOnly varient of said type. ToReadOnlyInputComponent() does the same, just casted to IReadOnlyProjectComponent.