Old World vs. New World

As software has become increasingly more complex and the demands placed on the test discipline have escalated, it is clear that the legacy approaches for testing software are not always adequate.  Sometimes test teams get caught up in performing the same types of tests and/or taking the same types of approaches not because those things…

0

Code Inspection for SDETs, Part II

In part I of this series, we looked at some of the benefits of the SDET discipline being fully plugged into the code inspection pipeline.  These benefits include such outcomes as pushing quality upstream and raising SDET awareness of the code that is being tested.  Plus, it’s fun!  J   Now we will share the…

0

Code Inspection for SDETs, part I

(Note for those unfamiliar with the acronym, SDET stands for Software Design Engineer in Test.  In simple terms an SDET is an engineer who develops code to test software) Code inspection has historically been a “high-yield for low cost” bug-prevention or bug-detection approach.  This is especially true when used as part of formal code review…

3