Why should we get used to Static Testing?

Emre
4 min readJun 6, 2021

Does prolonging a software development process bring profit or loss? It depends on how you approach the software development process. Unfortunately, many software companies are not able to advance the steps of the software life cycle healthily. This situation, unfortunately, damages the customer both in time and money at the point of the software construction in the next processes.

The reason for the problem arises from the failure to act according to the rules of the software life cycle during the initial phase of the project. Throughout the software lifecycle process, there should be healthy mutual communication between the customer and the software company. Otherwise, misunderstandings or incomplete explanations occur in the software application. However, this situation causes more difficult results to compensate in the next process.

At this point, the most important step to be taken into consideration is the construction of health information exchange in the requirements and design process, which are the first two stages of the software development process, and examinations with various test methods.

We use the Static Test method for this. In this article, I will explain the process, methods, and benefits of the Static Test method for you.

Static Test: It is a step-by-step review of the entire project files manually by the project managers, without running any code. Static tests are done before moving to dynamic testing.

In this way, as we mentioned above, possible obstacles can be avoided with cheaper and solvable methods.

Thanks to static testing techniques;

  • Increases productivity in the development process, resulting in better quality and healthier products.
  • Requirements are clarified and missing points are improved. Possible problems in the development process are avoided.
  • Savings in Time and Currency.
  • Less time and fewer bugs in the automation and manual testing phase.
  • A more effective communication process takes place within the team.

We can summarise what we have counted with 3 main headings. These,

1- Productivity

2-Defect prevention

3- Cost Savings

Static testing improves productivity, prevents defects, and reduces costs.

So How is this Static Testing process done?

1-Informal Review (Pass around):

It is a form of testing in which simple revisions are made on the document by meeting with the team leader in an unplanned manner without any preliminary preparation.

The aim here is to recognize the project and make improvements by eliminating obvious logic errors. In addition, a date can be set for the next test phase.

Photo link: https://unsplash.com/photos/6awfTPLGaCE?utm_source=unsplash&utm_medium=referral&utm_content=creditShareLink
Taken by @myleon

2- Walkthrough Review:

After the completion of the feedback given in the Informal Review process, the product file is reviewed on the specified date without any preliminary preparation. The examinations made in the walkthrough method are recorded in the form of minutes.

The main purpose here is; learning, understanding, and finding faults. It is also to build a healthier process for the next stage.

Photo Link: https://unsplash.com/photos/Lks7vei-eAg
Photo Taken by Charles Deluvio

3- Inspection Review:

It is the process where the final review is done by a small group before starting the development process. The Inspection Review process requires serious discipline and preparation. Because according to the result, the developers will create the project.

Participants should come to this meeting prepared in advance to review the file and present their views. Organized in a planned and prepared manner, this inspection review is managed by a competent moderator.

Certain parameters and metrics are followed at the meeting. The review process is recorded in writing and video. The main purpose here is to find existing errors and make necessary improvements.

After these 3 stages, the product file is transferred to the developers and the coding process begins.

Remember! the developers will build the result of the file you prepared and presented. The more careful you are here, the more healthy and less costly you will create a product.

In my next post, I will review Dynamic Testing Techniques.

Thanks so much for reading this far. If you want more of these and similar articles to come, all you have to do is give a like.

Thanks.

Emre Ozudogru.

Instagram: yunusozudogruu

--

--

Emre

Do not compare yourself with others. Compare yourself today to yourself tomorrow!