This blog expressed my technology vision and based on my professional experience in the Software industry.
Contains Knowledge base, Tutorials, Code examples and Best practices of frequently Software design issues.
To really understand the objective of “Static Testing” you must first understand the crucial point of finding bugs early as possible and the direct impact it has on the entire procedure of Requirements, Design, Developing and Testing in the factors of time and money.
Now, you all know that every bug that found has the three usual steps of the investigation, fixing and testing, this procedure is a great example of how the company can lose time and money, but the real problem occurs when those bugs failed to be found in earlier stages, the reason? The reason is basic and explained in one simple sentence “The later the bug is found, the company losses increased”, as a result, finding bugs earlier as possible has great importance, especially today in the software market that contain multiple competitors that doesn’t allow you to late in the product delivery.
After the problem explained, it’s now the time to discuss about the solution that called “Static Testing”, static testing allow us to make our tests on the earlier stages of the software life cycle (Requirements and specification), the main objective to use this testing method is to find the bugs on the earlier point of the software life cycle and remove those bugs on future stages.
Objectives of dynamic testing
The main objectives of this testing method is to find the software bugs while the code executed, during those tests we make sure that our application behaves based on the predefined requirements and specifications.