Only Visual Studio 2015 Enterprise has code coverage built-in. See the feature matrix for details. You can use the OpenCover.UI extension for code coverage check inside Visual Studio. It supports MSTest, nUnit, and xUnit. The new version can be downloaded from here (release notes).
In my experience, there are a couple of factors involved in this: Management doesn’t really understand what unit testing really is, or why it has real intrinsic value to them. Management tends to be more concerned with rapid product delivery, and (incorrectly) sees unit testing as counterproductive to that goal. There’s a misperception that testing … Read more
Test-driven developers should feel right at home in functional languages like F#: small functions that give deterministically repeatable results lend themselves perfectly to unit tests. There are also capabilities in the F# language that facilitate writing tests. Take, for example, Object Expressions. You can very easily write fakes for functions that take as their input … Read more
Your unit test class usually needs a few things to manage a shared resource for a group of test methods. And in Kotlin you can use @BeforeClass and @AfterClass not in the test class, but rather within its companion object along with the @JvmStatic annotation. The structure of a test class would look like: class … Read more
This is one of the hardest things to do. Getting your people to get it. Sometimes one of the best ways to help junior level programmers ‘get it’ and learn the right techniques from the seniors is to do a bit of pair programming. Try this: on an upcoming project, pair the junior guy up … Read more
QUnit is very easy to get started with, as you only need to include two files and a little bit of markup, then you can start writing tests. Jasmine strength, afaik is its BDD-style syntax, if that is something that you prefer (probably not a selling point for you) and tight integration into Ruby/Rails tools. … Read more
You need to store your mocked component in a variable with a name prefixed by “mock”. This solution is based on the Note at the end of the error message I was getting. Note: This is a precaution to guard against uninitialized mock variables. If it is ensured that the mock is required lazily, variable … Read more
If the team is floundering at implementing TDD, but they weren’t creating any Unit Tests before…then start them off by creating Unit Tests after their code is written. Even Unit tests written after the code are better than no Unit Tests at all! Once they’re proficient at Unit Testing (and everything that comes with it), … Read more
You can do this using Mockito to have the mock return the correct params, verify they were indeed called (optionally specify number of times), write the ‘result’ and verify it’s correct. import static org.junit.Assert.*; import static org.mockito.Mockito.*; import java.io.*; import javax.servlet.http.*; import org.apache.commons.io.FileUtils; import org.junit.Test; public class TestMyServlet extends Mockito{ @Test public void testServlet() throws … Read more
I think what you want is: input.simulate(‘change’, { target: { value: ‘Hello’ } }) Here’s my source. You shouldn’t need to use render() anywhere to set the value. And just FYI, you are using two different render()‘s. The one in your first code block is from Enzyme, and is a method on the wraper object … Read more