1. System analysis and design
Safaa s.y. dalloul

2. Testing

3. Unit 8: System Acquisition Strategy
Test Planning
Unit Tests
Black-box testing
White-box testing
Integration Tests
User interface testing
Use scenario testing
Data flow testing
system interface
System Tests
Requirements testing
Usability testing
Security testing
Performance testing
Acceptance Tests
Alpha testing
Beta testing

4. Introduction

5. Introduction
Programming and testing are very similar to writing and editing.
The attention paid to testing is justified by the high costs associated with downtime and failures cause by software bugs.
A program is not considered finished until it has passed it's testing.

6. Test Planning

7. Test Planning
Test plan defines a series of tests that will be conducted.
It is impossible to test every possible combination of input and situation; there are simple too many possible combinations.
A really good test would include a test case with nonsensical but potentially valid data.

8. Test Planning
It is dangerous to test early modules without an overall testing plan
It may be difficult to reproduce sequence of events causing an error
Testing must be done systematically and results documented carefully

9. Test Planning Example

10. Unit Tests

11. Unit Tests Unit tests focus on one unit.
Unit tests ensure the module performs its function.
Unit test done after programmers have developed and tested the code.

12. Unit Tests
There are two approaches to unit testing:

13. Unit Tests There are two approaches to unit testing:
This test is for normal unit testing.
This test based on program specifications
Black-box tests treats program as black box
The tester focuses on whether the unit meets the requirements stated in the program specifications

14. Unit Tests There are two approaches to unit testing:
This test is for more complex modules
The test based on program source code
On this test the tester looks inside the program to test its major elements.

15. Integration Tests

16. Integration Tests
Integration tests assess whether a set of modules that must work together do so without errors.
This test conducted after each module have been tested alone

17. Integration Tests User Interface Testing Use Scenario Testing
There are four approaches to integration tests
User Interface Testing
Use Scenario Testing
Data Flow Testing
System Interface

18. Integration Tests User Interface Testing
This test is based on interface design for normal integration tests, so the tester tests each interface function.
Interface testing is done by moving through each and ever menu item in the interface either in a top-down or bottom-up manner.

19. Integration Tests Use Scenario Testing
This test based on use case and scenario
This test conducted when the user interface is important
On use scenario tests the tester tests each use scenario

20. Integration Tests Data Flow Testing
This test based on physical DFDs when the system performs data processing.
On data flow test the tester tests each process in a step-by-step fashion.

21. Integration Tests Data Flow Testing
On this test the entire system begins as a set of stubs. Each unit is added in turn and the results of the unit are compared to the correct result from the test data.

22. Integration Tests System Interface
This test based on physical DFDs when the system exchanges data
System interface testing test the exchange of data with other systems.

23. Integration Tests System Interface
Because data transfers between systems are often automated and not monitored directly by the users, it is critical to design tests to ensure they are being done correctly

24. System Tests

25. System Tests
System tests conducted by analysis to ensure that all system modules are programs are working together without errors.
This test examines how well the system meets business requirements, usability, security, and performance.

26. System Tests Requirements Testing
This test based on system design, unit tests, and integration tests for normal system testing, to be sure that business requirements are met.
This test ensure that changes made as a result of integration testing did not create new errors

27. System Tests Requirements Testing
Testers often pretend to be uninformed users and perform improper actions to ensure the system is immune to invalid actions.

28. System Tests Usability Testing
This test based on interface design and use scenarios when user interface is important
Usability testing tests how convenient the system is to use

29. System Tests Security Testing
Based on infrastructure design when the system is important
Tests disaster recovery and unauthorized access

30. System Tests Performance Testing
Based on system proposal and infrastructure design when the system is important
Examines the ability to perform under high load

31. Acceptance Tests

32. Acceptance Tests
Acceptance tests are done primarily by the users with support from the project team.
The user's perceptions of the new system will be significantly influenced by their experiences during acceptance testing.

33. Acceptance Tests Alpha Testing Test plan source is all of the system.
For normal acceptance testing.
Conducted by users to ensure they accept the system
Alpha tests often repeats the previous tests but are conducted by users themselves to ensure they accept the system.

34. Acceptance Tests Beta Testing
This test conducted by the users without any plan using the real data, through their daily work and activities.
This test performed for critical systems.

35. Finally We Did It

36. Safaa S.y. dalloul
Safaadalloul.wordpress.com
Thank You