Re: expressive test macros (was: Report test_atomic_ops() failuresconsistently, via macros) - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: expressive test macros (was: Report test_atomic_ops() failuresconsistently, via macros)
Date
Msg-id 4d0e55f4-6a2f-b143-9ed2-157877051ba8@2ndquadrant.com
Whole thread Raw
In response to Re: expressive test macros (was: Report test_atomic_ops() failuresconsistently, via macros)  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
On 2019-10-08 06:59, Noah Misch wrote:
>> Btw., JUnit uses the ordering convention assertEquals(expected, actual),
>> whereas Perl Test::More uses is(actual, expected).  Let's make sure we
>> pick something and stick with it.
> Since we write "if (actual == expected)", I prefer f(actual, expected).  CUnit
> uses CU_ASSERT_EQUAL(actual, expected).

Yes, that seems to be the dominating order outside of JUnit.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Kohei KaiGai
Date:
Subject: Re: How to retain lesser paths at add_path()?
Next
From: Konstantin Knizhnik
Date:
Subject: Re: Global shared meta cache