Community mailing list archives
Re: Browser Testing with Seleniumby
Hi Andreas, dos you reas this? We actually have now one Person on Selenium and would be very interested in collaborating with you in your solution. Thanks and best, David
David Arnold <firstname.lastname@example.org> schrieb am Di., 23. Juni 2015 um 09:17:
Thanks Nhomar, Thanks Andreas,Andreas, actually I had the same problems you described, but did not quite right know how to document them here. I'm indeed very interested, because we might to use it for test driven scrum development with users, where customers might be able to "just record" there weekly testing and reviewing in order to achieve greater regression resilience of the evolving codebase. I think your development could be a valuable milestone towards that goal. I feel sufficiently confident, so that we could write a blogpost together?Nhomar, I was loosly able to connect phantomjs with Selenium as I have read those words together in several blogposts. I would hope to have both tools integrated for the sake of also beeing able to leverage the ease of just "recording" on the UI real transactions of actual users. Visionary: A button, that is integrated into Odoo in the userspace, which let's peolpe (on firefox) simple document test cases and submit them to the odoo codebase (or the addon-codebas or whatever)... How greate would that be?Thanks for your valuable comments and for your time! I would be interested to develop this idea further on a loose commitment basis. In this order of ideas, I can try to contribute (with roadmap but without schedule) by integrating tools into my workflow and develop some kind of Usecase/Proposal for the community.If this is deemed useful, I might also ask OCA for guidance and the exact steps to perform in order to fit common procedures.Kind RegardsDavid ArnoldEl mar., 23 jun. 2015 a las 3:44, Andreas Stauder (<email@example.com>) escribió:Hello DavidI used the Se-Builder ( http://seleniumbuilder.github.io/se-builder/ ) to record the teststeps in the Browser. The problem is, that Odoo set's dynamically HTML-IDs that change whenever you open the next view.I programmed a Odoo addon (1), that provides some additional information in the HTML, a extended Se-Builder (2) and a extension to the robot-framework (3) to play back the recorded case.All that is working only for a few many cases, like menu, text, date, many2one, one2many fields. Only the very very basic stuff. But it is possible to extend it.When you are interested in that, I will try to make a video demonstrating it and provide a install manual for all components.RegardsAndreasOn Tue, Jun 23, 2015 at 7:44 AM, Nhomar Hernández <firstname.lastname@example.org> wrote:So I would be interested in an opinion on how far Selenium could replace the existing approaches and if it is a viable suggestion for effectively increasing e2e test coverage and foster explorative testing?Did you read about phantomjs? (which is the actual model)Basically is create a no-frontend browser and run a set of steps on json, such tests can be changed/improved in a convenient way.The issue as usual with actual approach is the absolute leak of documentation, if odoo dedicate some time to explain for idiots some great ideas a lot of people should impact better in the community.IMHO selenium is great, and it does the job perfectly, but I prefer a solution embeded in the system with no graphical needs.If I personally dedicate something to odoo it should be in create more tests, and improve the output of actual ones (which are very cryptical first times).My 2 cents.