when they will only see the number of additional hours that we tack onto dev time in order to complete a assignment?
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Author of <a href="http://www.amazon.com/exec/obidos/ASIN/1932394230/ref=jranch-20" target="_blank" rel="nofollow">JUnit Recipes: Practical Methods for Programmer Testing</a>
Originally posted by J. B. Rainsberger:
Michael:
Like any other new skill, learning to write these tests takes time. However, once you get past the learning curve, our experience shows that writing tests helps us make steady, good progress. The result is fewer defects to the Testing team (saves time), to the customers (saves time and embarrassment), a more maintainable design (saves time on future releases)... the amount of time programmer testing saves far outweights the investment in learning the skill.
The problem is that your managers may be optimizing too small a part of the process. They may continue to pretend that coding, testing and maintenance should be separate phases of a project, rather than ongoing, concurrent activities.
SCJA,SCJP,SCWCD,SCBCD,SCEA I
Java Developer, Thailand
Originally posted by somkiat puisungnoen:
So, this is SAVE Time for developement application but IS NOT SAVE COST for development application OR NOT ???
Because , In project MUST Have Testing Team (This is cost).
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Author of <a href="http://www.amazon.com/exec/obidos/ASIN/1932394230/ref=jranch-20" target="_blank" rel="nofollow">JUnit Recipes: Practical Methods for Programmer Testing</a>
The problem is that your managers may be optimizing too small a part of the process. They may continue to pretend that coding, testing and maintenance should be separate phases of a project, rather than ongoing, concurrent activities.
Yes, you must have a testing team but the amount of work they have to do should be reduced significantly if you can eliminate errors before they are thrown over the wall to the testing team.
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Yes, it is. A big problem.Originally posted by Jeanne Boyarsky:
That wall is another problem.
Originally posted by Jeanne Boyarsky:
If the testing team and development team have different reporting/budget structures, the development manager will not care that you are reducing the amount of work for the testing team.
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
These two teams have a single project manager, a single goal (to get the release out on time, tested)
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Originally posted by Jeanne Boyarsky:
How does that not create a conflict of interest? The testers want to find bugs and the developers want to get the project out. What is the project manager evaluated on? Time? Quality without time? Both?
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
The testers don't want to find bugs.
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Don't get me started about those stupid light bulbs. |