You always end up coming to it. It's inevitable. It cannot be helped. Yep, it's time to write a custom validator for your shiny new Angular application. So how do you do that in Angular 4? And more importantly: how do you test it?
Being the test-driven developer that you are, you are writing a Jasmine test for your AngularJS factory function, which returns a promise generated by our beloved $q. You know how to test an asynchronous response with Jasmine. You confidently run the test and... bam, you get an error message "Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL"
It's an accepted trend nowadays: according to many TDD and BDD are useful tools with many advantages, and to others they are not. In this post I will not start that old debate again. I will however expose to you one great, possibly overlooked advantage in having extensive test/behavior/specifications coverage: a better team collaboration.
Do you get "Too many open files" issues or "java.lang.NoSuchMethodError: com.google.common.util.concurrent.RateLimiter.acquire(I)V" errors when running your CassandraUnit tests? Do you feel like your tests could get a speed boost? Then read this...
Looking for something to help you with testing your Cassandra-related methods? Then CassandraUnit might be what you're looking for! This article will provide you with a quick overview of CassandraUnit's features, and a practical example on how to set it up for your testing needs.
So you want to validate the data sent to your application's REST services? Nowadays you can quite easily do that using Spring and the Bean Validation API. And to help you test that validation process, how about bringing in Spring Boot to programmatically start your application and run your tests against it?
After last week's music-related post, I go back to IT and, in my humble opinion, to one of the major plagues of our industry: the transcription and transmission of the knowledge related to the software we deliver.