TL;DR your Test Classes must be public (but your Test Methods can be private and/or static) For reasons of efficiency, the xUnit authors have opted to not use BindingFlags.NonPublic when searching for Test Classes in the runner (the MSIL metadata tables don’t index private(/internal) classes to the same degree hence there is a significant performance … Read more
you need not use PhantomJS as an alternative to Selenium. Selenium includes a PhantomJS webdriver class, which rides on the GhostDriver platform. Simply install the PhantomJS binary to your machine. in python, you can then use: from selenium import webdriver dr = webdriver.PhantomJS() and voila.
A prettier way to do this, is to export both your plain component, and the component wrapped in connect. The named export would be the component, the default is the wrapped component: export class Sample extends Component { render() { let { verification } = this.props; return ( <h3>This is my awesome component.</h3> ); } … Read more
A summary from the answers by jdehaan and Eric Brown, as well as this question (see also this question): N.B. These solutions may affect other error reporting as well, e.g. failure to load a DLL or open a file. Option 1: Disable globally Works globally on the entire user account or machine, which can be … Read more
In my case, it turned out that I simply had to upgrade my test adapters and test framework. Done. Example using the NuGet Package Manager:
To my surprise, clearing temp files located in the %TEMP% directory resolved the issue for me. Note: This path is generally at C:\Users\(yourusername)\AppData\Local\Temp As @Warren-P included, you can navigate to the temp folder by putting in %temp% in Start Menu, or launch “File Explorer” and enter %temp% in the address bar.
[TestMethod] Test1Row1 { Test1(1,4,5); } [TestMethod] Test1Row2 { Test1(1,7,8); } private Test1(int i, int j, int k) { //all code and assertions in here }
My approach towards this is heavily biased on the Growing Object-Oriented Software Guided by Tests (GOOS) book that I just read, but it’s the best that I know of today. Specifically: Create an interface to abstract away the file system from your code. Mock it where this class is needed as a collaborator/dependency. This keeps … Read more
No, I don’t think of testing private or protected methods. The private and protected methods of a class aren’t part of the public interface, so they don’t expose public behavior. Generally these methods are created by refactorings you apply after you’ve made your test turn green. So these private methods are tested implicitly by the … Read more
Unit test: Specify and test one point of the contract of single method of a class. This should have a very narrow and well defined scope. Complex dependencies and interactions to the outside world are stubbed or mocked. Integration test: Test the correct inter-operation of multiple subsystems. There is whole spectrum there, from testing integration … Read more