Does anybody always follow concepts like, Cyclomatic Complexity, Equivalence Partitioning, Boundary Value Analysis in their testing applications ? or Let me know the best way to cover these techniques when testing application.
Tell me more
×
Software Quality Assurance & Testing Stack Exchange is a question and answer site for
software quality control experts, automation engineers, and software testers. It's 100% free, no registration required.
|
|
Test heuristics sheet is another useful document which provides checklist based on concepts and real-world experience. It took time to figureout the hyperlink to post it for this question. Please check http://testobsessed.com/wp-content/uploads/2011/04/testheuristicscheatsheetv1.pdf. I found this checklist useful for my reference. |
|||
|
|
|
For me, I wouldn't say I formally say "Hey, I'm doing Boundary Value Analysis". However, these are techniques that I've learned over the years that I apply in my evaluations almost intuitively. Yeah, there's probably room for me to more formalize this, but it's more a matter of practical application than formalization. |
|||||
|
|
Cyclomatic complexity is one way to assess or measure the complexity of a chunck of code (specifically the number of linearly indpendent paths). Some developers may use this measure to refactor complex code, or testers may use this to identify areas of the code that may be a "target rich environment" that is more likely to have issues. Equivalence partitioning, boundary value analysis, etc. are functional testing techniques and as Tristaan indicates all testers often informally apply the concepts of these techniques during their testing. |
|||
|
|
I apply such concepts when and if they are appropriate for the situation at hand. I can say with certainty that I don't always follow such concepts. |
|||
|
|
