addition: I unpack the downloaded webtest.jar from different version and look
for "VerifyHeader"
grep -r -i 'verifyHeader' *.taskdef

Result old jar:
webtest_base_relaxed.taskdef:verifyHeader:com.canoo.webtest.steps.verify.VerifyHeader
webtest_base_strict.taskdef:verifyHeader:com.canoo.webtest.steps.verify.VerifyHeader
webtest_relaxed.taskdef:verifyHeader:com.canoo.webtest.steps.verify.VerifyHeader
webtest_strict.taskdef:verifyHeader:com.canoo.webtest.steps.verify.VerifyHeader
webtest.taskdef:verifyHeader:com.canoo.webtest.steps.verify.VerifyHeader
 
Result new jar:
-


Marcel1606 wrote:
> 
> Hi.
> I got the exception, too
> (com.canoo.webtest.engine.StepExecutionException).
> The end of the stacktrace:
> 
> Caused by: : Problem: failed to create task or type verifyHeader
> Cause: The name is undefined.
> 
> In the source (/src/main/java/com/canoo/webtest/steps/verify/) isn't a
> file like verifyHeader.java.
> greeting
> Marcel
> 
> 
> 
> sebastianb wrote:
>> 
>> Hello,
>> 
>> since i have upgraded my grails (v1.3.4) to webtest 3.0 some of my
>> webtest fails due to a StepExecutionException for verifyHeader: e.g:
>> 
>> class SimpleWebTests extends grails.util.WebTest {
>> 
>>     void testGrailsProjectSite() {
>>         invoke 'http://www.grails.org'
>> 
>>         storeResponseCode(property: "status")
>>         verifyProperty(description:"response code should be 200",
>> name:"status", text:"200")
>> 
>>         verifyHeader(description: 'checking Content-Type header', name:
>> 'Content-Type', text: "text/html;charset=utf-8")
>>     }
>> 
>> }
>> 
>> Did the verifyHeader syntax change in some way or am i missing something?
>> 
>> Kind regards
>> Sebastian
>> 
>> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/verifyHeader-throws-com.canoo.webtest.engine.StepExecutionException-tp29406508p29428167.html
Sent from the WebTest mailing list archive at Nabble.com.

_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest

Reply via email to