Tag Info

New answers tagged

4

Point of testing units and components before whole system is to localize bugs BEFORE they damaged some unrelated part of the system, causing confusing red herring error. If you mock the surroundings of a component, you eliminated moving parts - and localized the bug. Of course you need to weight the effort to mock: because it is code, it will have bugs and ...


0

Usually component testing is before integration testing. I believe first doing component testing and then moving to integration testing will not only save you time but you will be able to find bugs quite early before the integration takes place. Component testing is done with different things in mind and integration testing has a different purpose than ...


2

Actually, we're doing this exact thing you mention. Testing in the same three weeks as development is nefarious for testing time and quality overall, as you seem to have experienced. So, we're testing for two or three weeks after the development sprint has finished. By delaying testing for a few weeks, you'll be working on a fully delivered sprint ...



Top 50 recent answers are included