News for hackers. Stuff that matters.
Re:100,000 e2e selenium tests? Sounds like a nightmare by lmm on Wednesday May 14, 2014 @11:54AM (#7744419)
Fair enough - but in that case we're really not talking about the kind of test the grandparent described, the one that looks like

    p = productDao.create("My New Product")
    assert true p.delete()
Re:100,000 e2e selenium tests? Sounds like a nightmare by jameshart on Wednesday May 14, 2014 @05:21PM (#7746525)
The grandparent was pointing out that a unit test like that doesn't give you any confidence in your system precisely because it fails to exercise the broader context - so while it tells you that 'yup, you deleted it', it doesn't tell you that 'other code is now treating it as deleted'. GP was arguing that a unit test was not useful but a functional test was.

You, on the other hand, argued that simple deletion didn't need ANY tests, unit or functional - I was responding with examples that demonstrated that functional integration tests for deletion are perfectly valid.

Re:100,000 e2e selenium tests? Sounds like a nightmare by lmm on Thursday May 15, 2014 @04:39AM (#7748390)
You need to compare apples to apples. An integration test that tests some logic is better than a unit test that doesn't test any logic, duh. But if you're not testing any logic then the test is useless either way. And if you are testing something like cache invalidation, then you can do that just as well, probably better, at the unit level.