Skip to content

Test inclusion patterns are derived from application code #19

Description

@nrainer

Characteristics

  • Issue Type: bug
  • Reproducibility: always
  • Severity: major
  • Execution Environment: Ubuntu x64

The problem is that test inclusion patterns are derived from the application code. (As a consequence, no tests from projects without application code are executed.)

Old ticket: Tests from modules without application code are skipped

Description

Modules that contain exclusively tests (and no source code) are skipped from the analysis. For example, some projects have a dedicated module for integration tests, which is skipped in this case. (Actually, the tests of this project get skipped, but the mutations analysis is conducted. A result file is created.) Hence, not all tests of a project will get executed.

Steps to reproduce

  1. Unzip the attached sample project. It is a multi-module project consisting of the modules core, extension, and tests. All modules contain tests, all modules except tests contain application code. The module tests does not contain application code and has no src/main/java folder.
  2. After building the project with mvn clean install, run pit-mp using mvn eu.stamp-project:pitmp-maven-plugin:run
  3. MyTest from the module tests covers a class from the module extension but does not get executed. See the attached mutation matrix.

Files

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions