In recent years there has been a variety of definitions applied to user acceptance testing (UAT). His success in validating a system or application is "fit for use" by the user attempts depends on how you define this phase of testing
For example, if you see the TSU as a functional test based solely on user needs, is likely to lose the same things in testing that were lost in the definition of requirements. Another example is that if you see the evidence that UAT can be automated in the agility tests, you may lose the "hands on" evaluation of actual users to determine how the practical application fits your needs .
This should be clear that I am not saying that you should use my definition of UAT, or is hopelessly doomed the project. What I am saying is that there are a variety of views UAT that may or may not suit your needs - and it is better to be sure you know the differences in the ways UAT is defined.
I must be clear that I am not saying that you should use my definition of UAT, or is hopelessly doomed the project. What I am saying is that there are a variety of views UAT that may or may not suit your needs - and it is better to be sure you know the differences in the ways UAT is defined.
0 comments:
Post a Comment