Explain Test Passed->Test Explorer (using NUnit)

It's upto you to write the logic to either consider the test passed or failed.

 

The nUnit does not apply any logic on it's own to consider your business logic.

 

It only gives it's result  based on the "Assert" statements you have written.

 

Usually what I do is I write multiple test cases for a method or function so that to test each and every aspect of it, by passing valid values, invalid values and those which will raise exceptions. Then I assert accordingly using Assert.Equal, Assert.NotEqual, etc methods.

 

The following link explains very basic ones.

http://www.infragistics.com/community/blogs/dhananjay_kumar/archive/2015/07/27/getting-started-with-net-unit-testing-using-nunit.aspx

 

P.S. explore more on FakeItEasy, FluentAssertions, Ploeh.AutoFixture nuGet packages, I use those along with nUnit