[Unit Testing] Getting Started with Unit Testing

Unit Testing:

  • Is a software development process in which the smallest testable parts of an application are individually and independently tested.
  • Simply verifies that individual units of code (mostly functions) work as expected.
  • Is a component of test-driven development (TDD).
  • Usually performed by the developer.
  • Performed using White Box Testing method.
  • Is meant to give the developer more confidence and trust in the code.
  • Encourages modularity - write programs that do one thing, and do it well! (Single Responsibility Principal)
  • Involves faking dependencies and methods in order to isolate the scope of the System Under Test (SUT)

Simple Example

The most simple example is testing the result of a method is within our expectation. For example, we we have a combineNumbers method below:

To test this, we simply compare the result of this method with our expected  result.


When you run the tests, you will be informed that these tests have passed.

When to do Unit Testing?

This should be done as often as possible.
In the bigger picture of unit testing, this should be done before we do Integration Testing.




Benefits

  • Anyone can look at the unit test and gain a basic understanding of the unit API, including the specifications and use case; documentation purpose.
  • Design Aid: gives you a clearer perspectie on the ideal API design.
  • Allows programmers to refactor code at a later date, and make sure the module still works correctly. (ie. Regression Testing and Continuous Delivery Aid)
  • Can test parts of the project without waiting for others to be completed.
  • Increases confidence in changing/maintaining code.
  • Force code to be modular; making code easier to re-use.
  • Cost of fixing detect during unit testing is lesser in comparison to detects found at higher levels; compare cost (time, effort, destruction, humiliation) of defect found in acceptance test, or during production.
  • Debugging is easy; you have a smaller scope to look at.
  • Codes are more reliable. 

Limitations

  • Can't be expected to catch every error in the program.
  • Can't catch integration errors or broad system level errors.

Resources

https://searchsoftwarequality.techtarget.com/definition/unit-testing
https://medium.com/@lazlojuly/how-to-get-started-with-unit-testing-part-1-7f490bbf560a
http://softwaretestingfundamentals.com/unit-testing/
https://www.guru99.com/unit-testing-guide.html
https://medium.com/javascript-scene/what-every-unit-test-needs-f6cd34d9836d

Comments

Post a Comment

Popular posts from this blog

[Redis] Redis Cluster vs Redis Sentinel

1) In-Depth Guides to Redis Cluster and Sentinel For more in-depth explanation for Redis Cluster or Redis Sentinel, please read my other posts: Sentinel:  https://notafraidofwong.blogspot.com/2019/05/redis-redis-sentinel.html Cluster:  https://notafraidofwong.blogspot.com/2019/05/redis-redis-cluster.html 2) Deciding between Redis Sentinel and Redis Cluster Similarities : Both solutions provide high availability for your system. 2.1) Redis Cluster 2.1.1) Pros Shards data across multiple nodes Has replication support Has built-in failover of master 2.1.2) Cons Not every library supports it May not be as robust (yet) as Standalone Redis or Sentinel Setup and maintenance is more complicated 2.2) Redis Sentinel 2.2.1) Pros Automatically selects new master in case of failure Easy to setup, (seems) easy to maintain 2.2.2) Cons No data sharding; master might be overutilized. Another distributed system to maintain. 3) So how do I dec...
Read more

[Unit Testing] Test Doubles (Stubs, Mocks....etc)

Image
In unit testing, isolation is key. The goal of unit testing is to test individual components, and not an entire system . The class/object/function you are testing is System Under Test (SUT) , and the other components of the system are Collaborators or Dependencies. Test Double  is a generic term for any kind of 'pretend' object used in place of a real object for testing purposes.  There are several types of Testing Doubles. We will start with: Fake Stub Mock Command Queries Mocks vs Stubs And then: Dummy Spies Spies vs Mocks I) Basic Testing Doubles a) Fake Fake are objects that have working implementations, but not same as production one. Usually they take some shortcut and have simplified version of production code. Note that Fake is a generic term - that can point to anything; usually mock and stubs. An example of this is an in-memory implementation of a database. This fake implementation will not access the actual database, but will ...
Read more

[Node.js] Pending HTTP requests lead to unresponsive nodeJS

This is a recap conclusion to the potential problems of a NodeJS program I worked on previously. The program simulates thousands of clients navigating a website by sending thousands of http requests to a given API . The idea is to load test a particular API to make sure they can handle high traffic. Because we are simulating clients, it's important to keep track of the state of the simulated client as well. The problem with this program is it is buggy and becomes unresponsive from time to time (the only solution is to restart it). The problem was fixed by re-writing the entire program in Java, but it was regretful that I never had enough time to find the exact reason the nodeJS version of it failed. The following are potential causes I suspect: 1. Exceptions The NodeJS program was not written very neatly and stacked callbacks on top of callbacks on top of callbacks. This made it very difficult to keep track of exceptions and unexpected http responses are prone to happen. So...
Read more