{"id":954,"date":"2018-11-04T16:05:32","date_gmt":"2018-11-04T16:05:32","guid":{"rendered":"http:\/\/talentedtester.com\/?p=954"},"modified":"2019-10-31T19:18:06","modified_gmt":"2019-10-31T19:18:06","slug":"what-is-an-agile-testing-acceptance-criteria","status":"publish","type":"post","link":"http:\/\/talentedtester.com\/what-is-an-agile-testing-acceptance-criteria\/","title":{"rendered":"What is an Agile Testing Acceptance Criteria?"},"content":{"rendered":"
In my years of testing one of the most important things I have identified is Acceptance criteria. Unfortunately, I have seen too many projects focus on what they think is right, rather than what was agreed and defined in the Acceptance criteria.<\/p>\n
What is Acceptance Criteria? Acceptance criteria is the agreed conditions that a software program should meet to be accepted by a customer or stakeholder. It defines what is acceptable by the program to insure quality.<\/b><\/p>\n
Typically, this acceptance criteria is broken down into 3 areas, functional, non-functional and performance. If you have been around in testing for a while, or been looking for testing jobs, its likely you have heard of these terms before.<\/p>\n
Shop Now<\/span> Ads by Amazon <\/a> <\/a> <\/span> <\/span>\u00d7Thank you!<\/p>\n This will help us improve your ad experience. We will try not to show you such ads again.<\/p>\n Report a problem<\/p>\n This item is…<\/p>\n Not relevant Inappropriate \/ Offensive Displayed poorly Other <\/p>\n Add Comments (Max 320 characters)<\/span><\/p>\n Software Testing<\/span> <\/a>$31.17<\/span>$49.99<\/span>Bestseller<\/span> <\/span>(30)<\/span> <\/a>DEAL OF THE DAYENDS IN <\/span> <\/a>\u00d7Thank you!<\/p>\n This will help us improve your ad experience. We will try not to show you such ads again.<\/p>\n Report a problem<\/p>\n This item is…<\/p>\n Not relevant Inappropriate \/ Offensive Displayed poorly Other <\/p>\n Add Comments (Max 320 characters)<\/span><\/p>\n Clean Code: A Handbook of Agi\u2026<\/span> <\/a>$39.49<\/span>$49.99<\/span>Bestseller<\/span> <\/span>(499)<\/span> <\/a>DEAL OF THE DAYENDS IN <\/span> <\/a>\u00d7Thank you!<\/p>\n This will help us improve your ad experience. We will try not to show you such ads again.<\/p>\n Report a problem<\/p>\n This item is…<\/p>\n Not relevant Inappropriate \/ Offensive Displayed poorly Other <\/p>\n Add Comments (Max 320 characters)<\/span><\/p>\n Lessons Learned in Software Testing: \u2026<\/span> <\/a>$29.78<\/span>$39.99<\/span>Bestseller<\/span> <\/span>(71)<\/span> <\/a>DEAL OF THE DAYENDS IN <\/span> <\/a>\u00d7Thank you!<\/p>\n This will help us improve your ad experience. We will try not to show you such ads again.<\/p>\n Report a problem<\/p>\n This item is…<\/p>\n Not relevant Inappropriate \/ Offensive Displayed poorly Other <\/p>\n Add Comments (Max 320 characters)<\/span><\/p>\n A Friendly Introduction to Software Testing<\/span> <\/a>$29.95<\/span>$29.95<\/span>Bestseller<\/span> <\/span>(18)<\/span> <\/a>DEAL OF THE DAYENDS IN <\/span> <\/a>\u00d7Thank you!<\/p>\n This will help us improve your ad experience. We will try not to show you such ads again.<\/p>\n Report a problem<\/p>\n This item is…<\/p>\n Not relevant Inappropriate \/ Offensive Displayed poorly Other <\/p>\n Add Comments (Max 320 characters)<\/span><\/p>\n The Art of Software Testing<\/span> <\/a>$97.22<\/span>$167.00<\/span>Bestseller<\/span> <\/span>(8)<\/span> <\/a>DEAL OF THE DAYENDS IN <\/span> <\/a>\u00d7Thank you!<\/p>\n This will help us improve your ad experience. We will try not to show you such ads again.<\/p>\n Report a problem<\/p>\n This item is…<\/p>\n Not relevant Inappropriate \/ Offensive Displayed poorly Other <\/p>\n Add Comments (Max 320 characters)<\/span><\/p>\n Software Testing 2nd (second) edition Text Only<\/span> <\/a>$45.56<\/span>Bestseller<\/span> <\/span> <\/a>DEAL OF THE DAYENDS IN <\/span> <\/a>\u00d7Thank you!<\/p>\n This will help us improve your ad experience. We will try not to show you such ads again.<\/p>\n Report a problem<\/p>\n This item is…<\/p>\n Not relevant Inappropriate \/ Offensive Displayed poorly Other <\/p>\n Add Comments (Max 320 characters)<\/span><\/p>\n The Way of the Web Tester: A Beginner’s \u2026<\/span> <\/a>$25.78<\/span>$29.00<\/span>Bestseller<\/span> <\/span>(14)<\/span> <\/a>DEAL OF THE DAYENDS IN <\/span> <\/a>\u00d7Thank you!<\/p>\n This will help us improve your ad experience. We will try not to show you such ads again.<\/p>\n Report a problem<\/p>\n This item is…<\/p>\n Not relevant Inappropriate \/ Offensive Displayed poorly Other <\/p>\n Add Comments (Max 320 characters)<\/span><\/p>\n Software Testing: A Craftsman’s Appr\u2026<\/span> <\/a>$96.16<\/span>$125.00<\/span>Bestseller<\/span> <\/span>(4)<\/span> <\/a>DEAL OF THE DAYENDS IN <\/span> <\/a> Ads by Amazon <\/a> <\/a> <\/span> <\/span><\/p>\n As the name suggests this breaks down the functional areas, such as \u201cA User Login\u201d. This is a specific function of the system that will have acceptance criteria, such as, once a valid password and user name is provided, the user will gain access.<\/p>\n A good example of non-functional is the design and layout of a corporate website. This is different to a functional module I this sense. So, if we extend the example of the corporate website, you may want your site to follow your agreed brand colours. Therefore, a non-functional criteria item could be verifying this has been met.<\/p>\n Performance is different to functional. It focusses on certain agreed performance metrics for the software. For example,<\/p>\n \u201cThe system must load the contacts page within 10 milliseconds\u201d.<\/p>\n Or<\/p>\n \u201cThe system must be able to support the load of 100 simultaneous users\u201d.<\/p>\n These are just quick examples to make sure you understand what I a mean, they are not the perfect example of a well drafted user story.<\/p>\n Acceptance criteria<\/strong>, done correctly, should not explicitly state how to technically do the solution. It should clearly state the intention. For example, it shouldn\u2019t say to authorise the invoice, the supervisor must click the \u201cA\u201d key. It should be saying; a supervisor can authorise an invoice.<\/p>\n In other words, it should not be biased to any form of implementation. The design and execution of the test is different, this is more for an acceptance test.<\/p>\n Acceptance Tests<\/strong>, on the other hand are tests to prove that the acceptance test criteria has been met. In agile<\/a>, they are typically derived from User stories. These tests are usually conducted by the actual user. Which is different to unit tests, for example. Because Unit tests are usually ran by developers.<\/p>\n These tests are also referred to as \u201cblack box tests\u201d. Reason being, the user looks at the tests at a high-level functional level, without any need to understand the coding conditions and interaction between modules.<\/p>\nFunctional Criteria<\/strong><\/h2>\n
Non-Functional Criteria<\/strong><\/h2>\n
Performance Criteria<\/h2>\n
What is the difference between an Acceptance test & Acceptance Criteria?<\/strong><\/h2>\n