{"id":30406,"date":"2015-12-02T15:14:34","date_gmt":"2015-12-02T09:44:34","guid":{"rendered":"https:\/\/2thenew.today\/blog\/?p=30406"},"modified":"2015-12-07T14:53:44","modified_gmt":"2015-12-07T09:23:44","slug":"javascript-to-groovy-objects-in-geb-functional-test-cases","status":"publish","type":"post","link":"https:\/\/2thenew.today\/blog\/javascript-to-groovy-objects-in-geb-functional-test-cases\/","title":{"rendered":"Javascript to groovy objects in GEB functional test cases"},"content":{"rendered":"

Use Case<\/h2>\n

While\u00a0writing functional tests<\/a> sometimes we need to test whether a certain javascript objects have some particular values.<\/p>\n

If we have a JavaScript object such as in our page<\/p>\n

[code]
\nvar myObj = { attr1 : ‘attr1-val’, attr2 : ‘attr2-val’};
\n[\/code]<\/p>\n

then after reaching that page we can execute the below in our GEB spec file to get that Object as a Map.<\/p>\n

[code]
\njs.exec("return myObj")
\n[\/code]<\/p>\n

Taking this object we can compare the values from some other places for validation e.g. compare with an API to make sure that the data present here matches the data being received from the server.<\/p>\n

But sometimes our objects may be bigger or complex. In such situation it could be better to have these objects as Groovy objects so we can easily compare them.<\/p>\n

Solution<\/h2>\n

So we can have a class like<\/p>\n

[code]
\n@EqualsAndHashCode
\nclass MyArgs {
\n String attr1
\n String attr2
\n}
\n[\/code]<\/p>\n

Now we can get an object in our GEB tests by using<\/p>\n

[code]
\nMyArgs myArgs = js.exec("return myObj") as MyArgs
\n[\/code]<\/p>\n

Problem – Extra properties in JS Object<\/h2>\n

But what would happen in case the JavaScript object had an extra key?<\/p>\n

[code]
\nvar myObj = { attr1 : ‘attr1-val’, attr2 : ‘attr2-val’, ‘EXTRA’: ‘EXTRA-VAL’};
\n[\/code]<\/p>\n

Our above code will break as there will be no property such as EXTRA in our MyArgs class.<\/p>\n

We will see something like<\/p>\n

[code]
\ngroovy.lang.MissingPropertyException: No such property: EXTRA for class: MyArgs
\n[\/code]<\/p>\n

Solution<\/h2>\n

We can take care of any extra properties by using a little metaprogramming trick<\/p>\n

[code]
\n@EqualsAndHashCode
\nclass MyArgs {
\n String attr1
\n String attr2<\/p>\n

def propertyMissing(String name, value){
\n \/\/ WARNING DON’T remove this
\n }<\/p>\n

}
\n[\/code]<\/p>\n

Now only the relevant properties will be mapped and no exception will be thrown in case extra properties are present.<\/p>\n","protected":false},"excerpt":{"rendered":"

Use Case While\u00a0writing functional tests sometimes we need to test whether a certain javascript objects have some particular values. If we have a JavaScript object such as in our page [code] var myObj = { attr1 : ‘attr1-val’, attr2 : ‘attr2-val’}; [\/code] then after reaching that page we can execute the below in our GEB […]<\/p>\n","protected":false},"author":161,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":1,"footnotes":""},"categories":[1818,1],"tags":[1561,14,897,9,55],"class_list":["post-30406","post","type-post","status-publish","format-standard","hentry","category-automation-testing-testing-2","category-technology","tag-automation-testing","tag-testing","tag-geb","tag-groovy","tag-javascript"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t