Skip to content

Addressing Precision Issues in Floating-Point Value Comparison #202

@ManuelLoaizaV

Description

@ManuelLoaizaV

Description

When comparing floating-point values in unit tests using toBe, false negatives occur due to slight differences in precision. This issue leads to discrepancies like

    Expected: 24.9
    Received: 24.900000000000002

Solution: Implement toBeCloseTo for Floating-Point Comparison

To mitigate this problem, Jest documentation recommends using toBeCloseTo instead of toBe for comparing floating-point values. This method allows specifying a precision level for comparison. Refer to Jest documentation for details.

Screenshots

Exercise 129: Calculate Bill Total
image

Exercise 137: Compute Compount Interest
image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions