{"id":1846,"date":"2012-10-31T17:48:13","date_gmt":"2012-10-31T12:18:13","guid":{"rendered":"http:\/\/www.automationrepository.com\/?p=1846"},"modified":"2012-11-21T19:03:49","modified_gmt":"2012-11-21T13:33:49","slug":"desigining-keyword-driven-framework-mapped-at-functional-level-part-1","status":"publish","type":"post","link":"https:\/\/www.automationrepository.com\/wordpress\/2012\/10\/desigining-keyword-driven-framework-mapped-at-functional-level-part-1\/","title":{"rendered":"Designing Keyword Driven Framework mapped at Functional Level – Part 1"},"content":{"rendered":"
\n

In the previous two articles we saw how to create a Keyword Driven Framework<\/a> where the keywords are mapped at Operation Level<\/a>. In this article, we will cover a different type of Keyword Driven Framework – the one where the keywords are mapped at Functional Level.<\/p>\n

Keyword Driven Framework mapped at Functional Level is the most commonly used Keyword Driven Framework type. How its actually implemented may vary from project to project. But the basic premise always remains the same – “define keywords and assign them to actions or functions”.<\/strong><\/p>\n

The important point that should be noted in this framework is that the keywords are mapped to a function which will contain more than one line of code. For example, you can have a keyword called ‘Login’ that in turn can be mapped to function called fnLogin. Now, this function will contain the few lines of code that will open the application, enter user name and password and then click on Submit button.<\/p>\n

This is different from the Keyword Driven Framework implementation mapped at Operational Level, where the keyword is mapped to an action performed at object level. (For more details about the basics of the Keyword Driven Framework, refer – Basics of Keyword Driven Framework<\/strong><\/a>)<\/p>\n


\n<\/span><\/p>\n

Topics that will be covered in this article<\/h3>\n

1)<\/strong> The components that are commonly used with this framework.<\/p>\n

2)<\/strong> Flow of the test cases in this framework.<\/p>\n

Let us see each of these points one by one.<\/p>\n


\n<\/span><\/p>\n

Common Components used in Keyword Driven Framework mapped at Functional Level<\/h3>\n

Following are the components that are commonly used with this framework –<\/p>\n

\"Components<\/p>\n

1)<\/strong> Test Scripts or Driver Script:<\/strong> As mentioned in the beginning of this article, in this type of framework all the keywords are associated with some functions. So naturally, the entire test case flow would be composed of multiple functions.<\/p>\n

For example, consider a test case where the you have to login to Gmail, send an email and then you have to Logout from Gmail. Looking at the test case, you can easily figure out that the test case can be divided into 3 functions –<\/p>\n