[活动]迎五一，庆周年，盖高楼(活动结束)

月上百合

数据的一致性，正确性测试        数据类型的字段10进制与16进制的转换的测试
        删除被引用基础数据的测试
        数量的数值是否计算正确的测试
        检查域的长度，是否有字符被截掉？
        检查数字域的最大值和最小值？
        检查数字域是否正确接受负数？
        数据库对数据的存储是否完整？有没有出现字符串被截，数值没有4舍5入等？
         特定数据的格式是否正确？如日期型数据有没有“-”或“/”等分隔符；金额字段的数据有没有每三位数字自动添加“，”分隔符？

witcher2002

软件测试的目的
首先，测试并不仅仅是为了要找出错误。通过分析错误产生的原因和错误的分布特征，可以帮助项目管理者发现当前所采用的软件过程的缺陷，以便改进。同时，这种分析也能帮助我们设计出有针对性地检测方法，改善测试的有效性。

witcher2002

白盒测试

白盒测试是基于代码的测试，测试人员通过阅读程序代码或者通过使用开发工具中的单步调试来判断软件的质量，一般黑盒测试由项目经理在程序员开发中来实现。白盒测试分为动态白盒测试和静态白盒测试
2.1 静态白盒测试
利用眼睛，浏览代码，凭借经验，找出代码中的错误或者代码中不符合书写规范的地方。比如，代码规范中规定，函数必须为动宾结构。

月上百合

新增，搜索，修改，排序，删除，打印等功能点的测试        连续新增，修改，删除的测试
        需求功能是否实现的测试
        新增，修改后，TREEVIEW中数据是否及时更新的测试
        查询条件與新增,修改時,输入单引号及特殊字符进行查询的校验的测试
        修改时编码不能修改的测试
        新增时编码是否需要自动更新的测试
        新增与修改时的校验规则测试见序号3
        用鼠标点击只读域，能否进入？
        当打开窗口时，光标/焦点是否位于第一个可输入域？
        编辑框域Edit Box是否限制了字符的长度？
        使用ALT+TAB组合键从一个应用到另一个应用切换时是否有冲突？
        ID、编号或单据号重复时，是否给出提示？
        排序项目是否正确、全面？
        项目的排列顺序是否与显示的排列顺序一致？
        特定权限人员搜索特定资料的测试
        特定权限人员使用特定功能的测试
        清除数据的测试，即没有基础数据的异常处理的测试
        全部展开树中所有数据，看看滚动条的是否能拖动到树中最低下的数据的测试

月上百合

3        校验规则测试        日期格式是否校验的测试
                小数类数据是否校验的测试
                整数类数据是否校验的测试
                校验提示信息是否正确，触发提示信息的时机是否恰当的测试。
                字母是否校验的测试
                特殊字符是否校验的测试
                邮箱格式是否校验的测试
                数据超长是否校验的测试
                数字最大最小值的校验的测试
                数据是否选择的校验的测试
                数据是否为空的校验的测试
                数据唯一性的校验的测试
                年份最大，最小值校验的测试
                数据被要求范围校验的测试
                定义文件名规则的校验的测试
                上传文件名超长的校验的测试
                上传文件名输入框为单引号的测试
                备注信息最长输入是否校验的测试
                闰年日期是否正确，是否不产生错误和计算误差？
                月份是否只能在1和12之间（包含本身）？
                日期是否只能在1和31之间（包含本身）？
                二月是否有28、29、30日？
                日期的周期性计算是否正确？
                是否有日历选择器？是否与手工输入有冲突？
                除零的情况是否不允许？
                在数字后面带有空格的数字域是否正确接受？
                数据联动性的测试

witcher2002

压力测试，是性能测试的一种，通常是指持续不断的给被测系统增加压力，直到将被测系统压垮为止，用来测试系统所能承受的最大压力。
比如我们不断增加并发的登录用户数，20，30，50…比如，当增加到70个用户并发登录时，系统崩溃了，我们就可以知道163邮箱所能承载的最大登录并发数为70个左右。

witcher2002

压力测试，是性能测试的一种，通常是指持续不断的给被测系统增加压力，直到将被测系统压垮为止，用来测试系统所能承受的最大压力。
比如我们不断增加并发的登录用户数，20，30，50…比如，当增加到70个用户并发登录时，系统崩溃了，我们就可以知道163邮箱所能承载的最大登录并发数为70个左右。

witcher2002

压力测试，是性能测试的一种，通常是指持续不断的给被测系统增加压力，直到将被测系统压垮为止，用来测试系统所能承受的最大压力。
比如我们不断增加并发的登录用户数，20，30，50…比如，当增加到70个用户并发登录时，系统崩溃了，我们就可以知道163邮箱所能承载的最大登录并发数为70个左右。

月上百合

压力测试        系统长时间运行是否会出现死机的现象的测试
        系统长时间运行是否会出现SESSON丢失的现象的测试
        长时间运行，是否会出现连数据库不成功的现象的测试
        大量数据导入导出是否会出现死机的现象的测试
        同时打开多个应用程序的测试的测试

小北ZZ

测试的目标
Myers对测试目标作了如下归纳：
测试是程序的一个执行过程，其目的在于发现错误；
一个好的测试用例在于能找到至今尚末发现的错误；
一个成功的测试是发现了至今尚末发现的错误。

walker1020

What is Regression testing?

Regression testing is any type of software testing which seeks to uncover software regressions. Such regressions occur whenever software functionality that was previously working correctly stops working as intended. Typically regressions occur as an unintended consequence of program changes.

Common methods of regression testing include re-running previously run tests and checking whether previously fixed faults have re-emerged.

walker1020

Background

Experience has shown that as software is developed, this kind of reemergence of faults is quite common. Sometimes it occurs because a fix gets lost through poor revision control practices (or simple human error in revision control), but often a fix for a problem will be "fragile" in that it fixes the problem in the narrow case where it was first observed but not in more general cases which may arise over the lifetime of the software. Finally, it has often been the case that when some feature is redesigned, the same mistakes will be made in the redesign that were made in the original implementation of the feature.

Therefore, in most software development situations it is considered good practice that when a bug is located and fixed, a test that exposes the bug is recorded and regularly retested after subsequent changes to the program. Although this may be done through manual testing procedures using programming techniques, it is often done using automated testing tools. Such a test suite contains software tools that allow the testing environment to execute all the regression test cases automatically; some projects even set up automated systems to automatically re-run all regression tests at specified intervals and report any failures (which could imply a regression or an out-of-date test). Common strategies are to run such a system after every successful compile (for small projects), every night, or once a week. Those strategies can be automated by an external tool, such as BuildBot.

Regression testing is an integral part of the extreme programming software development method. In this method, design documents are replaced by extensive, repeatable, and automated testing of the entire software package at every stage in the software development cycle

莫玉岩

软件评测发展趋势
    测试工作将进一步前移
    软件架构师、开发工程师、QA人员、测试工程题将进行更新的融合
    测试行业将得到充分的尊重
    设置独立的测试部门将得到越来越多公司的软件公司的共识
    测试外包服务将快速增长

walker1020

Regression test generation

Effective regression tests generate sufficient code execution coverage to exercise all meaningful code branches. Therefore, software testing is a combinatorial problem. However, in practice many combinations are unreachable so the problem size is greatly reduced. Every boolean decision statement requires at least two tests: one with an outcome of "true" and one with an outcome of "false". As a result, for every line of code written, programmers often need 3 to 5 lines of test code.

Traditionally, in the corporate world, regression testing has been performed by a software quality assurance team after the development team has completed work. However, defects found at this stage are the most costly to fix. This problem is being addressed by the rise of developer testing. Although developers have always written test cases as part of the development cycle, these test cases have generally been either functional tests or unit tests that verify only intended outcomes. Developer testing compels a developer to focus on unit testing and to include both positive and negative test cases.

When regression test generation is supported by a sustainable process for ensuring that test case failures are reviewed daily and addressed immediately, the end result is a regression test suite that evolves with the application, and becomes more robust and more intelligent each day. If such a process is not implemented and ingrained into the team's workflow, the application may evolve out of sync with the generated test suite — increasing false positives and reducing the effectiveness of the test suite.

Uses

Regression testing can be used not only for testing the correctness of a program, but it is also often used to track the quality of its output. For instance in the design of a compiler, regression testing should track the code size, simulation time and compilation time of the test suite cases.

walker1020

In computer programming, unit testing is a method of testing that verifies the individual units of source code are working properly. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual program, function, procedure, etc., while in object-oriented programming, the smallest unit is a method, which may belong to a base/super class, abstract class or derived/child class.

Ideally, each test case is independent from the others; Double objects like stubs, mock or fake objects as well as test harnesses can be used to assist testing a module in isolation. Unit testing is typically done by software developers to ensure that the code they have written meets software requirements and behaves as the developer intended.

Unit testing is a software development process in which the smallest testable parts of an application, called units, are individually and independently scrutinized for proper operation. Unit testing is often automated but it can also be done manually. This testing mode is a component of Extreme Programming (XP), a pragmatic method of software development that takes a meticulous approach to
building a product by means of continual testing and revision.

Unit testing involves only those characteristics that are vital to the performance of the unit under test. This encourages developers to modify the source code without immediate concerns about how such changes might affect the functioning of other units or the program as a whole. Once all of the units in a program have been found to be working in the most efficient and error-free manner possible, larger
components of the program can be evaluated by means of integration testing.

Unit testing can be time-consuming and tedious. It demands patience and thoroughness on the part of the development team. Rigorous documentation must be maintained. Unit testing must be done with an awareness that it may not be possible to test a unit for every input scenario that will occur when the program is run in a real-world environment.

iori

数据库容量测试指通过存储过程往数据库表中插入一定数量的数据，看看相关页面是否能够及时显示数据。

movestar

软件测试英语

1．静态测试：Non-Execution-Based Testing或Static testing
    代码走查：Walkthrough
    代码审查：Code Inspection
    技术评审：Review
2．动态测试：Execution-Based Testing
3．白盒测试：White-Box Testing
4．黑盒测试：Black-Box Testing
5． 灰盒测试：Gray-Box Testing
6． 软件质量保证SQA：Software Quality Assurance
7． 软件开发生命周期：Software Development Life Cycle
8． 冒烟测试：Smoke Test
9． 回归测试：Regression Test
10．功能测试：Function Testing
11．性能测试：Performance Testing
12．压力测试：Stress Testing
13．负载测试：Volume Testing
14．易用性测试：Usability Testing
15．安装测试：Installation Testing
16．界面测试：UI Testing
17．配置测试：Configuration Testing
18．文档测试：Documentation Testing
19．兼容性测试：Compatibility Testing
20．安全性测试：Security Testing
21．恢复测试：Recovery Testing
22．单元测试：Unit Tes
23．集成测试：Integration Test
24．系统测试：System Test
25．验收测试：Acceptance Test
26．测试计划应包括：
     测试对象：The Test Objectives,
     测试范围： The Test Scope,
     测试策略： The Test Strategy
     测试方法： The Test Approach,
     测试过程： The test procedures,
     测试环境： The Test Environment,
     测试完成标准：The test Completion criteria
     测试用例：The Test Cases
     测试进度表：The Test Schedules
     风险：Risks

27．主测试计划： a master test plan
28．需求规格说明书：The Test Specifications
29．需求分析阶段：The Requirements Phase
30．接口：Interface
31．最终用户：The End User
31．正式的测试环境：Formal Test Environment
32．确认需求：Verifying The Requirements
33．有分歧的需求：Ambiguous Requirements
34．运行和维护：Operation and Maintenance.
35．可复用性：Reusability
36．可靠性： Reliability/Availability
37．电机电子工程师协会IEEE：The Institute of Electrical and Electronics Engineers)
38．要从以下几方面测试软件：
     正确性：Correctness
     实用性：Utility
       性能：Performance
     健壮性：Robustness
     可靠性：Reliability

movestar

下面是一些具体的编写测试代码的技巧或较好的实践方法：
　　1. 不要用TestCase的构造函数初始化Fixture，而要用setUp()和tearDown()方法。
　　2. 不要依赖或假定测试运行的顺序，因为JUnit利用Vector保存测试方法。所以不同的平台会按不同的顺序从Vector中取出测试方法。
　　3. 避免编写有副作用的TestCase。例如：如果随后的测试依赖于某些特定的交易数据，就不要提交交易数据。简单的会滚就可以了。
　　4. 当继承一个测试类时，记得调用父类的setUp()和tearDown()方法。
　　5. 将测试代码和工作代码放在一起，一边同步编译和更新。（使用Ant中有支持junit的task.）
　　6. 测试类和测试方法应该有一致的命名方案。如在工作类名前加上test从而形成测试类名。
　　7. 确保测试与时间无关，不要依赖使用过期的数据进行测试。导致在随后的维护过程中很难重现测试。
　　8. 如果你编写的软件面向国际市场，编写测试时要考虑国际化的因素。不要仅用母语的Locale进行测试。
　　9. 尽可能地利用JUnit提供地assert/fail方法以及异常处理的方法，可以使代码更为简洁。
　　10.测试要尽可能地小，执行速度快。

月上百合

压力测试        系统长时间运行是否会出现死机的现象的测试
        系统长时间运行是否会出现SESSON丢失的现象的测试
        长时间运行，是否会出现连数据库不成功的现象的测试
        大量数据导入导出是否会出现死机的现象的测试
        同时打开多个应用程序的测试的测试

月上百合

状态转换的测试        各个数据状态的限制的测试