<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Hilaire,<br>
<br>
On 7/23/2023 8:07 AM, Hilaire Fernandes via Cuis-dev wrote:
<blockquote cite="mid:1ea9c5a2-5a88-65bd-39b6-6d900bfd36f4@free.fr"
type="cite">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<p>Hi, <br>
</p>
<p>IMHO, In the method below argument names should be reversed<br>
</p>
<p>TestCase>>assert: <b>expected</b> equals: <b>actual</b><br>
self<br>
assert: expected = actual<br>
description: [ self comparingStringBetween: expected
and: actual ]<br>
</p>
<p><br>
</p>
<p>I read the method <br>
</p>
<p>TestCase>>assert: actual equalsExpected: expected but it
<br>
</p>
<p><br>
</p>
<p>but it is odd and confusing to have both</p>
<p><br>
</p>
<p>Hilaire<br>
</p>
</blockquote>
<br>
I also think that #assert:equals: is ambiguous and somewhat
confusing. I'm not sure if removing it is a good decision, it could
break a lot of code for a very minor gain in consistency. Perhaps a
method comment recommending the use of #assert:equalsExpected: ?<br>
<br>
Thanks,<br>
<pre class="moz-signature" cols="72">--
Juan Vuletich
cuis.st
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich
linkedin.com/in/juan-vuletich-75611b3
twitter.com/JuanVuletich</pre>
</body>
</html>