1. Agenda for today: The Unified Software Development Process: Test (Note)
The purpose of testing
Artifacts
Test in the sw Life Cycle
Workers
Test procedure

2. The Unified Software Development Process: The purpose of testing
To find errors
To veryfie usecases, design ...

3. The Unified Software Development Process: Test in the sw Life Cycle
Maintain and develop the testmodel throughout the complete software life cycle
Remove obsolete test cases
Redefine some test cases
Create new test cases

4. The Unified Software Development Process: Artifacts
Test model
Test system
Test case
Test
Procedure
Test
Component

5. The Unified Software Development Process: Artifacts
Use Case Model
Test Model
Use Case
Test Case
Black Box Test
Text Case
Use Case
Design
White Box Test

6. The Unified Software Development Process: Other Artifacts
1.1.1  Test Case 1
Verification of the generation of the billing events through the Customer Care interface
The Unified Software Development Process: Other Artifacts
Artifact: Defect
A Defect is a system anomaly (like a sw fault)
Artifact: Evaluate Test

7. The Unified Software Development Process: Other Artifacts
1.1.1  Test Case 1
Verification of the generation of the billing events through the Customer Care interface
The Unified Software Development Process: Other Artifacts
Test the system as a whole
Installation test
Configuration test
Negative test
Stress tests

8. The Unified Software Development Process: Example testcase
Verification of the generation of the billing events through the Customer Care interface
The Unified Software Development Process: Example testcase
1.1. Test Case 1
Verification of the generation of the billing events through the Customer Care interface
In order to perform this test, the web Customer Care GUI has to be used.
An account has to be created in the system. This test case can be performed even if the account has not subscribed to a product.

9. The Unified Software Development Process: Example testcase
Verification of the generation of the billing events through the Customer Care interface
The Unified Software Development Process: Example testcase
Test Step
Input/Action
Expected Output
Result 1
Create an account or look up an existing one.
Use the apposite link to create a billing event.
A billing event is created.
The account balance change reflects the presence of the new billing event
Account balance: an amount is not shown in a proper way. Se screen shot Test Case 1.

10. The Unified Software Development Process: Example testcase
Verification of the generation of the billing events through the Customer Care interface
The Unified Software Development Process: Example testcase

11. The Unified Software Development Process: Example testcase
Verification of the generation of the billing events through the Customer Care interface
The Unified Software Development Process: Example testcase
Test model
Based on a given use-case there is always a related test-case .
E.g.. Use-case Put-Billingevent had an related test-case

12. The Unified Software Development Process: Workers
1.1.1  Test Case 1
Verification of the generation of the billing events through the Customer Care interface
The Unified Software Development Process: Workers
Workers
Test Designer
Component Engineer
Integration Tester
System Tester

13. The Unified Software Development Process: Test procedure
1.1.1  Test Case 1
Verification of the generation of the billing events through the Customer Care interface
The Unified Software Development Process: Test procedure
Activity: Plan Test
Describe a testing strategy.
Estimate the requirements for the testing effort, such as the human an system resources needed.
Scheduling the testing effort.

14. The Unified Software Development Process: Test procedure (V-model)
1.1.1  Test Case 1
Verification of the generation of the billing events through the Customer Care interface
The Unified Software Development Process: Test procedure (V-model)
Start Delivery
Requirement Specification Accept Test
Program Design Integration Test
Module Design Module Test
Module Coding

15. The Unified Software Development Process: Test procedure (Automate)
1.1.1  Test Case 1
Verification of the generation of the billing events through the Customer Care interface
The Unified Software Development Process: Test procedure (Automate)
Test-Driver
Requierments
Test procedure
Module under
test
Test-Stump 1
Test-Stump 2
Test-Stump 3

16. The Unified Software Development Process: Test Procedure
1.1.1  Test Case 1
Verification of the generation of the billing events through the Customer Care interface
The Unified Software Development Process: Test Procedure
In principle there are two ways to test
Incremental test
Top-down or Bottom-up
Total test

17. The Unified Software Development Process: My experiences
1.1.1  Test Case 1
Verification of the generation of the billing events through the Customer Care interface
The Unified Software Development Process: My experiences
Boundary tests
Input field my can only accept positive integers
Test
Input = 0, 1, -1, -1000, -0, Max value, 1.2, 0.1, -0.1

18. The Unified Software Development Process: My experiences
1.1.1  Test Case 1
Verification of the generation of the billing events through the Customer Care interface
The Unified Software Development Process: My experiences
Make sure you know what the result of the test is meant to be.
Plan test in advance
Document your test
Involve the end users in the system test
Be careful to align the users expectations

19. New Way - Accounts