Just found out something interesting about TestDriven.Net. It allows you to run code logic as a test, even when the [TestMethod] attribute is not on the method you're testing.
However don't try doing this with an client side integration test, as you'll just get an endpoint not set in code exception!
Just found this worked for me, when connecting to test runs...
Disable background discovery of test methods: (Available in VS2008 SP1 only)
1. Select the Tools | Options | Test Tools | Test Project menu option.
2. On the Test Project dialog (figure 1.1), select the “Disable background discover of test methods” checkbox option and press ok.
This will disable the background discovery of test methods and will dramatically speed up the IDE. However, since this is global option, this will disable the test method discovery on every project. If you wish to re-enable the discovery, simply load the Test Project dialog again and deselect the “Disable background discover of test methods” checkbox.
Also, another tip is to set the option "Double-clicking a failed or inconclusive unit test result displays the point of failure in the test"
Add this to the configuration for the test
<TestRunConfiguration ...>
...
<ExecutionThread apartmentState="MTA" />
</TestRunConfiguration>
To check the threading model used, add the following line to your test(s):
[TestMethod]
public void YourTest()
{
System.Diagnostics.Debug.WriteLine(System.Threading.Thread.CurrentThread.GetApartmentState().ToString());
// TODO: Add test logic here
}
Use the following powershell script to find the last users to login to a box since a given date, in this case the 21st April 2022 at 12pm un...
