News for hackers. Stuff that matters.
Re:100,000 e2e selenium tests? Sounds like a nightmare by falcolas on Wednesday May 14, 2014 @11:21AM (#7744236)
In my experience, if your integration testing is only happy path testing, you're doing integration testing wrong.

Integration testing should, at a minimum, include:

    * Combinatorial testing
      * i.e. testing all possible input combinations for every pair of two inputs
    * Fuzz testing
    * Limit testing
    * Success path testing
    * Failure case testing
Integration testing will discover more component interaction bugs than unit testing alone, and doing only happy path testing is doing it wrong.

On the other hand, I wholly believe that testing done by the developer alone will never catch as many bugs as testing done by both the developer and a QA engineer to the mix will. They think differently than we do, and as such are adept at finding our blind spots.

Re:100,000 e2e selenium tests? Sounds like a nightmare by jameskilton on Wednesday May 14, 2014 @11:30AM (#7744277)
We may have a wording definition issue here. I've heard multiple definitions of "integration tests". I usually use them where some people use "acceptance tests", aka, top-down be-a-user type testing (selenium in Firefox, for example). Sorry if there was any confusion there.

Agreed having a QA team also go through the app is great for finding things that tests can't catch, like usability errors, or crazy edge cases you didn't think about, etc. I have gotten to work with a good QA team and it's amazing the things they find.