search for: mockobjects

CentOS Errata and Bugfix Advisory 2013:0836 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0836.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d4bf3d056da18202bc6f7710d274c1ff2079f9867eb774c40fcfd36ccb9b3be4 perl-Test-MockObject-1.09-4.el6.noarch.rpm x86_64:

Hi I run into problem trying to set expectations for the mockobject.class method, I had to undefine a method before I could set some expectation. Is there any better way of doing it? object = mock() .... klass = class <<object; self; end klass.send(:undef_method, "class") # I had to do this because Mocha utilizes "method_missing(symbol, *arguments, &block) "

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi! Can anybody link to some ror based project what is using rspec, so nuby as me can learn from it. So it should have updated and practising advanced rspec. After reading last threat about "testing behaviour or testing code?", I just realised that I would definitely learn something from app like that. Some casual googling didn''t help me this time. Thanks! Priit at

So far I''ve been doing my controller testing against "real" (testing) objects; however, I''ve been beginning to wonder if I should "default" to using mocks in most cases -- both for performence and to enforce a looser coupling. In part this is driven by my viewpoint that rail''s "functional" tests are still "unit" tests, so they

Hi guys, I''ve just been reading Martin Fowler''s article re mock versus stubbing<http://martinfowler.com/articles/mocksArentStubs.html>where he compares traditional TDD testing techniques with mock based testing. I''d be interested in comments from a ruby on rails perspective in terms of this and Mocha? For example: a) Do you see Mocha as a robust way to test Ruby

Hey Guys, I''m trying to mock the Rails Logger for the following code: ... rescue TimeoutError => error $logger.error("#{self.name} Timeout for #{path}: #{error}") and return rescue SocketError => error $logger.error("#{self.name} SocketError for #{path}: #{error}") and return rescue StandardError => error

Hi First off, I apologise if this is covered somewhere and I just don''t get it... I''ve looked far and wide .... As a part of my current project I need to hook up to a particular XMLRPC webservice that won''t be available for me to use until close to launch date... So I am trying to recreate the webservice that mirrors the live one so I can test my application

...extract the deb packages filenmaes list: find /path/to/Packages.gz -type f -name Packages.gz -exec zcat \{\} + | awk '/^Filename:/{ print $2 } ' > deb-file.list At this point, the deb-file.list will contain a great number of lines like the following: ---------- [snipped] pool/main/m/mockobjects/libmockobjects-java-doc_0.09-5_all.deb pool/main/s/subtitleeditor/subtitleeditor_0.33.0-3_amd64.deb pool/main/h/haskell-hgl/libghc-hgl-prof_3.2.0.5-1_amd64.deb pool/main/l/lsh-utils/lsh-doc_2.1-5_all.deb pool/main/liba/libav/libswscale3_11.3-1_i386.deb pool/main/s/smokeqt/libsmokeqtuitools4-3_4.12....

How would one write a spec on environment.rb in a rails app? I was requiring a gem in environment.rb, but received a "MissingSourceError". Generally, ruby raises a LoadError when it can''t find a gem, but rails overrides this to raise a MissingSourceError (since rails is expecting a required file to be in lib/...). How would I write a spec to override this behavior,

Is it possible to create a stub that returns hash values. For example I would like to convert this: @siteItem = stub(''plmSiteItem'', :one => "uno") To something like this: @siteItem = stub(''plmSiteItem'', {''one'' => ''uno'', ''two'' => ''dos''} ) So that I can do this:

hypothetical question for all you BDD experts: I want to make sure that a :list action always returns widgets in alphabetical order. There''s at least 2 ways of doing this: it "should fetch items in alphabetical order" do Widget.should_receive(:find).with(:order => "name ASC") get :list end it "should fetch items in alphabetical order" do [:red,