WebTestRecorderEmail Step emailSetConfig
Description
Sets Email Configuration information.
Parameters
- server
- Required? yes
- The email server (including port if required).
- delay
- Required? no, default is 0
- The delay between email steps in seconds - sometimes helps with email servers which are fussy about multiple logins.
- description
- Required? no
- The description of this test step.
- password
- Required? yes/no
- The email account password. Probably required for your steps to work.
- type
- Required? no, default is pop3
- The email server type (only 'pop3' has been tested).
- username
- Required? yes/no
- The email account username. Probably required for your steps to work. Might be set using a system property.
Details
Here is an example of using emailSetConfig.
emailSetConfig
<property name="username" value="yourUsername"/>
<property name="password" value="yourPassword"/>
<property name="mailserver" value="your.mailserver.com"/>
<property name="servertype" value="pop3"/>
<steps>
<emailSetConfig server="${mailserver}" type="${servertype}"
password="${password}" username="${username}" delay="5"/>
<-- ... email tests go here ... -->
</steps>
<property name="password" value="yourPassword"/>
<property name="mailserver" value="your.mailserver.com"/>
<property name="servertype" value="pop3"/>
<steps>
<emailSetConfig server="${mailserver}" type="${servertype}"
password="${password}" username="${username}" delay="5"/>
<-- ... email tests go here ... -->
</steps>
The delay attribute is a convenience mechanism that has the same effect as putting a sleep in front of all of your email steps. This is provided because many email servers have issues with opening connections immediately after the previous one has been closed. If you steps are failing in an unexpected fashion, turn on debugging - if it shows that sometimes fewer messages are on your email server than you expect, try increasing the delay value. If that doesn't work, you can try placing your step(s) within a retry loop.
