Skip to content

Consider refactoring Frontier(BaseFork) into scoped mixins #2025

@fselmo

Description

@fselmo

Frontier is growing infinitely as the first BaseFork implementation class. This is a really powerful class that gives us the flexibility of making fork-based decisions in testing. I think the complexity of this class and what it does will only keep growing.

We should consider abstracting out some of the logic in this class - perhaps into fine-scoped mixin classes with focused separation of concerns. See this comment for a bit of extra context.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-test-forksArea: execution_testing.forksC-refactorCategory: refactorstaleThe Issue/PR has not had any activity for 60 days. PRs will be automatically closed.

    Type

    No type
    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