search for: should

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...

...//access.redhat.com/solutions/4367771 > Which is behind a paywall ;-) >> >> But what I'm hoping for is an expert would comment how >> would this apply >> to Samba with LDAP backend? > > What do you mean 'Samba with LDAP backend' ???? > > You really shouldn't be running Samba with LDAP any more > and the problem only occurred on a standalone server and > was fixed here: > https://bugzilla.samba.org/show_bug.cgi?id=13697 > > Rowland > >> >> many thanks, L. >> > > It's not a paywall, suffices to registe...

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,...

(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(

...t.com/solutions/4367771 >> Which is behind a paywall ;-) >>> But what I'm hoping for is an expert would comment how >>> would this apply >>> to Samba with LDAP backend? >> What do you mean 'Samba with LDAP backend' ???? >> >> You really shouldn't be running Samba with LDAP any more >> and the problem only occurred on a standalone server and >> was fixed here: >> https://bugzilla.samba.org/show_bug.cgi?id=13697 >> >> Rowland >> >>> many thanks, L. >>> >> > It's not a p...

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 encode...

...den. As previously outlined, in case of Ogg encapsulation the only specification compliant and reliable way to have metadata is to generate a chained stream in the source client. We understand that for software developers it's inconvenient to implement something differently if it feels like it should be as simple as the other thing, but as an open source project we are limited in the amount of work that we can reasonably take on. Embarking on the endeavour of modifying the stream that is sent by the source client properly, while maintaining consistency is neither enough of a priority, nor feasi...

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 this: describe Thing do before(:each) { @thing...

...den. As previously outlined, in case of Ogg encapsulation the only specification compliant and reliable way to have metadata is to generate a chained stream in the source client. We understand that for software developers it's inconvenient to implement something differently if it feels like it should be as simple as the other thing, but as an open source project we are limited in the amount of work that we can reasonably take on. Embarking on the endeavour of modifying the stream that is sent by the source client properly, while maintaining consistency is neither enough of a priority, nor feasi...

...f)+1e-4f*(n)) You will note that the last term is inside the parentheses of the second arctan function in the specification but outside in the libvorbis implementation. This results in extremely large differences at high frequencies. Which is correct: the specification or the implementation? What should I consider to be the reference Vorbis decoder? Currently I am supposing it to be the vorbisfile_example code in Vorbis but I am rather surprised that while the heavy transcendental functions are in double, many other calculations are only in float. I would have expected a reference decoder to use t...

...he developer who once implemented the admin interface update handling for Ogg/Vorbis streams was indeed very clever and user friendly! Because he implemented a feature which was extremely helpful for all ICEcast users and made life much easier for a lot of broadcasters. And isn’t this something we should aim for: Making the life of the users of our software easier? I am pretty sure, that you will notice, that most of your users who are streaming in the Ogg/Vorbis format will currently use the still existing admin interface for meta data updates! It also exists for MP3 and AAC as you noted, so how...

...n, > > 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 NaNs"/. > > *6.2.3 NaN propagation* > /"An operation that propagates a NaN operand to its result and has a single NaN > as an input should produce a NaN with the payload of the input NaN if > representable in the destination format"./ thanks for fi...

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 instead of: it &...