Software testing

Software testing目录1. Specialized Unit Testing (3)1.1 mock object(模拟对象) (3)1.2 refactoring(重构) (4)1.3 Roles(角色定义) (5)2. JUnit (6)2.1 What is JUnit (6)2.2 The features of JUnit (6)2.3 What is the test case(测试用例) (6)2.4 Using a test fixture(测试夹具) (7)2.5 JUnit for single tests (7)2.6 What is a TestSuite(测试套件) (8)3. Unit 3 black-box testing (8)3.1 FUNCTIONAL TESTING(功能测试) (8)3.2 STRESS TESTING(压力测试) (8)3.3 LOAD TESTING(负载测试) (9)3.4 AD-HOC TESTING(随机测试) (9)3.5 EXPLORATORY TESTING(探索性测试) (9)3.6 USABILITY TESTING(可用性测试) (10)4. Unit 4 black-box testing (10)4.1 FACTS – TESTING (10)4.2 SMOKE TESTING(烟雾测试) (10)4.3 RECOVERY TESTING(恢复性测试) (11)4.4 VOLUME TESTING(容量测试) (11)4.5 DOMAIN TESTING(域测试) (11)4.6 SCENARIO TESTING(场景测试) (11)4.7 REGRESSION TESTING(回归测试) (12)4.8 USER ACCEPTANCE TESTING(用户验收测试-β测试) (12)4.9 ALPHA TESTING(α测试) (13)4.10 BETA TESTING(β测试) (13)5. Unit 5 white-box testing (13)5.1 What is white-box testing (13)5.2 Advantages and disadvantages of white-box testing (13)5.3 UNIT TESTING(单元测试) (14)5.4 STATIC & DYNAMIC ANALYSIS(静态动态分析) (15)5.5 STATEMENT COVERAGE(语句覆盖) (15)5.6 BRANCH COVERAGE(分支覆盖) (15)5.7 SECURITY TESTING(安全测试) (15)5.8 MUTATION TESTING(变异测试) (15)6. Unit 6 Boundary value analysis and Equivalence partitioning, explained with simple example (15)6.1 Equivalence Partitioning(等价划分) (16)6.2 Boundary value analysis(边界值分析) (16)6.3 Test information flow(测试信息流) (16)6.4 Loop Testing(循环测试) (17)6.5 Black box testing tries to find errors in the following categories (17)7. Testing for Real-Time Systems (18)7.1 What is Real-time Systems(实时系统) (18)7.2 Automated Testing Tools(自动化测试工具) (18)7.3 Criteria for Completion Testing(测试完成标准) (19)1. Specialized Unit Testing1.1 mock object(模拟对象)1. What is mock objectA mock object is, as the name implies, a simulation of some real object. In Java, a mock object would typically be an implementation, with very limited functionality, of an Interface. Mock objects play a significant role in unit testing, for a number of reasons.2. Why we make mock objectYou'd consider using a mock object for your unit test if the real object has a complex set-up, uses many system resources (like CPU power), or doesn't yet exist!If you're writing an application that uses a database, there's no need to wait for the team that develops the database modules before you start coding the rest of the application. What you need is a mock object that behaves like the database modules. If you have interfaces defined to the database modules you're ready to go. Coding with these interfaces might even bring some problems in the Interface design to the surface before the coding of the database modules has even started!Unit testing has become widely accepted as a "best practice" for software development. When you write an object, you must also provide an automated test class containing methods that put the object through its paces, calling its various public methods with various parameters and making sure that the values returned are appropriate.(在编写对象的同时，要提供验证该对象的测试类，该测试类要能够调用该对象的所有公共方法和属性。

)When you're dealing with simple data or service objects, writing unit tests is straightforward. However, many objects rely on other objects or layers of infrastructure. When it comes to testing these objects, it is often expensive, impractical, or inefficient to instantiate(实例化) these collaborators(协作者).For example, to unit test an object that uses a database, it may be burdensome to install, configure, and seed a local copy of the database, run your tests, then tear the local database down again. Mock objects provide a way out of this dilemma.A mock object conforms to the interface of the real object, but has just enough code to fool the tested object and track its behavior. For example, a database connection for a particular unit test might record the query while always returning the same hardwired result.As long as the class being tested behaves as expected, it won't notice the difference, and the unit test can check that the proper query was emitted.3. Mock in the middleThe common coding style for testing with mock objects is to:Create instances of mock objectsSet state and expectations in the mock objectsInvoke domain code with mock objects as parametersVerify consistency in the mock objects1.2 refactoring(重构)Reference:重构（Refactoring）就是在不改变软件现有功能的基础上，通过调整程序代码改善软件的质量、性能，使其程序的设计模式和架构更趋合理，提高软件的扩展性和维护性. Cleaning up code, perhaps by moving a field from one class to another, pushing some code up or down a hierarchy. Most often it is the process of splitting out repetitive code to turn it into its own separate method.A refactoring is a code change that leaves the original functionality intact(破坏了原来功能的完整性), but changes the design of the code so that it's cleaner, more efficient, and easier to test. Refactoring is not always desirable(可取的), nor does it always result in code that is cleaner or easier to understand. In many cases, changing the method signature so the collaborator becomes a parameter will result in a confusing, untested snarl of code inside the method's original callers.Problem: The object being tested creates a collaborator object. This collaborator must be replaced with a mock object.(正在被测试的对象创建了一个协作对象，这个协作对象必须被虚拟对象所替换)class Application {...public void run() {View v = new View(); //创建了一个协作对象，这个对象必须被mock对象所替换v.display();...}}Solution: Extract the creation code into a factory method, override this factory method in a test subclass, and then make the overridden method return a mock object instead. Finally, if practical, add a unit test that requires the original object's factory method to return an object of the correct type:【将创建代码提取到一个工厂方法, 在测试子类覆盖这个工厂方法,然后让重写的方法返回一个mock对象。