ComparisonAssertion in the unit testing framework should not require overloaded operator <<

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This forces the usage of less expressive assertions on types that don't define such overloads. We could use SFINAE to dispatch to a specialization of ComparisonAssertion that prints the compared values if the types being compared are ostream printable, otherwise omit printing them.

            Assignee:
            Andy Schwerin
            Reporter:
            Adam Midvidy (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: