Test Initialize vs. Class Initialize

November 18, 2013 · 1 min read

One common oversight we have encountered while working with developers is the mix up of the [TestInitialize] and [ClassInitialize] Attributes. When using these methods, be conscience of their differences. The Class Initialize attribute executes the decorated method once before the first test in the class is run, while the Test Initialize attribute executes before each test is run. There are different scenarios for when to use each, and putting code incorrectly in one or the other can cause unexpected behavior.

[ClassInitialize] annotated methods should be used to setup the state of the test class.  This includes variables that are shared in all tests, but the values of which either does not change or the changing of their values will not impact a test.

[TestInitialize] annotated methods should be used to revert the state of variables in which every test depends upon.  

When using these attributes, always make sure to run the entire set of unit tests as a group and not just individually. This will make sure that the test class has been setup properly.

This article is part of the GWB Archives. Original Author: Abhishek Anand

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.