What is not done during unit testing?
Not every test you could conceivably write qualifies as a unit test. If you write code that stuffs things into a database or that reads a file from disk, you have not written a unit test. Unit tests don’t deal with their environment and with external systems to the codebase.
Why do you need unit test?
Unit testing ensures that all code meets quality standards before it’s deployed. This ensures a reliable engineering environment where quality is paramount. Over the course of the product development life cycle, unit testing saves time and money, and helps developers write better code, more efficiently.
What should one check for null if he does not?
Think of a search results on Stack Exchange in different groups (users, comments, questions). The method could check for null and abort the processing of users (which due to a bug is null) but return the “comments” and “questions” sections. The page would continue working except that the “users” section will be missing (which is a bug).
How to check for Nulls in.net code?
Checking for nulls doesn’t imply conditional statements. If you worry that null checking makes your code less readable, then you may want to consider .NET code contracts. Consider installing ReSharper (or similar) to search your code for missing null reference checks
What does it mean when a null is passed to a method?
You are just hiding an error. The error might be that something has changed in the code and null is now an expected value, or there is some other error and the wrong ID is passed to the method. On the other hand, checking for nulls may be a good habit in general.
Can a null ref cause an exception in Java?
As you know, in Java or C# things are different, using a null ref without checking for null will cause an exception, thus the error will not be secretly hidden as long as you don’t ignore it on the calling side. So in most cases, checking explicitly for null does not make much sense and overcomplicates the code more than necessary.