mstest

I have a number of test classes and methods that copy a particular directory like so: [TestClass, DeploymentItem("LanguageData", "LanguageData")] public class OcrTests { [TestMethod] public void Can_Capture_Field() { // some code that expects the LanguageData directory to be in the test results Out directory } // etc } [TestClass] public class OcrBuilderTests { [TestMethod, DeploymentItem("LanguageData", "LanguageData")] public void Can_Build_Specific_Ocr_Engine_Implementation() { // some more code that expects the LanguageData directory to be in the test results Out directory } // etc } Those

For unit testing you shouldn't test private methods, yes, but for integration tests (using a unit testing framework like MSTest or NUnit) I would very much like to run the internal API calls against a test url, to make sure the current code works when the third party API vendor changes their backend. Given the complexity of the system (stupid API's have hundreds of parameters) I have hidden most of it behind interfaces and IoC, with the API helper class completely internal to our data layer library. I don't want to change this because it used to be public and we found the odd developer new to

I'm trying to use MSTest to write unit tests for methods in my MainWindow class in my WPF application. However, I get the following exception: System.Windows.Markup.XamlParseException: 'Provide value on 'System.Windows.StaticResourceExtension' threw an exception.' Line number '127' and line position '32'. ---> System.Exception: Cannot find resource named 'verticalLineStyle'. Resource names are case sensitive. verticalLineStyle is found in a ResourceDictionary that is included in App.xaml . I have no need of this style to test the method I'm trying to test, but I can't get past this. I'm just

We are in the middle of developing a new CRM, and it uses both WPF for local users, and a Windows Universal App (Store App) for the users in the field. The basic flow is this Customer calls in and gets scheduled on a field user in WPF app. Field user goes on service call and updates on Surface through Universal App. Customer gets billed from the WPF App. All the modules are in place and working, but I do not seem to be able to integration test the entire project flow due to the different Project Types. What I need to be able to do is add a reference to my Universal App in the unit test for my

Is it possible to access the MSTest TestContext from within a SpecFlow (1.7.1) step binding class? In the generated code of a feature file there is a method FeatureSetup which takes the TestContext as an argument but apparently doesn't do anything with it. I found a way to pass parameters to TestContext and then access them from SpecFlow. By adding a [TestClass] which has a TestContext property and marking its AssemblyInit() method as [AssemblyInitialize] so it gets initialized early before runnig the tests and MSTest will be able to populate the TestContext. { [TestClass] public class