Let’s talk about a recipe first…

Do you love Omelette? (definitely…it might be your favorite breakfast)
Let’s prepare it…so you need some ingredients like… Eggs, Milk, Bacon, cheese, tomato, onion, salt. Few things you may want to verify, inspect, evaluate, and test before preparing the Omelette.

• How many eggs? Are they fresh?
• What kind of milk? How much? Is it spoiled?
• Is the bowl (for scrambling) clean?
• Is the frying pan heated enough when you put bacon in it?

And it goes on….you check, evaluate, verify, taste the ingredients from your end to prepare a perfect recipe of Omelette. When you’re doing this you are testing the individual ingredients, making the observations, and making judgments while being in the process of creating the product but note that you’re testing the components, not the product. If you cook the Omellete without giving attention to the process (and components) and later if you taste the final recipe, you may end up with preparing a bad recipe. The reason could be spoiled milk, dirty bowl, or anything else. This can create a serious health issue.

The same things happen in software development. In unit testing, individual components or each part of the program are tested during the development phase to ensure that they all are working correctly. A lot of developers hate to write the unit test but performing units can detect a lot of issues in the initial phase of the software development process. These issues can be rectified earlier before it becomes more problematic at the production level. Let’s talk about Unit testing in detail and why developers should learn it.

#gblog #software engineering #software testing