Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Is there a way to conditionally exclude a test?
Message
 
To
07/03/2013 17:09:06
General information
Forum:
ASP.NET
Category:
Testing and debugging
Environment versions
Environment:
C# 4.0
OS:
Windows 7
Network:
Windows 2003 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01567786
Message ID:
01567820
Views:
35
Interesting selling strategy though. Confuse - Insult - Land. CIL. :). Does that work at all? I see I've not only been missing out on shifting pardigms in IT lately :)




>Oy, what a mess. I'm available for contracting work to fix this.
>
>>This is what base class has:
>>
>>
>>[TestClass]
>>   public abstract class UnitTestBase
>>   {
>>      public static IniFile iniFile, systemIniFile;
>>      public static MiddlewareMain middlewareMain;
>>      public static Boolean isClassInitialized = false;
>>
>>      [ClassInitialize] // Runs only once before all tests.
>>      public static void ClassInit(TestContext context)
>>      {
>>         AppInfo.ModuleName = "Middleware";
>>
>>         if (null == systemIniFile)
>>            systemIniFile = new SystemIni();
>>         if (null == iniFile)
>>            iniFile = new LocalIni();
>>         if (null == middlewareMain || !isClassInitialized)
>>         {
>>                     database.CreateDatabaseConnection();
>>            middlewareMain                   = new MiddlewareMain(database, application);            
>>            middlewareMain.Rollback          = true;
>>         }
>>         isClassInitialized = true;
>>      }
>>
>>      [TestInitialize] // TestInitialize runs multiple times before each test.
>>      public void TestInit()
>>      {
>>         if (!isClassInitialized)
>>            ClassInit(null);
>>      }
>>   }
>>
>>
>>>Here does middleware get instantiated?

If things have the tendency to go your way, do not worry. It won't last. Jules Renard.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform