I’ve got it. And yes, it’s a bug. The problem is that there are two levels of string.Format going on here. The first level of formatting is something like: string template = string.Format(“Expected: {0}; Actual: {1}; Message: {2}”, expected, actual, message); Then we use string.Format with the parameters you’ve supplied: string finalMessage = string.Format(template, parameters); … Read more
DeploymentItem is a bit of a mess. Each file in your solution will have a “Copy To Output Folder” setting in VS.NET. You need this to be “Copy Always” (or similar) in order to get the files into the output folder. Check that you’ve got this set for the new files. If you don’t have … Read more
A method annotated with [TestInitialize] is run before each test. Likewise [TestCleanup] is after each test. [ClassInitialize] and [ClassCleanup] are run before and after the ‘suite’ of tests inside the TestClass.
This message is caused by an exception on a thread different from the executing test thread. All answers so far boil down to this simple explanation. It is a known bug in Visual Studio not to display any sensible information in that case. Visual Studio’s test runner totally chokes if a thread other than the … Read more
Your unit test will fail anyway if an exception is thrown – you don’t need to put in a special assert. This is one of the few scenarios where you will see unit tests with no assertions at all – the test will implicitly fail if an exception is raised. However, if you really did … Read more
use a DeploymentItem attribute using System; using System.IO; using Microsoft.VisualStudio.TestTools.UnitTesting; using CarMaker; namespace DeploymentTest { [TestClass] public class UnitTest1 { [TestMethod()] [DeploymentItem(“testFile1.xml”)] public void ConstructorTest() { string file = “testFile1.xml”; Assert.IsTrue(File.Exists(file), “deployment failed: ” + file + ” did not get deployed”); } } }
The following call will clear the in-memory datastore. _context.Database.EnsureDeleted();
It is possible to run mstest.exe without visual studio. Download one of the Agents for Visual Studio ISO’s below and install the Test Agent on the server: Visual Studio 2019 Visual Studio 2017 (127MB disk space, less than that for download) Visual Studio 2015 and older: visit https://www.visualstudio.com/vs/older-downloads/ and follow the instructions This installs everything … Read more
FWIW, you can use the AssemblyInitialize attribute to run code before all unit tests in an assembly executes: [TestClass] public class SetupAssemblyInitializer { [AssemblyInitialize] public static void AssemblyInit(TestContext context) { // Initalization code goes here } } If you have more than one unit test assembly, I’m not aware of anything that encompasses more than … Read more
The Console output is not appearing is because the backend code is not running in the context of the test. You’re probably better off using Trace.WriteLine (In System.Diagnostics) and then adding a trace listener which writes to a file. This topic from MSDN shows a way of doing this. According to Marty Neal’s and Dave … Read more