我的建议是,你应当拥有自动化和人工测试的健康组合。

www.un.org/Depts/DGACM/index_spanish.htm 缩略语

• Unit Testing
  Use NUnit to test your classes, functions and interaction between them.
  http://www.nunit.org/index.php

• Automated Functional Testing
  If it s possible you should automate a lot of the functional testing. Some frame works have functional testing built into them. Otherwise you have to use a tool for it. If you are developing web sites/applications you might want to look at Selenium.
  http://www.peterkrantz.com/2005/selenium-for-aspnet/

• Continuous Integration
  Use CI to make sure all your automated tests run every time someone in your team makes a commit to the project.
  http://martinfowler.com/articles/continuousIntegration.html

MANUAL TESTING
As much as I love automated testing it is, IMHO, not a substitute for manual testing. The main reason being that an automated can only do what it is told and only verify what it has been informed to view as pass/fail. A human can use it s intelligence to find faults and raise questions that appear while testing something else.

• Exploratory Testing
  ET is a very low cost and effective way to find defects in a project. It take advantage of the intelligence of a human being and a teaches the testers/developers more about the project than any other testing technique i know of. Doing an ET session aimed at every feature deployed in the test environment is not only an effective way to find problems fast, but also a good way to learn and fun!
  http://www.satisfice.com/articles/et-article.pdf

个人经验显示,最受欢迎的办法根本就没有。

我先与TDD(试验推动发展)合作,我对它的看法好坏参半。 基本上,你在撰写你的法典之前写了你的测试,并写了你的法典,以满足测试的要求。 贸易和发展会议迫使你在开始之前对你的要求有一个极为明确的想法。 另一项好处是,一旦你做好了发展工作,假定你密切关注TDD程序,你就拥有一整套符合该守则的测试程序。 倒数的方面是,它需要很长的时间,有时,你只想绕过几个步骤(例如,也许在像病人喜欢做这样的测试之前撰写法典)。

更多内容可读到here(wikilink)。

单位测试?

以合同为基础的方案拟定工作,即:

缺水模式

不同的商店做的是不同的事。 如果有一个办法来统治他们,那么你不会问这个问题。

在进行测试的前提下,我要说,与Junnit进行测试是 Java进行检测的共同办法。

虽然大多数测试都是与JUSG进行的,但大多数测试往往比单位测试更具融合性测试。 (不是孤立地检验一件事,而是一起检验一件事)

此外,试验大多不是在试验第一方法中写成的,而是在具体特征实施后同时进行。

如果你去一个能够更先进地利用测试的团队,你可能发现一些 CI服务器(Cruise Control, Hudson)在夜间施工期间至少每天操作一次测试。

按照最常用的方法顺序:

1. no tests at all
2. manual tests: running the app, clicking or providing input, check results
3. try to write some JUnits, forget about them, slide to 2 and 1
4. Start with TDD, see that it s hard then slide to 3, 2 and 1

on the theoretical side there are loads of ways to properly test the code. If you are looking for something practical take a look at Clean Code Talk. Take a look at the whole series, about 5 talks (can t post more than one link).

我建议对“java”项目进行测试,以保持简单。

Steps :- Manual Testing :-Achieve a stable product. Automation Testing :- Maintain the quality of the product. Report Generation and reporting :- Let people know the quality of the product. Continuous Integration :-Make it a complete automated,continuous tool.

当开发商履行功能时,便开始按模块对其模块进行测试。 将实际产出与预期产出进行比较,并与这些产出进行比较。

当开发商解决有关问题时,《融合测试标准》也开始测试已解决的国家问题,并检查是否由于发行信用卡而出现倒退。

At last when product become the stable one,Then start for automating the the modules. You can also follow automation step by step like:- 1.Automating the modules. 2.Report generation and send mail for product HealthCheck. 3.Continuous Integration and Automation testing on private server on local machine.