Survey: Python vs Ruby Test Ecosystems
1–10 of 16 posts
Re: Survey: Python vs Ruby Test Ecosystems
#2Great idea.
rvm is not a QA tool, by the way; it's a way to manage multiple versions of Ruby.
Re: Survey: Python vs Ruby Test Ecosystems
#3Please post the results later! I don't have experience on both to produce any valuable data to your survey but I'm interested in the results/discussions.
Re: Survey: Python vs Ruby Test Ecosystems
#4Great idea. rvm is not a QA tool, by the way; it's a way to manage multiple versions of Ruby.
If you're developing gems for distribution, it quickly becomes one.
Re: Survey: Python vs Ruby Test Ecosystems
#5Re: Survey: Python vs Ruby Test Ecosystems
#6I recently started developing for Google App Engine after several years working with Rails, and my sense is that Python testing (at least on App Engine) is seriously behind the Ruby/Rails world.
GAE is especially hard to test because you essentially run it in an emulator locally. It's also pretty bare-bones, so you don't get the free testing tools you get with Rails, like fixtures (love 'em or hate 'em, at least they can get you started) and a test runner.
Sure, you can set all that stuff up (and I do) but it sucks having to do a bunch of grunt work that's done for you in Rails.
FWIW, my preferred testing setup in Rails is Shoulda with Mocha for mocking and my own fixie library for pre-populating test data (it's faster than factory_girl) and factory_girl if I find I need it. I think acceptance testing with Cucumber is over rated and I'll be damned if I'm going to program in English, so I do not bother.
For GAE, I'm using gaetestbed and writing a lot of helper functions.
Re: Survey: Python vs Ruby Test Ecosystems
#7I know he made a little "bait" comment but at least he admits the simple inability for python to seriously host DSLs. If you look at any python port of a DSL (sinatra clone, cucumber clone, whatever) it's just simply ugly. It's STILL python code.
Re: Survey: Python vs Ruby Test Ecosystems
#8I recently started developing for Google App Engine after several years working with Rails, and my sense is that Python testing (at least on App Engine) is seriously behind the Ruby/Rails world. GAE is especially hard to test because you essentially run it in an emulator locally. It's also pretty bare-bones, so you don't get the free testing tools you get with Rails, like fixtures (love 'em or hate 'em, at least they…
I don't think it is fair to base your impression on GAE. GAE is a very particular platform.
I am not so familiar with testing for web applications, but nose on python certainly supports test runners, fixtures, etc... I am actually surprised you can get a testing framework without those
Re: Survey: Python vs Ruby Test Ecosystems
#9A common thing I have heard is that Python people are obsessed with documentation and Ruby people are obsessed with testing. Not saying that one or the other is 'better', just that the culture around each of the languages has created these stereotypes.
Re: Survey: Python vs Ruby Test Ecosystems
#10I know he made a little "bait" comment but at least he admits the simple inability for python to seriously host DSLs. If you look at any python port of a DSL (sinatra clone, cucumber clone, whatever) it's just simply ugly. It's STILL python code.
Ruby DSLs still look like Ruby code, too; it just has a laxer lexer. For a reality check, look at DSLs in Forth or Prolog sometime. Many Ruby DSLs are :covered with? accent "marks", though, like Romanized Vietnamese* . You're probably just used to it.