The most important thing that you have to test your code whatever in which phase,throught the software lifecylcle you need to test your progroam.
The following are getting from the book,just as a remind,when we do the coding ,do not forget to do the test.
Unit tests
Most of us doing this level
Test coverage
This refers to the proportion of application code that is tested (usually, by unit tests). For example,we might aim to check that every line of code is executed by at least one test, or that every logicalbranch in the code is tested.
Black-box testing
This considers only the public interfaces of classes under test. It is not based on knowledge of implementation details.
White-box testing
do not advocate this
Regression tests
These establish that, following changes or additions, code still does what it did before. Given adequate coverage, unit tests can serve as regression tests.
Boundary-value tests
These test unusual or extreme situations that code under test should be able to handle (for example, unexpected null arguments to a method).
Acceptance tests (sometimes called Functional tests)
These are tests from a customer's viewpoint. An acceptance test is concerned with how the application meets business requirements. While unit tests test how each part of an application doesits job, acceptance tests ignore the implementation details and test the ultimate functionality,using concepts that make sense to a user (or customer, in XP terminology)
Load tests
These test an application's behavior as load increases (for example, to simulate a greater population of users). The aim of load testing is to prove that the application can cope with the load
it is expected to encounter in production and to establish the maximum load it can support. Load tests will often be run over long periods of time, to test stability. Load testing may uncover
concurrency issues. Throughput targets are an important part of an application's non-functional requirements and should be defined as part of business requirements.
Stress tests
分享到:
相关推荐
《Expert One on One》是Oracle领域的一本权威学习书籍,专为数据库管理员(DBA)和开发者设计,提供了深入且实践性强的学习资源。这本书的核心目标是帮助读者提升在Oracle数据库管理与开发方面的技能。 首先,Oracle...
《Expert one on one Oracle》是Oracle数据库领域的一本权威著作,深受广大数据库管理员、开发者和IT专业人士的喜爱。这本书深入探讨了Oracle数据库系统的核心概念和技术,旨在帮助读者掌握Oracle的高级特性和最佳...
《Expert One-on-One J2EE Development without EJB》是由Rod Johnson和Juergen Hoeller编写的关于J2EE开发的权威著作。这本书着重讨论了在不使用EJB(Enterprise JavaBeans)的情况下进行J2EE开发的实践和策略,...
《Apress_Expert one on one Oracle》是一本深入探讨Oracle数据库技术的专业书籍,被誉为DBA学习的宝典。本书不仅适合Oracle数据库管理员(DBA),也适用于希望深入了解Oracle数据库架构、性能优化、安全性以及并发...
Expert One-on-One J2EE Development Without EJB中文版.pdf.7z.001 (共3个)
Expert One-on-One J2EE Development Without EJB中文版.pdf.7z.002(共3个)
"Expert One-on-One: J2EE Design and Development" aims to demystify J2EE development. Using a practical focus, it shows how to use J2EE technologies to reduce, rather than increase, complexity. Rod ...
### Expert One-on-One J2EE Design and Development #### 关键知识点概述 《Expert One-on-One J2EE Design and Development》是一本深入探讨Java 2 Platform, Enterprise Edition (J2EE)设计与开发的专业书籍。...
Expert One-on-One J2EE Development Without EJB中文版 一共10个文件,共需资源分:2,第一个和最后一个各1分 欢迎大家下载
中文版EXPERT-ONE-ON-ONE-J2EE-DEVELOPMENT-WITHOUT-EJB.part2.rar
Thomas大师的大作,英文名叫Expert One-On-One Oracle,中文翻译名叫Oracle专家高级编程,袁勤勇、张玉魁翻译,PDF扫描版,有大量SQL*PLUS脚本示例,帮助理解Oracle数据库原理,比Oracle官方文档通俗易懂,无论是...
Expert One-on-One J2EE Development without EJB第三部分
《Expert One-on-One Oracle》是Oracle技术领域里一本极具权威性的著作,由Oracle的大师级人物Thomas Kyte撰写。这本书的中文译名为《Oracle专家高级编程》,为读者提供了深入理解Oracle数据库系统的专业知识和实践...
这是Expert one-on-one Oracle压缩包的第二部分,也是最后一部分,大家用力下吧
大师级书籍的中译本,但是有人评论说翻译的不好,当对于英语不好的来说,总比英文版好吧
Expert one-on-one Oracle一本好书
《Expert One-on-One J2EE Development Without EJB中文版》是一本专为Java EE开发者设计的书籍,旨在探讨如何在不依赖Enterprise JavaBeans (EJB)的情况下进行高效、灵活的J2EE应用开发。该书深入浅出地阐述了EJB...
根据给定文件的信息,我们可以提炼出一系列与Oracle数据库相关的深入知识点,主要涵盖了Oracle数据库的应用开发、架构、锁定与并发控制、事务处理以及重做与回滚等关键领域。以下是详细的知识点总结: ...