On 16/03/10 01:22 +0000, David Lutterkort wrote: >On Mon, 2010-03-15 at 14:17 +0100, [email protected] wrote: >> I finnish revamp of Test::Unit to Cucumber to match >> testing suite used in portal. > >Cool. > >> Basic usage: >> >> rake features >> >> OR: >> >> cucumber features/<feature_name>.feature -q >> >> You don't need to start server or configure something extra. >> Right now, there are two failures: >> >> 1. Image with no name in Mock driver (could be easely fixed in fixtures) >> 2. Device name in one storage volume is empty (not sure about this) > >I get a long list of failures after applying your patch to the HEAD of >master. I've attached the output I get from 'rake features'.
Hmm interesting. Which version of Ruby you are using ? I applied same patch against HEAD and my results seems OK. I used a small method for replacing variables in features with variables from configuration file. Seems like it's something with this method. >Out of curiosity, is there a way to generate pretty HTML output ? >Slogging through the dump on the console seems like a drag. Sure, you could edit Rakefile and replace --format pretty with --format html --out result.html. Or you can do 'cucumber --format html --out result.html' in 'server' directory. HTML output looks much nicer [1] ;-) >> One bonus thing is, that if you have 'rcov' gem installed, >> you will get 'code coverage' generated by this gem in './coverage' >> directory. This could be extra usefull for testing. > >For me, it only worked if I had rcov installed - I agree that it's >useful, but since generating the rcov report takes quite a bit of time, >it should only be done optionally. Good idea. I'll split this into two tasks 'rake features' and 'rake rcow' > >> Second bonus thing is, that these test are configurable. >> Right now there is only configuration for 'mock' driver, >> but with small changes, (hopefully) we will be able to test >> EC2 and other providers using Cucumber as well. > >Any idea how hard it would be to completely stub out the interaction >with the backend cloud for the tests ? For an integration/release test, >we'd definitely want to run them against the actual clouds, but for >individual developers, that takes too long and costs money. Sure, we could talk about creating a mock EC2 driver. But this doesn't change basic concept, which is that you could configure these tests to run against this driver. (or against real EC2, if it's needed) - Michal [1] http://mifo.sk/cucumber.html -- -------------------------------------------------------- Michal Fojtik, [email protected], +420 532 294 4307 Ruby / Ruby On Rails Developer Deltacloud API: http://deltacloud.org -------------------------------------------------------- _______________________________________________ deltacloud-devel mailing list [email protected] https://fedorahosted.org/mailman/listinfo/deltacloud-devel
