There’s some debate as to whether or not you should test private members in a class. Generally, I fall in to the “if it makes sense to test it, test it” camp. If there’s a private method that is only accessible by a hard-to-mock series of callbacks or events, I would much rather write a … [Read more…]
In a previous post I talked about testing Observables in your Angular code. This is pretty common, because HttpClient sends back an Observable<T> – so if you want to spyOn that function, you’ll need to figure out how to return an Observable. I’ve been bouncing around a couple of projects/repos recently, and it turns out … [Read more…]
Recently I was updating and fixing some existing unit tests after doing a (rather large) overhaul of code.The unit test previously needed to wait for an asynchronous callback to finish before continuing, something like this: Note the optional done parameter provided to beforeEach. This is a void function that signals Jasmine that the callback is … [Read more…]
In Jasmine, you can expect an object toBe another object. However, this will check to see if the two arrays point to the same reference object. In other words, it will check to see if the arrays point to the same memory address. Produces this not-very-helpful error message: Expected [ 42, ‘Forty-Two’ ] to be … [Read more…]
Recently I had a problem where in an Angular unit test where I had an object that was being initialized in ngOnInit from a service. As far as I could tell, everything should be working, but the test would fail because I was trying to set a property on the object before it had finished … [Read more…]
I find that writing unit tests in JavaScript kind of sucks, so this post will (hopefully) serve as a cheat sheet of all the stuff I keep looking up. As such, it will be updated as I learn new stuffs. How To: scope test run to specific tests Remember to set it back before you … [Read more…]
In the last post I talked about using and extending IActionResult to return your preferred HttpStatus code in your ASP.NET MVC controllers. But how do you write unit tests that make sure that you’re returning what you expect? Your controllers will return one of these: IActionResult There’s nothing on this interface that you can easily … [Read more…]
Unit testing can be annoying. Sometimes it feels like setting up a delicate house of cards in just the right way and hoping that nobody opens a window to let a breeze knock the whole thing over. If you’re using inversion of control (and you should be), its a little easier because you can use … [Read more…]
In the last blog post I talked about how to use Moq’s built in SetupSequence to create a “chain” of actions to execute for subsequent calls of the same mocked method. This works great for the simple case, but falls down when you have to do something a little more complicated like, say, issue a … [Read more…]
Say that you’re unit testing and you want a mocked interface to behave differently for different calls to the same method. I was trying to test a TCP listener loop – a TcpListener waits for an incoming connection, does something with it, and then goes back to listening. In essence, the loop will last until … [Read more…]