search for: scattershot

hello. first things first - I am new to ruby on rails (ruby, too), so I''m figuring this is just a basic newbie error. I''m creating a basic photography website. And I have two tables with a relationship: photos: - id (set up as PK) - title - shutter - aperture - date - the_order ...etc photo_comments: - id (set up as a PK) - photos_id (set up as a FK) - author - date -

Hi all! Once again, Apple has messed with their trailers/website such that I can no longer play their trailers on Centos 6 (note that it still works fine on my two Fedora machines, F17 and F19, without any special settings. on Centos, I've long ago found that by setting the user agent to certain values I could make it work, but now that no longer helps. when I try to view a trailer all I get

Found this on usenet: August 13, 2001 E-Business Inventors Release Free Alternative To MP3 Music, but Cost Is High By MEI FONG Staff Reporter of THE WALL STREET JOURNAL SOMERVILLE, Mass. -- Christopher Montgomery wants to be the Linus Torvalds of music, the creator of a piece of free software that has the sweeping impact of Mr. Torvalds's Linux operating system. He soon may begin finding

...ting to become what we rely on for correctness, nor what we expect developers (or even most buildbots) to run for correctness. They are slower and problematic in different ways that would slow down our velocity. That sort of coverage should still be carefully chosen for when it adds value, not too scattershot/broad (we have the test-suite for really broad "does this work with the real world" sort of stuff - but anything below that should still be fairly isolated/targeted, I think). - David > > thanks, > > David > > > On Fri, Feb 26, 2016 at 2:15 PM, David Blaikie <db...

...ely on for correctness, nor what we expect developers > (or even most buildbots) to run for correctness. They are slower and > problematic in different ways that would slow down our velocity. > > That sort of coverage should still be carefully chosen for when it adds > value, not too scattershot/broad (we have the test-suite for really broad > "does this work with the real world" sort of stuff - but anything below > that should still be fairly isolated/targeted, I think). > > - David > > >> >> thanks, >> >> David >> >> >&gt...

...ct developers (or even most buildbots) to run for > correctness. They are slower and problematic in different ways that would > slow down our velocity. > That is true and totally fine. > > That sort of coverage should still be carefully chosen for when it adds > value, not too scattershot/broad (we have the test-suite for really broad > "does this work with the real world" sort of stuff - but anything below > that should still be fairly isolated/targeted, I think). > > For the runtime feature owners and developers, those tests are a must -- not that the burden...

...run for >> correctness. They are slower and problematic in different ways that would >> slow down our velocity. >> > > That is true and totally fine. > > >> >> That sort of coverage should still be carefully chosen for when it adds >> value, not too scattershot/broad (we have the test-suite for really broad >> "does this work with the real world" sort of stuff - but anything below >> that should still be fairly isolated/targeted, I think). >> >> > For the runtime feature owners and developers, those tests are a must --...

...are slower and problematic in different ways that would >>> slow down our velocity. >>> >> >> That is true and totally fine. >> >> >>> >>> That sort of coverage should still be carefully chosen for when it adds >>> value, not too scattershot/broad (we have the test-suite for really broad >>> "does this work with the real world" sort of stuff - but anything below >>> that should still be fairly isolated/targeted, I think). >>> >>> >> For the runtime feature owners and developers, those...

Sean and Alexey have said a lot on this topic. Here is my version of explanation that LLVM testing is not suitable to replace end to end testing. - The most important reason being that LLVM tests tend to test 'implementation details'. This has many drawbacks: a) by only writing test cases like this, it is hard to expose bugs inherited in the implementation itself; b) the connection

On Fri, Feb 26, 2016 at 2:10 PM, Alexey Samsonov <vonosmas at gmail.com> wrote: > > On Fri, Feb 26, 2016 at 1:34 PM, David Blaikie <dblaikie at gmail.com> wrote: > >> >> >> On Fri, Feb 26, 2016 at 1:31 PM, Sean Silva <chisophugis at gmail.com> >> wrote: >> >>> >>> >>> On Fri, Feb 26, 2016 at 1:11 PM, David Blaikie