search

stefan2904 / shunit2

Automatically exported from code.google.com/p/shunit2
0 stars 0 forks source link

Issue with line number macro. #22

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run a test like this: ${_ASSERT_EQUALS_} "some msg" 'x' 'y'

What is the expected output? What do you see instead?
I got this error:
ASSERT:[13] some msg expected:<x> but was:<y>
but got this instead:
shunit2:ERROR assertEquals() requires two or three arguments; 4 given
shunit2:ERROR 1: some 2: msg 3: x

What version of the product are you using? On what operating system?
2.1.5

Please provide any additional information below.

Original issue reported on code.google.com by GavinBra...@gmail.com on 6 May 2010 at 9:00

GoogleCodeExporter commented 9 years ago 
I got the svn tree, run shunit2 test collection under source/2.1 and noticed 
that
some tests startSkipping if no ${LINENO:-} variable available. Assertion line 
number
reports are very useful. Sadly I do not master Bourne shells so much a to 
figure out
where the problem is...

Original comment by jcbor...@gmail.com on 24 May 2010 at 9:50

GoogleCodeExporter commented 9 years ago 
What shell were you using with this? Could you run the lib/versions script 
included with the source and give the output here?

Original comment by kate.war...@gtempaccount.com on 15 Mar 2011 at 12:27

GoogleCodeExporter commented 9 years ago 
I'm actually able to reproduce this under Linux (Ubuntu 10.04) with dash, so 
I'll work on fixing it at least.

Original comment by kate.war...@gtempaccount.com on 16 Mar 2011 at 9:19