A strange nunit problem

wolfganguhr

Hello

To demonstrate the a small problem we have in n-unit I've add three screenshoots. Here in T02_Revaluation, I've implemented no Assert.Equal-Test. That is Testroutine which "just runs" and the test is postive. But no test has been done.

I've implemented three System.Diagnostics.Debug.WriteLines in the code which shall be tested, this is the line "delta ....", xxx and yyy. Then I've clicked on run and I've made three screen shoots.

So nor the code itself neither the test code has been changed. And the test code does not write anything to the database so that data are changed or else. Three clicks and three different reaktions and some other reactions are possible.

Does anyone has an idea to handle the problem?

Best regards
Wolfgang

pokorra

Please attach the source code of the test file.

pokorra

On a second thought, does it make a different to use Console.WriteLine instead of System.Diagnostics.Debug.WriteLine?

I think, the output is just delayed. The server only shuts down triggered by the TearDown() method, marked with TestFixtureTearDown. This means, all tests have been finished. This might be in a different thread perhaps, and this means the output gets mixed up with the WriteLines from the test.

Does it cause trouble for your tests?

wolfganguhr

pokorra wrote
Please attach the source code of the test file.

Done - see 1109. I only have renamed the problem to T03_Revaluation because nunit lists and runs the routines in alphabetical order. So I give the tests a number to enforce a test sequence.

And the sources of the test are "clearly arranged" ...

[Test]
public void T03_Revaluation()
{
string[] currencies = new string[2];
currencies[0] = "GBP";
currencies[1] = "YEN";
decimal[] rates = new decimal[2];
rates[0] = 1.234m;
rates[1] = 2.345m;
TRevaluationWebConnector.Revaluate(43, "EUR",
"5300", "3700",currencies, rates);
}

pokorra wrote
I think, the output is just delayed.

Ok, there my be a delay, but this is one the half of the problem. In one case the server is not stopped, in one case it is stopped one times and in the third case it is stopped two times.