Software testing or Mobile APP testing is a complex process. The final product is almost like the perfect dish, A dish that is that accompanies a lot of flavors till its perfect.Software testing takes many forms, it should occur at multiple stages in a development project, and it varies in its activities . Evolution of technology has made a big difference as these practices have also changed .

Let’s explore the various software testing strategies and methods available today, and explain why you might use one approach over another in a given context. Today we are going to specifically take into consideration Unit Testing .


According to a blog by  Adrian Hall – Unit testing tests individual parts of your code for correctness, usually using an automated test suite. A good unit test assures you that the functionality that you are expecting out of the unit (your code; usually a single method) is correct. He adds that  A good unit test compromises of the following.

A good unit test is :

  • Repeatable — you can run it several times and it produces the same result.
  • Quick — you don’t want it to interrupt the flow of your work.
  • Readable — you can understand what the test is doing.
  • Independent — you can run a single test from a suite.
  • Comprehensive — you have enough tests to test all the main cases and corner cases of inputs and cover all code paths.

 Unit test suite augments the developer documentation for your app. This helps new developers come up to speed by describing the functionality of specific methods. When coupled with good code coverage, a unit test acts as a safeguard against regressions . Unit tests are important for anything that does not produce a UI.

Today there are test frameworks such as JUnit, TestNG, RayGun, and so on, or cloud-based tools such as Sauce Labs, to help formalize and automate your unit tests. Whereas unit tests were once little more than a check mark in a to-do list, today they execute continuously as code is written, using sophisticated tools. This can go a long way towards building confidence in terms of software quality, starting from an early stage of development.

Unit tests are a very powerful tool to help developers avoid bugs and spot them quickly when they do appear. They help you maintain your code, but at the same time they need maintenance as well. The big problem of many projects is tests that no one uses, and to avoid it you need to stick to some rules.

Your tests must:

  • be reliable;
  • not depend on the environment they’re run in;
  • be easy to maintain;
  • be easy to read and understand (even a beginner QA has to be able to understand what’s going on);
  • have a standard naming convention;
  • and be launched regularly and be automated
    This is just one of the ingredients to a perfect product launch. My following blogs will give you an understanding of more such testing methodologies.