Tweeted twitter.com/#!/StackProgrammer/status/245401608274444288
7 added 178 characters in body
source | link

Having read a lot about this topic --- such as on this Software Testing Fundamentals site on verification and validation and Software Testing and Quality Assurance: Theory and Practice by Naik and Tripathy --- I still do not get it. Verification should prove that you are building the product right, while validation proves that you built the right product. But only static techniques (code reviews, requirements checks...) are mentioned as being verification methods. How can you say if its implemented correctly if you do not test it? It is said that verification ensures that the product meet specified requirements. Again, if the function is specified to work somehow, only by testing I can say that it does.

Could anyone explain this to me please?

Having read a lot about this topic --- such as on this Software Testing Fundamentals site on verification and validation --- I still do not get it. Verification should prove that you are building the product right, while validation proves that you built the right product. But only static techniques (code reviews, requirements checks...) are mentioned as being verification methods. How can you say if its implemented correctly if you do not test it? It is said that verification ensures that the product meet specified requirements. Again, if the function is specified to work somehow, only by testing I can say that it does.

Could anyone explain this to me please?

Having read a lot about this topic --- such as on this Software Testing Fundamentals site on verification and validation and Software Testing and Quality Assurance: Theory and Practice by Naik and Tripathy --- I still do not get it. Verification should prove that you are building the product right, while validation proves that you built the right product. But only static techniques (code reviews, requirements checks...) are mentioned as being verification methods. How can you say if its implemented correctly if you do not test it? It is said that verification ensures that the product meet specified requirements. Again, if the function is specified to work somehow, only by testing I can say that it does.

Could anyone explain this to me please?

6 Fixing missing parenthesis.
source | link

Having read a lot about this topic (such--- such as on this Software Testing Fundamentals site on verification and validation, --- I still do not get it. Verification should prove that you are building the product right, while validation proves that you built the right product. But only static techniques (code reviews, requirements checks...) are mentioned as being verification methods. How can you say if its implemented correctly if you do not test it? It is said that verification ensures that the product meet specified requirements. Again, if the function is specified to work somehow, only by testing I can say that it does.

Could anyone explain this to me please?

Having read a lot about this topic (such as on this Software Testing Fundamentals site on verification and validation, I still do not get it. Verification should prove that you are building the product right, while validation proves that you built the right product. But only static techniques (code reviews, requirements checks...) are mentioned as being verification methods. How can you say if its implemented correctly if you do not test it? It is said that verification ensures that the product meet specified requirements. Again, if the function is specified to work somehow, only by testing I can say that it does.

Could anyone explain this to me please?

Having read a lot about this topic --- such as on this Software Testing Fundamentals site on verification and validation --- I still do not get it. Verification should prove that you are building the product right, while validation proves that you built the right product. But only static techniques (code reviews, requirements checks...) are mentioned as being verification methods. How can you say if its implemented correctly if you do not test it? It is said that verification ensures that the product meet specified requirements. Again, if the function is specified to work somehow, only by testing I can say that it does.

Could anyone explain this to me please?

5 deleted 111 characters in body
source | link

Having read a lot about this topic (such as on this Software Testing Fundamentals site on verification and validation, I still diddo not get it. Verification should prove that you are building the product right, while validation proves that you buildbuilt the right product. But only static techniques are mentioned as being verification methods (code reviews, requirements checks...) are mentioned as being verification methods. But howHow can you say if its implemented correctly if you do not test it? It is said that verification checks e.g. code for its correctnes. Verification - ensureensures that the product meet specified requirements. Again, if the function is specified to work somehow, only by testing I can say that it does. Could

Could anyone explain this to me please?

EDIT: As Wiki says:
Verification:Preparing of the test cases (based on the analysis of the requireemnts)
Validation: Running of the test cases

Having read a lot about this topic, I still did not get it. Verification should prove that you are building the product right, while validation you build the right product. But only static techniques are mentioned as being verification methods (code reviews, requirements checks...). But how can you say if its implemented correctly if you do not test it? It is said that verification checks e.g. code for its correctnes. Verification - ensure that the product meet specified requirements. Again, if the function is specified to work somehow, only by testing I can say that it does. Could anyone explain this to me please?

EDIT: As Wiki says:
Verification:Preparing of the test cases (based on the analysis of the requireemnts)
Validation: Running of the test cases

Having read a lot about this topic (such as on this Software Testing Fundamentals site on verification and validation, I still do not get it. Verification should prove that you are building the product right, while validation proves that you built the right product. But only static techniques (code reviews, requirements checks...) are mentioned as being verification methods. How can you say if its implemented correctly if you do not test it? It is said that verification ensures that the product meet specified requirements. Again, if the function is specified to work somehow, only by testing I can say that it does.

Could anyone explain this to me please?

4 Added link from comment.
source | link
3 added 154 characters in body
source | link
2 edited tags
| link
1
source | link