So, really, the only option is to make sure a older version of firefox is available on your development machine, so you can run the acceptance tests.īut just to be clear, this doesn't mean I am sitting browsing the web with a old firefox browser, it simply means that to complete a build, I need to have a environment available on my machine that can finish a build (including the automated testing, which relies on seleniums webdriver, which relies on well, a older firefox ). Now, you can't just remove selenium from the build(that would mean stripping the acceptances tests for the UI), nor just randomly upgrade it, even if a newer version was there (there is a process for changing the build). Which means, if the machine running the automated tests have a firefox version newer than that, the build will fail.
Now, selenium currently only supports firefox up until v20 ( … leaseNotes). These automated acceptance tests are done with various tools, and more often than not, one of these tools being the selenium web-driver.
Usually, if any modules of your project has a web ui, a subset of the acceptance tests will be written against the UI.
Most larger companies, who develop in a BDD or ATDD way, will have a very clear defined build, testing and deployment process. Hello again, I don't think I clearly explained the scenario, there is not really any mess for us to fix.
0 kommentar(er)
