1. Testing in UP1 Testing as part of the Unified Process (UP)

2. Testing in UP2 Black box vs. white box testing Black box testing –We don’t have / need access to the source code to plan the test White box testing –We have access to the source code when the test is planned.

3. Testing in UP3 Testing use cases Uses cases are an important part of the specification on a UP project Use cases must be tested! Use case –Must be tested by a test case Black box Use case realization –Must be tested by a test case White box

4. Testing in UP4 Testing types Function Testing –Expected results occur when valid data is used User Interface Testing Performance Profiling Data and Database Integrity Testing Performance Profiling Load Testing Volume Testing Security and Access Control Testing Failover / Recovery Testing Configuration Testing Installation Testing Reference http://www.upedu.org/upedu/proce ss/artifact/tmpl_cs/webtmpl/TEST/ upedu_tstpl.htm#_Toc11133133 http://www.upedu.org/upedu/proce ss/artifact/tmpl_cs/webtmpl/TEST/ upedu_tstpl.htm#_Toc11133133

5. Testing in UP5 Workers Who’s involved in testing? Test Manager –Acquire appropriate resources Test Designer –Generate test plan –Generate test model Tester –Execute tests Test System Administrator –Administer test management system Database Administrator –Administer test data Designer –Define test classes Implementer –Create the test classes

6. Testing in UP6 Test coverage Requirements-based Test Coverage Code-based Test Coverage –UP Test evaluation report, page 4 http://www.upedu.org/upedu/process/artifact/ar_tst ev.htmhttp://www.upedu.org/upedu/process/artifact/ar_tst ev.htm

7. Testing in UP7 References Jacobsen, et. al The Unified Software Development Process, Addison Wesley 1999 –Chapter 11 Test, page 295-313 UP Test Plan –http://www.upedu.org/upedu/process/artifact/ar_tstpl. htmhttp://www.upedu.org/upedu/process/artifact/ar_tstpl. htm UP Test Evaluation Report –http://www.upedu.org/upedu/process/artifact/ar_tstev. htm