search for: shoulds

One of the things that turned me on to BDD and RSpec was speccing views first, that the desired end would drive the development. In previous projects while using Test::Unit I would try to make educated guesses as to what would be needed in the model and controllers to derive the view without actually writing the view until afterwards. This is all because testing relied on each previous

Hi, I am trying to use Rspec together with FunFX for Flex testing. To ease the number of tests and the functionality each test does, I would like to run all the it "shoulds..." in sequence. This works just fine, but the creation of FunFX is created after each it "should..." and no wonder since I create it in the before method. But my question is where should I put the two lines of code that creates an instance of FunFx so that all the it "should...

...????? ... ????? idmap config * : backend = tdb ????? idmap config * : range 10000-199999 ????? idmap config DOMAIN : backend = autorid ????? idmap config DOMAIN : range = 200000-2147483647 ??? Ensure the BUILTIN\Guests is mapped ??? Raw ??? net groupman list sid=S-1-5-32-546 Does not bother me shoulds and shouldnots, I'm doing it, and facing a problem which I'd hope can be solved without changing a lot. User db is in LDAP and winbind is not used. many thanks, L.

Sorry, lots of questions these days. Is there a normal approach for preconditions? In JUnit, I might put a few assertions in the setUp() just to make sure that the test ''data'' I''ve created meets expectations before going to test it. So, for instance, I''ve got an object that is audited using acts_as_audited and I''d like to test the XML that results

Many Thanks for your answer. Actually quite a few 'ifs', 'maybes' or 'shoulds'... ;-) I have tried most of them (except liquidsoap). However, even the mentioned apps like RadioDJ or Mixxx do NOT support meta data changes via the encoder (they all use the admin interface)! And as you correctly pointed out: none of the reference encoders support this. Not even the FLAC, O...

(Drats! Jitterbug is playing tricks with the PR# again. Attempting to refile so that we can kill PR#10509) Peter Dalgaard wrote: > Kurt.Hornik at wu-wien.ac.at wrote: > =20 >> ------- Start of forwarded message ------- >> Date: Tue, 13 Nov 2007 21:44:57 +0100 >> To: Steve Mongin <sjm at ccbr.umn.edu> >> Cc: cran at r-project.org >> Subject: Re: range(

...; ????? idmap config * : range 10000-199999 > ????? idmap config DOMAIN : backend = autorid > ????? idmap config DOMAIN : range = 200000-2147483647 > > ??? Ensure the BUILTIN\Guests is mapped > ??? Raw > > ??? net groupman list sid=S-1-5-32-546 > > > Does not bother me shoulds and shouldnots, I'm doing it, and > facing a problem which I'd hope can be solved without > changing a lot. User db is in LDAP and winbind is not used. > many thanks, L. > > > any experts roaming around? To make it a bit bizarre - it only happens to one of the three Samba...

hi everyone, I believe a resolution is there - https://access.redhat.com/solutions/4367771 But what I'm hoping for is an expert would comment how would this apply to Samba with LDAP backend? many thanks, L.

...u can try tracktor pro and see how it streams. cause it handles it well: track's info updates in ogg without rupture.. regards renan waves.pw On 15/08/2019 20:48, bn at radio42.com wrote: > Many Thanks for your answer. > > Actually quite a few 'ifs', 'maybes' or 'shoulds'... ;-) > I have tried most of them (except liquidsoap). > However, even the mentioned apps like RadioDJ or Mixxx do NOT support meta data changes via the encoder (they all use the admin interface)! > > And as you correctly pointed out: none of the reference encoders support this....

...e it handles it well: track's info updates in ogg without > rupture.. > > regards > renan > waves.pw > >> On 15/08/2019 20:48, bn at radio42.com wrote: >> Many Thanks for your answer. >> >> Actually quite a few 'ifs', 'maybes' or 'shoulds'... ;-) >> I have tried most of them (except liquidsoap). >> However, even the mentioned apps like RadioDJ or Mixxx do NOT support meta data changes via the encoder (they all use the admin interface)! >> >> And as you correctly pointed out: none of the reference encoder...

...updates in ogg without >> rupture.. >> >> regards >> renan >> waves.pw >> >>> On 15/08/2019 20:48, bn at radio42.com wrote: >>> Many Thanks for your answer. >>> >>> Actually quite a few 'ifs', 'maybes' or 'shoulds'... ;-) I have >>> tried most of them (except liquidsoap). >>> However, even the mentioned apps like RadioDJ or Mixxx do NOT support meta data changes via the encoder (they all use the admin interface)! >>> >>> And as you correctly pointed out: none of the r...

Hey all, I see examples showing up that look like this: describe Thing do before(:each) do @thing = Thing.new end it do @thing.should be_something end end This will produce output like this: Thing - should be something But "it do" is driving me mad :( We need a better word. Of course, ''specify'' has not been completely removed, so you can still do

...o updates in ogg without >> rupture.. >> >> regards >> renan >> waves.pw >> >>> On 15/08/2019 20:48, bn at radio42.com wrote: >>> Many Thanks for your answer. >>> >>> Actually quite a few 'ifs', 'maybes' or 'shoulds'... ;-) >>> I have tried most of them (except liquidsoap). >>> However, even the mentioned apps like RadioDJ or Mixxx do NOT support meta data changes via the encoder (they all use the admin interface)! >>> >>> And as you correctly pointed out: none of the re...

Hi, In the course of some work which I describe below, I have found a very significant difference between the BARK function described in the Vorbis specification and its implementation in libvorbis. In the specificationhttp://xiph.org/vorbis/doc/Vorbis_I_spec.pdf bark(x) = 13.1arctan(.00074x) + 2.24arctan(.0000000185x**2 + .0001x) In the libvorbis code

Hi Philipp, While you might logically/theoretically be right with what you say, it is not really practical and unfortunately not user friendly. Let me try to explain my standpoint: Most users do use ICEcast to stream a continuous stream, e.g. they stream a live DJ or radio program. I.e. they setup a single encoder on a single audio stream. Still this logical stream contains different tracks being

Hi Oleg, On 01/09/14 18:46, Oleg Ranevskyy wrote: > Hi Duncan, > > I looked through the IEEE standard and here is what I found: > > *6.2 Operations with NaNs* > /"For an operation with quiet NaN inputs, other than maximum and minimum > operations, if a floating-point result is to be delivered the result shall be a > quiet NaN which should be one of the input

I''d like to start gathering information/debating on the advantages/disadvantages of using it "should ..." vs other techniques. Dan North explained why we should use should: http://dannorth.net/introducing-bdd/ I used to use it "should ..." for the projects I was on, until I was challenged by a fellow developer who started using it with an active voice. For example