build moneky* :) 2012/7/22 Linards Liepiņš <[email protected]>
> Hmm .. I suppose some clarification/reminding of how stuff owrks will not > harm here... > > Something must build/compile this selenium plugin. Usually this something > is "build moneky". Usually these build monekys are most occupied people in > whole development process because of several reasons - few of them you > mentioned by yourself. For example - build automatization systems, > therefore, build scripts have got no AI to automatically adapt to new > changes made in api level of the dependewd software, therefore you have two > options: > > - maintain you own compatability layer ( in the form of some kind of lib > .. ) > - force Selenium to pay someone willing to maintain it. Web Browser deves > have no 3rd party interest in this ... :/ > > Therefore it the word "maintaining" is used ... it is not about willing - > it is almost all the time about inconsistency on the release/version > schedule and lack of documentation. > > > 2012/7/22 Andrew Gray <[email protected]> > >> Hi All, >> >> One of the biggest showstoppers for me is the incompatibility of the >> version of selenium embedded within the selenium plugin with browser >> versions changing so much. We are up to Chrome 22 or something and Firefox >> 14.0.1. >> >> My tests just fail because the jenkins plugin is not spawning the browser >> process to run the test. >> >> Is there a(n) (automated?) way we can get keep the Selenium Plugin up to >> date with browser releases? >> >> The Selenium Project seems to be able to release versions of selenium >> that keep pace with browsers >> >> Why can't the Selenium Plugin keep place with the latest release of >> Selenium (and therefore browsers)? >> >> Regards, >> >> Andrew >> > > > > -- > A.C. Linards L. > -- A.C. Linards L.
