Skip to main content
8 events
when toggle format what by license comment
Jul 29, 2013 at 12:34 comment added BЈовић @Dainius No, they are not opposite. What is a point of writing unit tests for a class which displays a button? You can unit test logic that disables that button, but not the code that displays the button. Regarding DB access, there can be errors, but you should not unit test functions to access the DB.
Jul 29, 2013 at 12:03 comment added Dainius "Yes, you need to unit test every method." and "Unit tests are not for those." are a bit opposite, aren't they? And if we don't need to unit testing database access, does that means there cannot be errors (or just there is no way how to test that?).
Jul 29, 2013 at 9:21 comment added BЈовић @Dainius No, read again. 100% code coverage is not bug free. Yes, you need to unit test every method. Of course, unit testing data base access, GUI, etc makes no sense. Unit tests are not for those.
Jul 29, 2013 at 8:12 comment added Dainius so you say that if I write unit test my code will be completely tested and if all test pass, that of course mean that software is bug free (or at least better). So I just need test every method of my software e.g. "function testSqr() { int a = 3; assertTrue(mySqr(a) == 9); } function mySqr(int a) {return 9;}"
Jul 29, 2013 at 7:40 comment added BЈовић @RobertHarvey Right, but if they want to do BDUF - it is their choice. If you are really doing agile, then you are free to improve their design, and still do TDD.
Jul 29, 2013 at 7:38 comment added Stephen BDUF is generally not compatible with any good development management practices. But it would be possible to do a BDUF project in a TDD fashion. TDD is a technique for authoring better quality software while BDUF is a technique for requirements elicitation. A bad technique, but a technique nonetheless.
Jul 29, 2013 at 6:58 comment added Robert Harvey As I understand it, TDD and BDUF are not generally compatible with each other.
Jul 29, 2013 at 5:44 history answered BЈовић CC BY-SA 3.0