Re: Persistent Sessions (UNCLASSIFIED)

Hi,

in our Ant-based webtests, we only use include files for including
maps and the config elements, as they cannot be parametrized. Instead,
we use Ant-Macros, so you can write something like
<go_to_startpage_and_login withName="foo" andPassword="bar"/>

in our Groovy-based webtests, we have a little more control over how
tests are executed. Here we are able to add steps at the beginning or
end of a test, thereby reducing clutter.

Regards,
Murat Knecht


2011/1/19 Habbert, Michael (Key-Work) <[email protected]>:
> Hi Lee,
>
> we do keep our webtests as small as possible.
>
> Of course we also have to login and logout in nearly every webtest.
>
> We do it by outsourcing these basic steps into some include files (xml snippets inside the include directory).
> These files are included at the beginning - login - and at the end - logout - of each test.
>
> ----------------
> <project default="test">
>        &load_ui_labels;
>        <target name="test">
>
>                <webtest name="test-name to identify">
>                        &config;
>
>                        <steps>
>                                &login;
>
> [.... here ist he place fort he testing .. ]
>
>                                &logout;
>                        </steps>
>                </webtest>
>        </target>
> </project>
> --------------------
>
> So our webtests keep simple and clean or at least without the login and logout stuff.
>
> Greetings
>
> Michael Habbert
>
>
>
> Michael Habbert
> Key-Work Consulting GmbH | Kriegsstr. 100 | 76133 Karlsruhe | Germany | www.key-work.de
> Fon: +49-721-78203-269 | E-Mail: [email protected] | Fax: +49-721-78203-10
>
> Key-Work Consulting GmbH Karlsruhe, HRB 108695, HRG Mannheim
> Geschäftsführer: Andreas Stappert, Tobin Wotring
> -----Ursprüngliche Nachricht-----
> Von: [email protected] [mailto:[email protected]] Im Auftrag von Lee V. Mangold (LVM Engineering, Inc.)
> Gesendet: Dienstag, 18. Januar 2011 18:56
> An: [email protected]
> Betreff: [Webtest] Persistent Sessions (UNCLASSIFIED)
>
> Classification:  UNCLASSIFIED
> Caveats: NONE
>
> I realize this question has been asked a number of times, but I have yet to find a good answer:
>
> I'm trying to write test cases for Drupal CMS. I need to log in, run tests, and logout. I'm able to do this in one monolithic test case, but that's not a sustainable approach. I'm wondering what others do in situations like this, or if anyone has experience with this inside Drupal...
>
>
>
>
> Classification:  UNCLASSIFIED
> Caveats: NONE
>
>
> _______________________________________________
> WebTest mailing list
> [email protected]
> http://lists.canoo.com/mailman/listinfo/webtest
>
>
> _______________________________________________
> WebTest mailing list
> [email protected]
> http://lists.canoo.com/mailman/listinfo/webtest
>