No best practices

No best practices

 

Chen nengtech

2007-7-24

 

Article 1 of the seven basic principles of context-driven testing:

The value of any practice depends on its context.

The value of any practice depends on the context of its application.

 

For this principle, James Bach made an in-depth analysis in "no best practices: how to think about methodology.

 

There is no best practice.

Not most people think that good is best practice.

Nor can it be because an authoritative person you respect says that he prefers to do so as a best practice.

Best practices are irrelevant to popularity. Best practices are technical issues and are related to the application context.

Some practices can be called good practices or useful practices in some specific contexts in some regions.

 

For example, is there a so-called best practice for determining the code freezing stage?

Some people will think that it should be frozen early, which will help reduce the test pressure and reduce the possibility of new bugs. However, the objection is that early freezing will lead to a review workload and will slow down the pace of Product improvement.

This is actually a conflict between progress and risk. There is no best practice to resolve this conflict. It can be determined only by analyzing the context in a specific project.

 

 

What does best practice mean? In fact, the so-called best practice is that some people think that if you do not follow the best practice, it is likely to fail or suffer losses. But that's all. Who propose best practices? Do they know full enough? Is their theory suitable for your application? Is there any other good solution besides the methods proposed by these so-called best practices?

 

Some so-called best practices are not even practices, because there is a big gap between what we say and what we do.