Page MenuHomePhabricator

Make assertTrue() / assertFalse() messages more descriptive
ClosedPublic

Authored by epriestley on Mar 9 2014, 3:08 AM.
Tags
None
Referenced Files
F15516659: D8465.id.diff
Fri, Apr 18, 8:23 PM
F15511529: D8465.id20075.diff
Thu, Apr 17, 2:47 AM
F15506816: D8465.id20075.diff
Tue, Apr 15, 2:24 PM
F15478476: D8465.id20074.diff
Mon, Apr 7, 11:35 PM
F15451521: D8465.diff
Fri, Mar 28, 10:32 PM
F15421897: D8465.id.diff
Mar 22 2025, 3:14 AM
F15395943: D8465.id20075.diff
Mar 16 2025, 10:52 AM
F15387661: D8465.diff
Mar 15 2025, 2:45 AM
Subscribers

Details

Summary

See discussion in D8460. Primarily, this prints out the failing value when a true/false assertion fails, so if it was something useful (like a function result) it's visible.

Test Plan

Added assertTrue("quack"):

   FAIL  ArcanistDiffParserTestCase::testParser
Assertion failed, expected 'true' (at ArcanistDiffParserTestCase.php:16).

ACTUAL VALUE
quack

Added assertFalse("quack"):

   FAIL  ArcanistDiffParserTestCase::testParser
Assertion failed, expected 'false' (at ArcanistDiffParserTestCase.php:16).

ACTUAL VALUE
quack

Added assertEqual("quack", "moo"):

   FAIL  ArcanistDiffParserTestCase::testParser
Assertion failed, expected values to be equal (at ArcanistDiffParserTestCase.php:16).
Expected: quack
  Actual: moo

Diff Detail

Repository
rARC Arcanist
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

joshuaspence edited edge metadata.

Yeah, this makes sense.

This revision is now accepted and ready to land.Mar 9 2014, 3:22 AM

90% of the time it's probably not useful (especially if you're judicious about assertEqual() even when the expected parameter is false), but I think it's never really worse.

epriestley updated this revision to Diff 20075.

Closed by commit rARCa90a72c648ac (authored by @epriestley).