[isaacde]

Hi Everyone,

I've been having a frustrating time this morning trying to use the Visual Studio 2008 Professional Unit Testing framework. For some reason an Assert is failing that shouldn't be as far as I can tell.

Here's what I'm working with, in simplified version:

int[,] expected = { { 10, 0, 0, 0 }, { 0, 0, 0, 0 }, { 0, 0, 0, 0 }, { 0, 0, 0, 10 } };
int[,] wtfexpected = { { 10, 0, 0, 0 }, { 0, 0, 0, 0 }, { 0, 0, 0, 0 }, { 0, 0, 0, 10 } };
Assert.AreEqual(expected, wtfexpected);

This returns:
Assert.AreEqual failed. Expected:<System.Int32[,]>. Actual:<System.Int32[,]>.

I can replace the last line with:

Assert.AreEqual<int[,]>(expected, wtfexpected);

And it does not change the result.

However if I use my target object's property 'stones' of type int[,] instead:

BoardState target = new BoardState();
int[,] expected = { { 10, 0, 0, 0 }, { 0, 0, 0, 0 }, { 0, 0, 0, 0 }, { 0, 0, 0, 10 } };
int[,] actual;
target.Stones = expected;
actual = target.Stones;
Assert.AreEqual(expected, actual);

The assert works.

Here's some code from in my BoardState class:

	public class BoardState
	{
		private int[,] stonesDistribution;

		public BoardState()
		{
			//initialize the board
			//stones array shows where the stones are
			stonesDistribution = new int[4,4]{ { 10, 0, 0, 0 } , { 0, 0, 0, 0 }, { 0, 0, 0, 0 }, { 0, 0, 0, 10 } };
		}
		public int[,] Stones
		{
			get
			{
				return stonesDistribution;
			}
			set
			{
				stonesDistribution = value;
			}
		}
	 }

Can anybody help me out?

[egof]

When your doing the comparison its doing the memory address and not the actual values.

[SwiftStriker00]

Ok, that is weird. I tried this

[TestMethod]
		public void dichelp() {
			int[,] expected = { { 10, 0, 0, 0 }, { 0, 0, 0, 0 }, { 0, 0, 0, 0 }, { 0, 0, 0, 10 } };
			int[,] wtfexpected = { { 10, 0, 0, 0 }, { 0, 0, 0, 0 }, { 0, 0, 0, 0 }, { 0, 0, 0, 10 } };

			for( int i = 0; i < 4; i++ ) {
				for( int j = 0; j < 4; j++ ) {
					Assert.AreEqual(expected[i,j], wtfexpected[i,j]);
				} 
			}
		}

And that passed.


What I think is happening is there no compareTo<T>() method for int[,], and even if there is its not going to matter. When you create an array you set X amount of memory where X = sizeOftype*sizeOfarray. Any the computer is most likely placing expected at [MEM:0000] and wtfexpected at [MEM: 1001] for example, and when you compare them, its just returning the start index of the int[,].

The reason it works when you pass it into your stones, is that your actually making a reference and not a new one. Essentially pointers to the same orignial object at [MEM:0000].

[isaacde]

Awesome, thank you that makes sense. I'll just compare item by item