A: 

Sample:

    Assert.AreNotEqual(0, result.Count);
     [exec]
     [exec] Tests run: 11, Failures: 1, Not run: 0, Time: 50.422 seconds
     [exec]
     [exec] Failures:
     [exec] 1) Domain.UnitTest.ManagerTest.TestEmbeddedIndex
 :   Expected: not 0
     [exec]   But was:  0
     [exec]

Is this what you are looking for?
Assert is very extensive. On fail of one of the conditions Nunit throws an error.

Assert.AreEqual(),Assert.AreSame(), Assert.Contains(),Assert.Fail();

Additionally Nunit has things like

[ExpectedException]

Dig into the documentation to learn more..

Cherian
+1  A: 

Settings for the tabs are in the NUnit options - see the docs here.

For instance, if you check Display Console Error Output then that tab will display text written to Console.Error by your tests.

Gary.Ray
+1  A: 

Based on the Edit update:
If I were you I would do this as part of the build mechanism. In nant I’d do something like this…

<target name="setup" description="Initializes test properties">
    <echo message="Sucessfully initialized tests" />
</target>

Showing console messages after every [Test] is a bad idea IMHO. It delays the tests which counts when you run 1000’s of them. Tests are meant to be blazingly fast.

Cherian