Main question of testing: How to forecast quality of software?
(for devs, testers, clients, users)
- Analytic school (established when access to processor time was very limited).
Testing is a scientific, analytical work. SW is a logical artifact. Testing without test cases NOT possible. Lots of thinking. Quality can be measured with numbers! Creativity is not applied. Testing can be binarily Correct or Incorrect.
Weakness: Cannot guarantee that the software does the correct thing... Can only ensure that things that are done are done correctly.
- Standard school
Quality is conformance to standards. Standards and documentation needed to perform tests. Standardizing the standards! Testing is measuring of development process. Testing checks the product, not more.
Testing can be managed: predictability, metrics, repeatability, planning.
Testing only what is documented. Quality components guarantee quality system.
Weakness: Tests are OK, but there are still bus in SW!!!
- Quality school
Quality is what CUSTOMER dictates (that's documented and used as a guide to develop and test). There is no only one 'correct' standard.
Weakness: SW is done by docs, but it does NOT conform to wishes and expectetations.... Integration tests are used. Test cases still rule! 'Police control' after quality. Only testers know what 'it is ready' - and he is the main responsible. Devs make mistakes. "Testing is the most important part of the process" - testers of this school think ;).
- Agile school
Quality is customer's thinking / evaluation of product, not a standard or a document... Pelaple & working SW is more important than the docs. Let's sit together with customer and write SW! The same with test ;) Find bugs that important for customers!!!
'Police contolr' sucks! Everybody can test. Test automation & TDD rules! Automate everything!!! Prove that SW functions 'as expected'. User stories, DoD.
Still cannot quarantee quality of SW...
- Context-driven school
Everything is shit. Life is misery. The value of any practice depends on its context. There are good practices in a context, but there are no best practices.
The product is a solution. If the problem is not solved, the product oes NOT work!!!
Good SW testing is a challenging intellectual process.
Sometimes documentation is essential. Sometimes we need a test plan. Sometimes we DO NOT need testing...
Correct is what works HERE & NOW. Test what's important to customer!!!
(for devs, testers, clients, users)
- Analytic school (established when access to processor time was very limited).
Testing is a scientific, analytical work. SW is a logical artifact. Testing without test cases NOT possible. Lots of thinking. Quality can be measured with numbers! Creativity is not applied. Testing can be binarily Correct or Incorrect.
Weakness: Cannot guarantee that the software does the correct thing... Can only ensure that things that are done are done correctly.
- Standard school
Quality is conformance to standards. Standards and documentation needed to perform tests. Standardizing the standards! Testing is measuring of development process. Testing checks the product, not more.
Testing can be managed: predictability, metrics, repeatability, planning.
Testing only what is documented. Quality components guarantee quality system.
Weakness: Tests are OK, but there are still bus in SW!!!
- Quality school
Quality is what CUSTOMER dictates (that's documented and used as a guide to develop and test). There is no only one 'correct' standard.
Weakness: SW is done by docs, but it does NOT conform to wishes and expectetations.... Integration tests are used. Test cases still rule! 'Police control' after quality. Only testers know what 'it is ready' - and he is the main responsible. Devs make mistakes. "Testing is the most important part of the process" - testers of this school think ;).
- Agile school
Quality is customer's thinking / evaluation of product, not a standard or a document... Pelaple & working SW is more important than the docs. Let's sit together with customer and write SW! The same with test ;) Find bugs that important for customers!!!
'Police contolr' sucks! Everybody can test. Test automation & TDD rules! Automate everything!!! Prove that SW functions 'as expected'. User stories, DoD.
Still cannot quarantee quality of SW...
- Context-driven school
Everything is shit. Life is misery. The value of any practice depends on its context. There are good practices in a context, but there are no best practices.
The product is a solution. If the problem is not solved, the product oes NOT work!!!
Good SW testing is a challenging intellectual process.
Sometimes documentation is essential. Sometimes we need a test plan. Sometimes we DO NOT need testing...
Correct is what works HERE & NOW. Test what's important to customer!!!
0 коментарі:
Дописати коментар