An unexpected exception is a test failure, so you neither need nor want to catch one. @Test public void canConvertStringsToDecimals() { String str = “1.234”; Assert.assertEquals(1.234, service.convert(str), 1.0e-4); } Until service does not throw an IllegalArgumentException because str has a decimal point in it, that will be a simple test failure. An expected exception should … Read more
Classic example which demonstrates that if you cannot unit test a particular component, REFACTOR it! This is why I love what any mocking framework enforces you to do – write decoupled code. In your example, the ProductBusiness class is tightly coupled with the ProductDataAccess class. You could decouple it using (like most of the answers … Read more
A tenet of unit-testing is that each test should be independent of all others. If in your case the code in testTestA must come before testTestB, then you could combine both into one test: def testTestA_and_TestB(self): # test code from testTestA … # test code from testTestB or, perhaps better would be def TestA(self): # … Read more
If you have Babel in your stack, you can fix this in the right way using babel-jest Just do npm i –save-dev babel-jest and in your jest settings file add: “moduleNameMapper”: { “^.+\\.(css|less|scss)$”: “babel-jest” }
Support for Pytest in Visual Studio has been added on Visual Studio 2019 (16.3 Preview 2) You have to change your project’s test framework by right-clicking it and going to Properties -> Test You can add a pytest.ini to your project to configure pytest further. More info from MS themselves: https://devblogs.microsoft.com/python/whats-new-for-python-in-visual-studio-16-3-preview-2/
Look at VSTest.Console.EXE they added this for CodedUI tests. Seems to have more functionality. https://msdn.microsoft.com/en-us/library/jj155800.aspx in C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow directory.
One way to do it would be to put the functions you don’t want tested in a separate go file, and use a build tag to keep it from being included during tests. For example, I do this sometimes with applications where I have a main.go file with the main function, maybe a usage function, … Read more
The common causes of tests failing at the coverage stage are PIT picking up tests not included/are excluded in the normal test config Tests rely on an environment variable or other property set in the test config, but not set in the pitest config Tests have a hidden order dependency that is not revealed during … Read more