ContributionsMost RecentMost LikesSolutionsRe: generating requestI have a structure with attributes and their values for every risk. I want to use it depending on value for risk in .xls file. It's not only value but very large structure. for example: in xls true true true req: <InstanceData> <RiskList> <Risk id="one"> </Risk> <Risk id="two"> </Risk> <Risk id="three"> </Risk> </RiskList> </InstanceData> in xls true false false <InstanceData> <RiskList> <Risk id="one"> </Risk> </RiskList> </InstanceData> in xls true false true <InstanceData> <RiskList> <Risk id="one"> </Risk> <Risk id="three"> </Risk> </RiskList> </InstanceData> If it is only value, it's not a problem with get data. What if it is structure with thousands of lines nested tags in tags in tags in tags...generating requestI have a question. Part of my request structure looks like this: <InstanceData> <RiskList> <Risk id="one"> </Risk> <Risk id="two"> </Risk> <Risk id="three"> </Risk> </RiskList> </InstanceData> Every risk has a lot of attributes (around 200 lines). In .xls I have an array of combinations of these risks where a line is a combination of true and false values for a specific risk. How can I build an automatic test case for this (existing of all risk node depends on its value from .xls file)?Re: XQuery match returns success where failure expectedI wrote about it too when beta came out.Re: xquery match bug and no find/replace in responseOk, nightly find option works. XQuery doesn't work even when I select only one value. It's like it compare expected value and result and it always is valid...xquery match bug and no find/replace in response- no find/replace in response xml view - Xquery match doesn't work declare function local:sortAttributes($elem as node()) as node() { element{name($elem)} { for $attr in $elem/@* order by name($attr) return if (ends-with(string($attr),'.0')) then attribute {name($attr)} {substring-before(string($attr),'.')} else $attr, for $subelem in $elem/*[name(.) != 'Attribute'] order by $subelem/@id return local:sortAttributes($subelem), for $a in $elem/Attribute order by $a/@symbol return local:sortAttributes($a), if (count($elem/*) = 0) then if (ends-with(string($elem),'.0')) then substring-before(string($elem), '.') else string($elem) else () } }; declare function local:changeMessage($elem as node()) as node() { element{name($elem)} { for $attr in $elem/@* where name($attr) != 'line' and name($attr) != 'formula' and name($attr) != 'function' order by name($attr) return $attr, string($elem) } }; <body> { for $s in //SalesProduct order by $s/@brand return local:sortAttributes($s), for $m in //Message order by $m/@object return local:changeMessage($m) } </body> It says it's valid but some parametres are different when I check old and new response in winmerge -Re: feedback betaDo you fix bugs in xml view (no search in response) and xquery match assertions? These things stop me and other people I knew from using beta2 version.Re: feedback betaXquery match doesn't work. I have my old test from 4.0.1 with declaration like this declare function local:sortAttributes($elem as node()) as node() { element{name($elem)} { for $attr in $elem/@* order by name($attr) return if (ends-with(string($attr),'.0')) then attribute {name($attr)} {substring-before(string($attr),'.')} else $attr, for $subelem in $elem/*[name(.) != 'Attribute'] order by $subelem/@id return local:sortAttributes($subelem), for $a in $elem/Attribute order by $a/@symbol return local:sortAttributes($a), if (count($elem/*) = 0) then if (ends-with(string($elem),'.0')) then substring-before(string($elem), '.') else string($elem) else () } }; declare function local:changeMessage($elem as node()) as node() { element{name($elem)} { for $attr in $elem/@* where name($attr) != 'line' and name($attr) != 'formula' and name($attr) != 'function' order by name($attr) return $attr, string($elem) } }; <body> { for $s in //SalesProduct order by $s/@brand return local:sortAttributes($s), for $m in //Message order by $m/@object return local:changeMessage($m) } </body> Old expected result is different from the new one but I get green light in beta.Re: feedback betaThere is no find/replace in response xml viewRe: feedback betaEnvironment JDBC connection setting are used only by JDBC request. It would be great if it can be used by datasource jdbc too.Re: feedback betaWill there be possible to select environment in pom.xml file (maven plugin)? It will be great to create environments with selected combinations of endpoints and jdbc connectionsa and then autostart it for example by hudson.