New answers tagged

2

Unit test should be written by developers. Unit test are very close to the core code and developers have intimate knowledge of how units should work. testers are usually more removed from the deep innards of the core code and they will not be ass effective writing unit tests as core developers are. Acceptance/integration/end-to-end test do not require this ...


3

If developers also write unit tests, then what's the point of having special testers in our team and should we replace testers with developers? Unit testing is not the only kind of automated testing. Integration tests, performance tests, scalability tests, and fault tolerance tests are all examples of automated tests that are not unit tests and that a ...


4

The TDD cycle is more a development cycle for a developer, to quote James Shore, The Art of Agile, Test-Driven Development chapter: Programmers new to TDD are often surprised at how small each increment can be. Although you might think that only beginners need to work in small steps, my experience is the reverse: the more TDD experience you have, ...


3

I'd plan it this way: The specific tests that are written 'before the code' are unit tests that are written by developers just before they write the actual code. It should only take 5-20 minutes to write a simple test. The test is written, the code is written for it and then the test is changed or the next test is written and then more unit level code is ...


0

The developers on my team (and the testers as well) generally do exactly this (pull the value we are checking from the config to ensure that the feature works as designed). We also have a suite of configuration unit tests to verify that the values are set as expected for key values. We've enjoyed the benefits you mention in the majority of our tests, while ...


0

When the same value is checked all the time autotest becomes nearly useless (no new knowledge of the product). Unless you check that the default value of timeout is set correctly in config-file. And in this case configuration value could not be used by tests and your devs are right. But you are checking that the timeout works properly so it's not good for ...



Top 50 recent answers are included