Skip to content

Refactor HistoryTest.cpp to use HistoryViewModel (from CalcViewModel) instead of CalculatorHistory (from CalcManager) #783

@rudyhuyn

Description

@rudyhuyn

Describe the bug

All our unit tests related to the History function use CalculatorHistory while we should use HistoryViewModel to also detect bugs and regressions in our view models (some difference between the 2, the order is different for example). This modification will bring our unit tests closer to how we actually manage the history in the Calculator project.

Requested Assignment
If possible, I would like to fix this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Pri: 2approvedcodebase qualityIssues that are not bugs, but still might be worth improving (eg, code hygiene or maintainability)

    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