Community mailing list archives
Re: Browser Testing with Seleniumby
Am 06.09.2015 um 16:34 schrieb David Arnold <firstname.lastname@example.org>:
That's an article of outstanding usefulness to me! One question remains in my mind (maybe for a "Conclusion" Section):
At the end, are your testers using robot code or does is it aimed to work with selenium IDE?
Because there is definitely a (huge) difference in usability for the none coders. It would be like not bridging the last mile. However, at the end, it was not clear to me, what has been achieved.
Nevertheless, thank you very much! I will definitely read over this article a couple of times!
Best, DavidNils Hamerlinck <email@example.com> schrieb am So., 6. Sep. 2015 um 09:17:Hi all,Here's a blog post explaining how to use and extend the great work of Andreas: http://nils.hamerlinck.fr/blog/2015/09/06/odoo-automation-for-quality-testing/Here's a video showing what you can achieve: https://youtu.be/PH-n5jXdHZYBr,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.RegardsAndreas2015-06-22 23:44 GMT-05:00 David Arnold <firstname.lastname@example.org>: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.
_______________________________________________--Stauder Andreas | Consultant und Projektleiter
brain-tec AG | Technoparkstrassse 1, CH-8005 Zürich