assertEquals repeats message argument about shunit2 HOT 6 CLOSED

I recently noticed this too. Here's a patch with a single unit test added. (More
however would not be a bad idea.)

In addition to the above noted fix there are two other small changes.

Also "make test" in the source was not working because in this line
test: @echo
there should be a line break. And while I was in that section I added a "check"
target as sort of an alias for "test". (GNU automake uses "make check" instead 
of
"make test".

Hi Rocky,

I'm not sure what I need to do with assert-output.diff

I tried:

patch shunit2 < assert-output.diff

but got:

Processing...  I cannot find a patch in there anywhere.

Is there another patch-like utility I should be using? Do I need to split up
the file assert-output.diff and patch using just one part of it?

Regards, Mal.

Works for me 
$  cd ...shunit2/trunk/source/2.1
$  patch -p0 < ~/Desktop/assert-output.diff 
patching file src/shell/shunit2.
...

$ patch --version
patch 2.5.9
Copyright (C) 1988 Larry Wall
Copyright (C) 2003 Free Software Foundation, Inc.

This program comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of this program
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING

If this is not the version of that your are using get it from
ftp://ftp.gnu.org:/pub/gnu/patch/patch-2.5.4.tar.gz

If you can't do that, edit the file:


--- src/shell/shunit2   (revision 226)
+++ src/shell/shunit2   (working copy)
@@ -124,7 +124,7 @@

   [ -z "${shunit_message_:-}" ] && shunit_message_=''
   if [ $# -eq 3 ]; then
-    shunit_message_="${shunit_message_}$1"
+    shunit_message_="$1"
     shift
   fi
   shunit_expected_=$1

And look for a line like the one that has - in it and change it to a
line like the one that has + in it.

Good luck.

The provided patch is only a hack to fix a larger problem, one that stems from 
the _SHUNIT_LINENO_ macro. I'm 
looking into it.

Ah, actually it stems from the fact that when assertEquals fails, it calls 
failNotEqual, which itself extends the 
shunit_message_ variable yet again with the same information. Now, how to fix...

Fixed in rev# 230.