Skip to content

Make LineCoverageTestFitness non-binary and add tests#143

Open
Aditya-9215 wants to merge 1 commit intose2p:mainfrom
Aditya-9215:feature/line-coverage-non-binary-clean
Open

Make LineCoverageTestFitness non-binary and add tests#143
Aditya-9215 wants to merge 1 commit intose2p:mainfrom
Aditya-9215:feature/line-coverage-non-binary-clean

Conversation

@Aditya-9215
Copy link
Copy Markdown

This PR replaces the binary fitness computation of LineCoverageTestFitness with a distance-based approximation.

Previously:

  • Covered → 0
  • Not covered → 1

Now:

  • Covered → 0
  • Not covered → value > 0 based on execution distance

This provides better guidance for search-based algorithms and is a prerequisite for supporting line coverage in DynaMOSA.

Unit tests are added to verify the new behavior.

Copilot AI review requested due to automatic review settings April 16, 2026 17:04
@Aditya-9215
Copy link
Copy Markdown
Author

Hi,

I followed your suggestion and split this into a separate PR.

This PR focuses only on making LineCoverageTestFitness non-binary, without modifying DynaMOSA yet.

Please let me know if this aligns with your expectations before I proceed further.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates LineCoverageTestFitness to return a non-binary (distance-based) fitness value for uncovered lines, aiming to provide a smoother optimisation signal (e.g., for DynaMOSA), and adds unit tests for the new behaviour.

Changes:

  • Replace binary line-coverage fitness (0/1) with a non-binary approximation based on execution trace data.
  • Add tests covering “covered → 0.0” and “not covered → > 0.0”.
  • Add goal properties for line-coverage and checked-coverage test fitness functions.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.

File Description
src/pynguin/ga/coveragegoals.py Implements non-binary line-coverage fitness and adds goal properties; also modifies SPDX header.
tests/ga/test_linecoverage_fitness.py Introduces unit tests for the new line fitness behaviour using dummy execution results.
tests/fixtures/simple_line_target.py Adds a new fixture module intended for line-coverage testing.

Comment on lines +1 to +3
# SPDX-License-Identifier: MIT
# SPDX-FileCopyrightText: 2026 Aditya Sinha
# SPDX-License-Identifier: MIT
Comment on lines +39 to +47
execution = DummyExecutionResult(covered_lines=[], executed_code_objects=[1, 2])
chromosome = DummyChromosome(execution)

# Monkey patch run method
fitness._run_test_case_chromosome = lambda _: execution

value = fitness.compute_fitness(chromosome)

assert value > 0.0
Comment on lines +6 to +7
# SPDX-FileCopyrightText: 2026 Aditya Sinha
# SPDX-License-Identifier: MIT
Comment on lines +431 to +436
# If nothing executed → maximum penalty
if not trace.executed_code_objects:
return 1.0

# Use number of executed code objects as rough distance signal
return float(len(trace.executed_code_objects))
Comment on lines +419 to +436
# Otherwise → return non-binary distance
return 1.0 + self._approximate_distance(result)

def _approximate_distance(self, result: ExecutionResult) -> float:
"""Estimate how far execution was from reaching this line.

This is a lightweight approximation based on execution trace information.
It provides a non-binary signal without requiring full control-flow analysis.
"""
try:
trace = result.execution_trace

# If nothing executed → maximum penalty
if not trace.executed_code_objects:
return 1.0

# Use number of executed code objects as rough distance signal
return float(len(trace.executed_code_objects))
Comment on lines +1 to +13
def foo(x: int) -> int:
if x > 0:
return x + 1
elif x == 0:
return 0
else:
return x - 1


def bar(y: int) -> int:
if y % 2 == 0:
return y * 2
return y + 3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants