Friday, March 28, 2014

Static Testing

Static testing is all operations performed by testers and developers without a direct relation or need in the actual code of the software (non-runtime environments), and in other words we can simply say that this kind of
test performed while the code is not executed in one way or another (code execution is not involved in any way...), great examples for static testing: 

  • Review/inspection made to software requirements (Specs).
  • Review/inspection made to software technical design (DDD).
  • Review/inspection made to the user manual that come along with the software and going to be used by the client as guidelines to how to use the software.
  • Review/inspection made to developers code.
  • Review/inspection the test documentations (STD, STP, ATP).
  • Review/inspection made to development and testing strategies.
  • Review/inspection made to the testing end results.
  • Review/inspection made to project timelines and progress.
  • Examination made by developers to their own code with different manipulations to reduce defects in the actual run time (White Box testing anyone..?).
  • Walk-through of the tested software, this method will educate your testers, and benefit with the testing quality.

Based on the list above, I’m positively sure that you understand that executing a great ‘Static’ testing is one of the main keys for success in any given software life cycle, the following list will provide a short list of benefits you gain from this type of testing:

Improve the communication with the company clients – great communication and inspection for your client requests is the key, while examining the requirements, you can create a great collaboration that in the end will lead to great results suggest: 

  • Understanding the requirements in 100%, no surprises during the engineering process.
  • Understand the client environment and the specific site architecture.
  • Understand the user expectations from the software and how he wants to use it, by accomplished this simple task you can design effective test cases and reduce the once that not relevant.


Time and money is the key – great static testing will contribute to reduce the costs and engineering process that contribute to the company “success” factor.

Improve productivity without incising the timelines – when you understand your tasks, you can develop and test in greater efficiency. Therefore, you improve your productivity and reduce the delay you probably had without the use of static testing.

Reduce the number of bugs – static testing is the key to doing so, if executed with perfection I can ensure that stupid bugs will not be part from your testing cycle (Although your developer may do some magic if he failed to sleep at night before..).

No comments:

Post a Comment

My Presentations