Return to Answer

“Quality is free, but only to those who are willing to pay heavily for it.” – T. DeMarco and T. Lister

As being someone who is doing test reviews from over a decade, would add couple of points on 'why' and 'what' on test reviews:

• Clarity: First of all, a test should actually test what it is supposed to test only and report it clearly.Each test should be very clear on what exactly it is testing and precisely what not.

• Readable : The code should be readable; it should be understandable just by reading it, even without any comments.If somebody has to explain it , it is not been designed correctly.

• Maintainable:In the event of bug fixing/functional change in the AUT, it should be easily changeable multiple times over a period of time. If one moderate change in application requires big changes in multiple places in automation , it is not efficient(DRY).

“Quality is free, but only to those who are willing to pay heavily for it.” – T. DeMarco and T. Lister

Being someone who has been doing test reviews from over a decade, would add couple of points on 'why' and 'what' on test reviews:

• Clarity: First of all, a test should actually test what it is supposed to test only and report it clearly.Each test should be very clear on what exactly it is testing and precisely what not.

• Readable : The code should be readable; it should be understandable just by reading it, even without any comments.If somebody has to explain it , it is not been designed correctly.

• Maintainable:In the event of bug fixing/functional change in the AUT, it should be easily changeable multiple times over a period of time. If one moderate change in application requires big changes in multiple places in automation , it is not efficient(DRY).

“Quality is free, but only to those who are willing to pay heavily for it.” – T. DeMarco and T. Lister

As being someone who is doing test reviews from over a decade, would add couple of points on 'why' and 'what' on test reviews:

• Clarity: First of all, it should actually test what it is supposed to test only and report it clearly.Each test should be very clear on what it is testing , it should pass or fail only for the reasons for which it has been designed.

• Readable : The code should be readable; it should be understandable just by reading it, even without any comments.If somebody has to explain it , it is not been designed correctly.

• Maintainable:In the event of bug fixing/functional change in the AUT, it should be easily changeable multiple times over a period of time. If one moderate change in application requires big changes in multiple places in automation , it is not efficient(DRY).

“Quality is free, but only to those who are willing to pay heavily for it.” – T. DeMarco and T. Lister

As being someone who is doing test reviews from over a decade, would add couple of points on 'why' and 'what' on test reviews:

• Clarity: First of all, a test should actually test what it is supposed to test only and report it clearly.Each test should be very clear on what exactly it is testing and precisely what not.

• Readable : The code should be readable; it should be understandable just by reading it, even without any comments.If somebody has to explain it , it is not been designed correctly.

• Maintainable:In the event of bug fixing/functional change in the AUT, it should be easily changeable multiple times over a period of time. If one moderate change in application requires big changes in multiple places in automation , it is not efficient(DRY).

“Quality is free, but only to those who are willing to pay heavily for it.” – T. DeMarco and T. Lister

As being someone who is doing test reviews from over a decade, would add couple of points on 'why' and 'what' on test reviews:

• Clarity: First of all, it should actually test what it is supposed to test only and report it clearly.Each test should be very clear on what it is testing , it should pass or fail only for one and only reason for which it has been designed.

• Readable : The code should be readable; it should be understandable just by reading it, even without any comments.If somebody has to explain it , it is not been designed correctly.

• Maintainable:In the event of bug fixing/functional change in the AUT, it should be easily changeable multiple times over a period of time. If one moderate change in application requires big changes in multiple places in automation , it is not efficient(DRY).

“Quality is free, but only to those who are willing to pay heavily for it.” – T. DeMarco and T. Lister

As being someone who is doing test reviews from over a decade, would add couple of points on 'why' and 'what' on test reviews:

• Clarity: First of all, it should actually test what it is supposed to test only and report it clearly.Each test should be very clear on what it is testing , it should pass or fail only for the reasons for which it has been designed.

• Readable : The code should be readable; it should be understandable just by reading it, even without any comments.If somebody has to explain it , it is not been designed correctly.

• Maintainable:In the event of bug fixing/functional change in the AUT, it should be easily changeable multiple times over a period of time. If one moderate change in application requires big changes in multiple places in automation , it is not efficient(DRY).