Now that I'm actually integrating @Lampei's/my pull request into a project, I notice a change that enables WebDriver ("version 2" mode) by default.
That means that existing tests will often fail, because RC and WebDriver don't have all of the same functionality.
Here's an example from ValidateThis (a consumer of CFSelenium):
public void function beforeTests() {
baseurl = "http://#cgi.server_name#:#cgi.server_port#";
browserUrl = "#baseUrl#/validatethis/samples/FacadeDemo/";
super.beforeTests();
selenium.setTimeout(30000);
crlf = chr(10);
}
The super call would need to be changed to point back to the old version, in order for tests to work:
super.beforeTests(version=1, browserUrl=browserUrl);
It might have been better to preserve seamless backward compatibility by defaulting to v1 (RC), then folks could upgrade, when they see fit, to v2 (Webdriver) by changing their beforeTests() accordingly.
@Lampei, @ddspringle, et al,, thoughts?
Now that I'm actually integrating @Lampei's/my pull request into a project, I notice a change that enables WebDriver ("version 2" mode) by default.
That means that existing tests will often fail, because RC and WebDriver don't have all of the same functionality.
Here's an example from ValidateThis (a consumer of CFSelenium):
The
supercall would need to be changed to point back to the old version, in order for tests to work:It might have been better to preserve seamless backward compatibility by defaulting to v1 (RC), then folks could upgrade, when they see fit, to v2 (Webdriver) by changing their
beforeTests()accordingly.@Lampei, @ddspringle, et al,, thoughts?