You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DUnitX is not calling the test with the correct TestCase parameters on Android 32 bits, when there are many Singles or Doubles in the parameters. I made a small project reproducing the problem (download the full project here: DUnitXBug.zip). Here's the code:
I don't so mobile dev so I'm not setup to test this, but my guess is that the wrong AreEqual overload is being called since there isn't an overload with Single parameters. Happy to accept a PR for this (assuming it doesn't break other platforms).
I don't so mobile dev so I'm not setup to test this, but my guess is that the wrong AreEqual overload is being called since there isn't an overload with Single parameters.
No, it’s not related to AreEqual function, the value of the last string parameter is also wrong.
Ok, but that doesn't alter the fact that I am not able to test this. Did you try stepping into the dunitx code to see where the bug is? You will need to add DUNITXDEBUG to your project defines to enable debug info on the dunitx code.
DUnitX is not calling the test with the correct TestCase parameters on Android 32 bits, when there are many Singles or Doubles in the parameters. I made a small project reproducing the problem (download the full project here: DUnitXBug.zip). Here's the code:
Windows result (expected):
Android32 result (wrong):
The text was updated successfully, but these errors were encountered: