Hi,
First thank you Raphaël ! I, we, appreciate your work on all that stuff around improving OpenERP and his community ! Thank you for all your efforts. I agree with you, I prefer OpenERP SA to spend more time improving the framework and refactoring the code rather than coding a concurrent to a ready-to-use community project. Unfortunately, this is not the first time... I hope this time, they will admit and recognize our work. In a ideal world, I would even dream about OpenERP SA supporting our project as the official Testing system.... I'm happy to ear Cucumber really rocks, even compare to equivalent in Python. Hope this topic will end with OERPScenario & Ooor ! Regards, Joël Le 21 févr. 2010 à 19:47, Raphaël Valyi a écrit : > Hello folks, > > I strongly suggest you look that presentation by a fellow Pythonista that > happened to open his mind to Ruby: > he clearly explains why Python clones of RSpec or Cucumber cannot come close > due to Python LANGUAGE LIMITATIONS (especially after 7'50): > http://blog.extracheese.org/2010/02/python-vs-ruby-a-battle-to-the-death.html > > Now, he first makes a few critics to Ruby that I hope will give him > credibility to you Pythonistas (even if I think myself some of those first > statements are wrong: to me map[non_existing_key] raising an exception in > Python is just one of those unexpected singular cases that break rules where > they don't in Ruby and I think Python has just more of them; as for optional > parenthesis, they are also what makes RSpec/Cucmber and other DSL so powerful > in Ruby...) > > So, I desperately call you to give OERPScenario (Cucumber) a shot because no > matter the efforts you are willing to waste, you will not come close, as > explained in this presentation. So, I rather suggest you picks up that > incredible tool CampToCamp made and use it and rather use your remaining time > refactoring the core of OpenERP for less bugs, rather than trying to make a > clone that will fail to be as powerful. Note that in OERPScenario, you will > only use Cucumber, meaning that even if you would consider valid the critics > against Ruby, they just wouldn't apply as you don't have to write Ruby code > yourself past using the Cucumber/OERPScenario. > > Now, yes, I welcome you to implement YAML as an option for feeding OpenERP > with fixtures/meta parametrization rather than XML (look at HAML > http://haml-lang.com/ if you don't know how to do it for views, everybody I > know that tried it sticked to it and never went back to writing HTML XML by > hand), but this can be added in a backward compatible way, meaning after 5.2 > while lot's of refactoring/bugfix cannot be backward compatible and I suggest > you take car of that first for the 5.2 freeze. I also recall you that for the > test prospective Cucumber/OERPScenario supports YAML out of the box already... > > NB1: notice that what C2C made with OERPScenario on the top of OOOR would > perfectly works with RSpec too for unit testing and low level TDD. > NB2: our TerminatOOOR OOOR based Kettle ETL plugin for OpenERP works like a > charm using laster code/instructions here: > http://github.com/rvalyi/terminatooor I'm just afraid we have no time to > document it further for now. > > Thanks > > Raphaël Valyi > http://www.akretion.com > > > > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-expert-framework > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openerp-expert-framework > More help : https://help.launchpad.net/ListHelp -- Joël Grand-Guillaume Division Manager Business Solutions Camptocamp SA PSE A, CH-1015 Lausanne www.camptocamp.com Phone: +41 21 619 10 28 Office: +41 21 619 10 10 Fax: +41 21 619 10 00 Email: [email protected] http://www.camptocamp.com/fr/business-solutions/formations
_______________________________________________ Mailing list: https://launchpad.net/~openerp-expert-framework Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-expert-framework More help : https://help.launchpad.net/ListHelp
