The objective of functionality testing is to ascertain if the behavior of the entity under test (EUT) is as intended. Behaviour of a EUT is about \u2019obeying some rules\u2019. These \u2019rules\u2019 are really the specification. So to test a functionality of any EUT, we need to first understand the intended rules and then create scenarios that are really various behaviors by combining the rules in different ways and then check the outcome(s).<\/p>\n\n\n\n
To understand the intended behavior, first describe what the EUT is supposed to do. Describe the behavior as a series of steps. Each step accepts\/uses data and processes the data according to some condition(s). Examine each step and extract the condition(s) hidden in the step.<\/p>\n\n\n\n
Once the conditions are extracted from each step, re-write each step as a series of rules and what we have now is prescriptive behavior. From this it is easier to create the test scenarios and then identify the various data sets for each scenario and subsequently generate test cases and therefore for the entire EUT.<\/p>\n","protected":false},"excerpt":{"rendered":"
The objective of functionality testing is to ascertain if the behavior of the entity under test (EUT) is as intended. Behaviour of a EUT is about \u2019obeying some rules\u2019. These \u2019rules\u2019 are really the specification. So to test a functionality of any EUT, we need to first understand the intended rules and then create scenarios […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_links_to":"","_links_to_target":""},"categories":[10],"tags":[],"class_list":["post-158","post","type-post","status-publish","format-standard","hentry","category-robust-test-design"],"yoast_head":"\n