I noticed you don't have a browser with Microphone Support. If you would like to use the microphone you will need to use Chrome for the time being. Until then you may use the chat box below.
|No Mic? No problem, type your message below|
Node is one of the premier frameworks for microservice architecture today. The microservice pattern allows developers to compartmentalize individual components of a larger application infrastructure. Because each component runs independently, you can upgrade or modify components without impacting the larger application. Each component exposes an interface to external consumers who are blind to any internal logic the service does. One of the challenges of working in a microservice environment is the process of one service finding another to call it. Each service runs as an application and has an address that the calling service must find before it can call any functions on its interface. Seneca is a microservice toolkit that helps alleviate this headache by providing the foundations of a microservice application. Seneca markets itself as a toolkit for Node that leaves you free to worry about the business logic in your application.
There is often a lot of confusion and doubt regarding unit testing when discussing it with stakeholders and clients. Unit testing sometimes sounds the way flossing does to a child, “I already brush my teeth, why do I need to do this?” Suggesting unit testing often sounds like an unnecessary expense for people who consider their testing methods and user acceptance testing strong enough. But Unit Tests are a very powerful tool and are simpler than you may think. In this article, we will take a look at unit testing and what tools are available in DotNet such as Microsoft.VisualStudio.TestTools and Moq.