Our philosophy, time versus money applies to your circumstance as well. The more time that is spent on unit testing, the less likely it is that code will contain bugs after it is released. At the same time, the more time your spend unit testing the less profitable the code is.
We take a more cavalier approach. Our programmers test their own code, pass it off to a fellow programmer for testing, and then a final review and unit test is performed by a supervisor. If all three tests pass, the code is stamped complete and is passed on the end users.
Bugs are an inherent part of programming and must be anticipated as inevitable. No amount of testing can truly guarantee that code is 100% bug free.
Some good methods of avoiding writing bugs are found at this site.
Released software will always contain some bugs, even the big companies like MS, Google and apple can't release without bugs. Ofc you can do lots of thing to prevent it, like unit testing, smoke testingen, stress testuing ect. ect., but there will always be bugs. thats as certain as rain when you'r on holiday in England.
Make sure you discuss stuff like this in the sell proces. For example 3 weeks aftercare(bugs fixed for free), after that the can buy maintaince hours
发布评论
评论（2）
我们的理念“时间与金钱”也适用于您的情况。在单元测试上花费的时间越多，代码发布后包含错误的可能性就越小。同时，花在单元测试上的时间越多，代码的利润就越少。
我们采取更加傲慢的态度。我们的程序员测试自己的代码，将其传递给其他程序员进行测试，然后由主管执行最终审查和单元测试。如果所有三个测试都通过，则代码将被标记为完整并传递给最终用户。
错误是编程的固有部分，必须预见到不可避免的。再多的测试也无法真正保证代码 100% 无错误。
在此站点上可以找到一些避免编写错误的好方法。
http://sites.google.com/site/yacoset /Home/如何避免编写错误
Our philosophy, time versus money applies to your circumstance as well. The more time that is spent on unit testing, the less likely it is that code will contain bugs after it is released. At the same time, the more time your spend unit testing the less profitable the code is.
We take a more cavalier approach. Our programmers test their own code, pass it off to a fellow programmer for testing, and then a final review and unit test is performed by a supervisor. If all three tests pass, the code is stamped complete and is passed on the end users.
Bugs are an inherent part of programming and must be anticipated as inevitable. No amount of testing can truly guarantee that code is 100% bug free.
Some good methods of avoiding writing bugs are found at this site.
http://sites.google.com/site/yacoset/Home/how-to-avoid-writing-bugs
发布的软件总会包含一些bug，即使是微软、谷歌、苹果这样的大公司也不可能发布没有bug的软件。 Ofc 你可以做很多事情来防止它，比如单元测试、冒烟测试、压力测试等。等等，但总会有错误。这就像你在英国度假时下雨一样不可避免。
确保在销售过程中讨论此类内容。例如 3 周的售后服务（免费修复错误），之后可以购买维护时间
Released software will always contain some bugs, even the big companies like MS, Google and apple can't release without bugs. Ofc you can do lots of thing to prevent it, like unit testing, smoke testingen, stress testuing ect. ect., but there will always be bugs. thats as certain as rain when you'r on holiday in England.
Make sure you discuss stuff like this in the sell proces. For example 3 weeks aftercare(bugs fixed for free), after that the can buy maintaince hours