Page MenuHomePhabricator

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

Authored by epriestley on Mar 9 2014, 3:08 AM.
Tags
None
Referenced Files
F15421897: D8465.id.diff
Sat, Mar 22, 3:14 AM
F15395943: D8465.id20075.diff
Sun, Mar 16, 10:52 AM
F15387661: D8465.diff
Sat, Mar 15, 2:45 AM
F15384155: D8465.diff
Fri, Mar 14, 6:58 PM
F15293728: D8465.id20074.diff
Wed, Mar 5, 4:35 AM
Unknown Object (File)
Feb 1 2025, 3:13 AM
Unknown Object (File)
Jan 29 2025, 2:43 AM
Unknown Object (File)
Jan 29 2025, 2:43 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).