How to get Property.Name

In some scenarios you might be interested to know current method / property name.
Eg I called some common code from each property and wanted to know calling property name.
Obviously C# doesnt have something like CurrentProperty.Name

You can archive that analysing Stack trace:

<br />[System.Runtime.CompilerServices.MethodImpl(System.Runtime.CompilerServices.MethodImplOptions.NoInlining)]<br />public static void MyMethod () {<br />propertyName = new System.Diagnostics.StackTrace().GetFrame(2).GetMethod().Name.Substring(4);<br />

You might want to change index no in GetFrame to get interested information

Disable constraints

I've looked the way to temporarily turn off all DB's constraints (eg table relationships)

I needed to copy (using INSERTs) one DBs tables to another DB I know I can archive that by executing commands in proper order (to do not brake relationships)

But it would be easier if I could turn off checking constraints temporarily and turn on it back after operation finish.

So, you can disable FK and CHECK constraints only in SQL 2005+ using below command

ALTER TABLE foo WITH NOCHECK CONSTRAINT ALL

or

ALTER TABLE foo WITH NOCHECK CONSTRAINT CK_foo_column

Note: Primary keys and unique constraints can not be disabled.

Unit testing in Visual Studio 2008 Team System - part IV

Next (maybe not last) part re units tests inside VS.

[Ignore()]

Useful if one of test methods failed – you can use [Ignore()] attribute to decide later what to do with that test

So, our complete class code looks now as follow:

<br /> <br /> <br /> <br /> <br /> <br /> <br />using bank; <br />using Microsoft.VisualStudio.TestTools.UnitTesting; <br />namespace UnitTests <br />{ <br /> <br /> <br /> /// <summary> <br /> ///This is a test class for AccountTest and is intended <br /> ///to contain all AccountTest Unit Tests <br /> ///</summary> <br /> [TestClass ()] <br /> public class AccountTest { <br /> <br /> <br /> private TestContext testContextInstance; <br /> <br /> /// <summary> <br /> ///Gets or sets the test context which provides <br /> ///information about and functionality for the current test run. <br /> ///</summary> <br /> public TestContext TestContext { <br /> get { <br /> return testContextInstance; <br /> } <br /> set { <br /> testContextInstance = value; <br /> } <br /> } <br /> <br /> /// <summary> <br /> ///A test for TransferFunds <br /> ///</summary> <br /> [TestMethod ()] <br /> [ExpectedException(typeof(InsufficientFundsException))] <br /> public void TransferFundsTest() { <br /> Account source = new Account (); <br /> source.Deposit(200F); // source.Ballance = 200 <br /> <br /> Account destination = new Account(); <br /> destination.Deposit(150F); // destination.Ballance = 150 <br /> <br /> // Call tested method <br /> source.TransferFunds ( destination, 195F ); <br /> // source.Ballance = 200 - 100 = 100; <br /> // destination.Ballance = 150 + 100 = 250; <br /> <br /> // Perform checks <br /> Assert.AreEqual( 250F, destination.Balance); // OK <br /> Assert.AreEqual( 100F, source.Balance); // OK <br /> <br /> // No exception thrown - test failed <br /> } <br /> <br /> [TestMethod ()] <br /> [Ignore()] <br /> public void TransferWithInsufficientFundsAtomicity() { <br /> Account source = new Account (); <br /> source.Deposit(200F); // source.Ballance = 200 <br /> <br /> Account destination = new Account(); <br /> destination.Deposit(150F); // destination.Ballance = 150 <br /> <br /> try { <br /> // Call tested method <br /> source.TransferFunds ( destination, 300F ); <br /> // source.Ballance = 200 - 300 = -100; -> exceptin thrown <br /> // destination.Ballance = 150 + 300 = 450; <br /> } <br /> catch (InsufficientFundsException expected) { <br /> // source balance less than 10F - exception catch here... <br /> } <br /> <br /> // Balances will not change as Exception thrown <br /> <br /> // Perform checks <br /> Assert.AreEqual( 200F, source.Balance); // OK <br /> Assert.AreEqual( 150F, destination.Balance); // OK <br /> <br /> // No exception thrown - test failed <br /> } <br /> } <br />} <br /> <br /> <br /> <br /> <br /> <br /> public void TransferFunds ( Account destination, float amount ) { <br /> // Throw exception if minimum ballance exceeded <br /> if (balance-amount< 10F ) throw new InsufficientFundsException(); <br /> <br /> destination.Deposit(amount); // ++ <br /> Withdraw(amount); // -- <br /> <br /> } <br /> <br />

Refactoring

If we look at above code we can see lot of code duplication – refactoring is necessary.

We can appoint common block of code, it is worth to split tests on small 1 function methods.

To achieve that we will:

• Define local members (source + destination)
• Add Init() method marked by attribute [TestInitialize()] – executed before each tests
  (please note method need to be public)
• Break down test methods on 3 atomic methods

After all our code shall look as follow:

<br /> <br />using bank; <br />using Microsoft.VisualStudio.TestTools.UnitTesting; <br />namespace UnitTests <br />{ <br /> <br /> <br /> /// <summary> <br /> ///This is a test class for AccountTest and is intended <br /> ///to contain all AccountTest Unit Tests <br /> ///</summary> <br /> [TestClass ()] <br /> public class AccountTest { <br /> private TestContext testContextInstance; <br /> /// <summary> <br /> ///Gets or sets the test context which provides <br /> ///information about and functionality for the current test run. <br /> ///</summary> <br /> public TestContext TestContext { <br /> get { <br /> return testContextInstance; <br /> } <br /> set { <br /> testContextInstance = value; <br /> } <br /> } <br /> <br /> Account source; <br /> Account destination; <br /> <br /> /// <summary> <br /> /// Initializes each tests in class <br /> /// </summary> <br /> [TestInitialize()] <br /> public void Init() { <br /> // COnstruct 2 objects <br /> source = new Account(); <br /> destination = new Account(); <br /> <br /> source.Deposit(200F); // source.Ballance = 200 <br /> destination.Deposit(150F); // destination.Ballance = 150 <br /> } <br /> <br /> <br /> /// <summary> <br /> ///A test for TransferFunds <br /> ///</summary> <br /> [TestMethod ()] <br /> public void TransferFundsTest() { <br /> // Call tested method <br /> source.TransferFunds ( destination, 100F ); <br /> // source.Ballance = 200 - 100 = 100; <br /> // destination.Ballance = 150 + 100 = 250; <br /> <br /> // Perform checks <br /> Assert.AreEqual( 100F, source.Balance); // OK <br /> Assert.AreEqual( 250F, destination.Balance); // OK <br /> } <br /> <br /> /// <summary> <br /> ///A test for TransferFunds <br /> ///</summary> <br /> [TestMethod ()] <br /> [ExpectedException(typeof(InsufficientFundsException))] <br /> public void TransferFundsMinBallanceExceededTest() { <br /> // Call tested method <br /> source.TransferFunds ( destination, 195F ); <br /> // source.Ballance = 200 - 195 = 5; <br /> // destination.Ballance = 150 + 195 = 345; <br /> <br /> // Exception need be thrown <br /> } <br /> <br /> [TestMethod ()] <br /> public void TransferWithInsufficientFundsAtomicity() { <br /> try { <br /> // Call tested method <br /> source.TransferFunds ( destination, 300F ); <br /> // source.Ballance = 200 - 300 = -100; -> exceptin thrown <br /> // destination.Ballance = 150 + 300 = 450; <br /> } <br /> catch (InsufficientFundsException expected) { <br /> // source balance less than 10F - exception catch here... <br /> } <br /> <br /> // Balances will not change as Exception thrown <br /> <br /> // Perform checks <br /> Assert.AreEqual( 200F, source.Balance); // OK <br /> Assert.AreEqual( 150F, destination.Balance); // OK <br /> <br /> // No exception thrown - test failed <br /> } <br /> } <br />} <br /> <br /> <br />

Unit testing in Visual Studio 2008 Team System - part III

In previous post Unit testing in Visual Studio 2008 Team System - part II I’ve described how to perform units tests using new test functionality in VS2008 TS.

In this part I will continue describing test functionality (base on nUnit guide’s example)

In Part II I’ve showed how to use Assert methods to evaluate tests.

Asert() is not only one way to perform tests. Units testing gives also possibility to examine if expected exception occurred.

Let’s return to nUnit example.

[ExpectedException(typeof(InsufficientFundsException))]

If we assume that minimum acceptable account’s balance can be 10F, and if balance is less custom exception (named “InsufficientFundsException“) will be throw.

In that case we can add attribute to our test method informing that we expecting exception:
[ExpectedException(typeof(InsufficientFundsException))]

So, we need to archive this is

1) implement own Exception class:

public class InsufficientFundsException : ApplicationException {}

2) correct orrect our test method:


<br /><br />[TestMethod ()] <br /> [ExpectedException(typeof(InsufficientFundsException))]<br /> public void TransferFundsTest() {<br /> Account source = new Account (); <br /> source.Deposit(200F); // source.Ballance = 200<br /><br /> Account destination = new Account();<br /> destination.Deposit(150F); // destination.Ballance = 150<br /><br /> // Call tested method<br /> source.TransferFunds ( destination, 195F );<br /> // source.Ballance = 200 - 195= 5;<br /> // destination.Ballance = 150 + 195= 245;<br /><br /> // Perform checks<br /> Assert.AreEqual( 250F, destination.Balance); // OK<br /> Assert.AreEqual( 100F, source.Balance); // OK<br /><br /> // No exception thrown - test failed<br /> }<br /><br />

3) correct our production Account.TransferFunds() method:

<br /><br /> public void TransferFunds ( Account destination, float amount ) {<br /> // Throw exception if minimum ballance exceeded<br /> if (balance-amount< 10F ) throw new InsufficientFundsException();<br /><br /> destination.Deposit(amount); // ++<br /> Withdraw(amount); // --<br /><br /> }<br /><br /><br />

Unit testing in Visual Studio 2008 Team System - part II

In previous post (http://csharpmatters.blogspot.com/2009/03/unit-testing-in-visual-studio-2008-team.html) I’ve described new test functionality in VS2008 TS.

In this post I drill down unit tests inside VS2008 more detail.

VS built-in units tests use attributes (similar to NUnit).

Attributes are used to denote various test methods and test classes.

Common attributes:

[TestClass()] mark class representing a unit test case. Class need to be public.

[TestMethod()]marks Test Method

Another popular attributes:

[ClassInitialize()] –code need to be run before running the first test in the class

[ClassCleanup()] – code need to be run after all tests in class

[TestInitialize()] – code need to be run before each test

[TestCleanup ()] – code need to be run after each test

Example:

[TestClass()]
public class MyClassTest

[TestMethod()]
public void MyClassInitTest()

VS provides Assert class with static methods to check various conditions.

All Asserts methods accept 2 parameters: Boolean condition and exception message provided by user. If condition is FALSE: test exception with custom msg is thrown.

More about assert methods here: http://msdn.microsoft.com/en-us/library/microsoft.visualstudio.testtools.unittesting.assert_members.aspx

If you worked with nUnit tool you can see a lot of similarities.

(Please note UI testing is not supported in the current version of unit testing with VS.NET 2008)

Let’s follow nUnit example (http://www.nunit.org/index.php?p=quickStart&r=2.4.7) but using VS built-in tests this time.

Production code example:
<br />public class Account<br /> {<br /> #region Members<br /> private float balance; <br /> #endregion Members<br /><br /><br /> #region Properties<br /> public float Balance {<br /> get { return balance; }<br /> } <br /> #endregion Properties<br /><br /> #region Public Methods<br /> public void Deposit ( float amount ) {<br /> balance += amount;<br /> }<br /> public void Withdraw ( float amount ) {<br /> balance -= amount;<br /> }<br /> public void TransferFunds ( Account destination, float amount ) {<br /> }<br /> #endregion Public Methods<br /><br /> }<br />

Test Class code:
<br /><br />namespace UnitTests<br />{<br /> /// <summary><br /> ///This is a test class for AccountTest and is intended<br /> ///to contain all AccountTest Unit Tests<br /> ///</summary><br /> [TestClass ()]<br /> public class AccountTest {<br /><br /> private TestContext testContextInstance;<br /><br /> /// <summary><br /> ///Gets or sets the test context which provides<br /> ///information about and functionality for the current test run.<br /> ///</summary><br /> public TestContext TestContext {<br /> get {<br /> return testContextInstance;<br /> }<br /> set {<br /> testContextInstance = value;<br /> }<br /> }<br /> /// <summary><br /> ///A test for TransferFunds<br /> ///</summary><br /> [TestMethod ()]<br /> public void TransferFundsTest() {<br /> Account source = new Account (); <br /> source.Deposit(200F);<br /><br /> Account destination = new Account();<br /> destination.Deposit(150F);<br /><br /> // Call tested method<br /> source.TransferFunds ( destination, 100F );<br /><br /> // Perform checks<br /> Assert.AreEqual( 250F, destination.Balance);<br /> Assert.AreEqual( 100F, source.Balance);<br /> }<br /> }<br />}<br /><br /><br />

After test run you will see that test failed with message:

TransferFundsTest UnitTests Assert.AreEqual failed. Expected:<250>. Actual:<150>.

All because production method TransferFunds() has no implementation yet.

Let’s correct that as follows:

public void TransferFunds ( Account destination, float amount ) {

destination.Deposit( amount );

Withdraw(amount);

}

After that correction test is passed.

Please find more about testing in next part(s) of post

Unit testing in Visual Studio 2008 Team System

As you probably noticed, VS.NET 2008 comes with unit testing integrated within.

There two ways to create test:

1) From existing, production code

2) Manually

Obviously option 1 requires less work, and I’m going to describe this scenario.

Quick start:

1. Open your existing project
2. Right click on the source and select “Create Unit Tests”
3. Select methods you want to create tests
4. (Optionally) Change settings (by clicking on “Settings..” button
5. Click OK to create new test project

After all new test project will be created and added to your solution.

Now you can change run your tests (Menu Test \ Run)

TIP: you can double click on test result record to see more detail view.

What's also very useful: you can also add some brakpoints and start debuging test classes.

Of course auto generated tests are not very valuable there are inconclusive (at least)

You need to change test methods according to unit tests art – but most of dirty work was done by VS!

In next posts I will try explain more about unit testing.

Keep reading!

Five favourite new features in VS 2008

1. Extension methods

This feature I like most.
Thanks that you can extend standard object methods

Lets look below example:

<br />public static class StringHelper {<br /> public static bool IsTrimmed (this string a) {<br /> return a.Trim().Equals(a);<br /> }<br />}<br />

As you noticed only difference is “this” word near parameter.
Here you are how to use this:

<br />string a = "abc ";<br />string b = "bcd";<br /><br />bool result1 = a.IsTrimmed(); // uses extenston<br />bool result2 = StringHelper.IsTrimmed(b) ; // standard call<br />


Please also note that if you add extension to object type – all variable types will get access to this extension!

My favourite example (coming from Scott Gu’s blog http://weblogs.asp.net/scottgu/archive/2007/03/13/new-orcas-language-feature-extension-methods.aspx )


<br />// Extension<br />public static bool In (this object o, System.Collections.IEnumerable c) {<br /> foreach( object i in c) {<br /> if (i.Equals(o)) return true;<br /> }<br /> return false;<br />};<br /><br /><br />// *** EXAMPLE ***<br /><br /><br />// search string array<br />bool result = "a".In( new string[] {"a","b","c"} );<br />Console.WriteLine(result );<br /><br />// search List<int><br />List <int> intVals = new List<int>();<br />intVals.Add(10);<br />intVals.Add(11);<br />intVals.Add(12);<br />intVals.Add(13);<br /><br />result = 13.In(intVals)<br />


2. Object Initializers

This is feature I waited long. It gives you possibility to assign in one line public properties in braces after constructor, like this:

<br /><br />TestClass tc = new TestClass() {Name="John", Surname = "Kowalsky"};<br /><br />public class TestClass {<br /> public string Name {<br /> get; set;<br /> }<br /> public string Surname {<br /> get; set;<br /> }<br />}<br />


3. Automatic Properties

If you don’t like all extra effort you need to do to write fields and properties code you can use below snippet.

<br /><br />public string Name {<br /> get;<br /> set;<br />}<br />

CLR 3.x (during compilation) will generate fields and property code for you.
Note: you will not be able to access generated field (only way is only through setters and getters)

4. Local variable type inference

This feature allows you define local variables without defining their types (similar to variant variables in some cases), so you can do this:


<br />var var1 = 10;<br />var var2 = “some string”;<br />var var3 = new SomeType();<br />

Compiler generates appropriate int, string and “SomeType” variables in early-bound strongly-typed fashion.

Personally, I’d prefer explicit types definitions – this gives more clarity in code.
But in some cases (mainly for shorten long code) I’m finding it usefull:

<br /><br />// Foreach<br />Foreach (var i in someCollection) <br /> …<br />// instead of Dictionary<int,> dictCol = new Dictionary<int,>();<br />var dictCol = new Dictionary<int,>();<br />

5. Lambdas

Described soon...




Other nice features:
- partial methods