Re: [Wonder-disc] ERSelenium without ERExtensions
Re: [Wonder-disc] ERSelenium without ERExtensions
- Subject: Re: [Wonder-disc] ERSelenium without ERExtensions
- From: Steven Mark McCraw <email@hidden>
- Date: Tue, 26 Jun 2007 18:19:29 -0400
ERSelenium's idea is to facilitate a lot of common tasks that are
usually solved manually to organize Selenium testing. Among these
tasks are:
- Automatic test suites generation from your folder structure.
I am curious as to what you are doing for this. To me, Selenium
tests are for functional testing and so have no relation at all to
project structure.
The reason for doing it this way (says the guy who's used ERSelenium
a few times now) is that is a piece of cake to create test suites.
There is no maintaining an external test suite. You just create a
folder called Selenium (or whatever you configure the name to be) in
the Properties folder of the project you want to test, and any folder
you embed within it becomes a test suite when you run everything from
a simple URL. You drop your selenium tests in child folders of the
Selenium folder and you are done. It is ridiculously easy, as
opposed to the whole chrome:// test suite thing, which I never got to
work, although I did not spend much time trying because ERSelenium
became available just as I began getting good and familiar with using
Selenium.
The up side to user ERSelenium test suites (besides how easy it is to
create them) is that they run in any browser. All you have to do is
point to the 'StartSeleniumTesting' direct action class in your
application url, and away you go. I believe I read that if you use
chrome:// as your URL, you are stuck with Firefox as a testing
platform, because only Firefox supports that protocol.
- Writing tests in the preferred format - wiki/html.
Is that different from Selenese?
The difference is that instead of using html tags to delimit things,
you use pipe symbols, and it's a lot more readable (says me).
Instead of
<tr>
<td>type</td>
<td>userName</td>
<td>chill2</td>
</tr>
<tr>
<td>type</td>
<td>password</td>
<td>chill2</td>
</tr>
<tr>
<td>clickAndWait</td>
<td>loginButton</td>
<td></td>
</tr>
You have
|type|userName|chill2|
|type|password|chill2|
|clickAndWait|loginButton||
But I believe you can use this format with or without ERSelenium.
- Unified format of setup/tear down methods with appropriate error
messages.
I don't see the need for these. For me, the Selenium tests should be
from the point of view of the user of the application. So any
setup / tear down outside of loading the bootstrap data should be
done through the UI and be part of the test. In some rare occasions
(mimicking interactions from other systems), I do need some setup
that is not possible from the UI. In that case, I create a direct
action to do this and call it from the test in a new window. The
direct action is only enabled during testing runs.
I agree with you here. I've just been using direct actions. Not
sure what ERSelenium brings to the table here or how to use it.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden