W.C.Uduwela. Dept. of Mathematics & Computer Science

Transcription

1 Software Testing W.C.Uduwela Dept. of Mathematics & Computer Science

2 The image cann ot be displayed. Your compu ter may not have enough memory to open the image, or the image may have been cor rup ted. Restart you r computer, and then open the file again. If the red x still appears, y ou may have to delete the image and then insert it again. To demonstrate to the developer and the Topics customer covered that the software meets its requirements. Two fundamental testing activities Component Testing Interface Testing System Testing Integration Testing Release Testing Performance Testing Goal of Testing process Validation testing Defect testing To discover faults or defects in the software where the behavior of the software is incorrect, undesirable or Testing does not conform to its specification

3 Component testing The Testing Process Testing of individual program components; Identifying defects in components Functions, Objects, Reusable Components Usually the responsibility of the component developer (except sometimes for critical systems); Tests are derived from the developer s experience.

4 Cont System testing Testing of groups of components integrated to create a system or sub-system; The responsibility of an independent testing team; Tests are based on a system specification (Functional and non functional requirement). Sometimes defects missed in components testing can be found in here

5 Testing phases Component testing System testing Software developer Independent testing team

6 "Are we building the right product. The software should do what the user really requires. Software testing process has two distinct goals Validation testing To demonstrate to the developer and the system customer that the software meets its requirements; A successful test shows that the system operates as intended. Defect testing To discover faults or defects in the software where its behavior is incorrect or not in conformance with its specification; A successful test is a test that makes the system perform incorrectly and so exposes a defect in the system.

7 S/W Testing.??? Testing can only show the presence of error not their absence Testing is a process intended to build confidence in the software

8 System testing Involves integrating components to create a system or sub-system. May involve testing an increment to be delivered to the customer (Iterative development) Two phases: Integration testing - the test team have access to the system source code. The system is tested as components are integrated. Release testing - the test team test the complete system to be delivered as a black-box. Acceptance testing

9 Integration testing Involves building a system from its components and testing it for problems that arise from component interactions (testing checks that these component actually work together are called correctly and transfer the right data at the right time across the interface) There are 02 ways: Top-down integration testing Develop the skeleton of the system and populate it with components. Bottom-up integration testing Integrate infrastructure components then add functional components. To simplify error localisation, systems should be incrementally integrated.

10 Up_Integration

11 Incremental integration testing A T1 A T1 A T1 T2 B T2 T2 B T3 B T3 C T3 T4 C T4 D T5 Test sequence 1 Test sequence 2 Test sequence 3

12 Cont Reality is different. The implementation of system features may be spread across a number of components To test a new feature you may have to integrate several different components Therefore repairing an error also difficult Further integrating and testing a new component can change the pattern of already tested component integrations

13 Regression Testing When a new increment is integrate it is important to return the tests for previous increments as well as the new tests that are required to verify the new system function. This is regression testing Expensive process Impractical without some automation support

14 Need to show it delivers the specified functionality, performance and dependability and that it does not fail during normal use. Release testing The process of testing a release of a system that will be distributed to customers. Primary goal is to increase the supplier s confidence that the system meets its requirements. Release testing is usually black-box or functional testing Based on the system specification only; Testers do not have knowledge of the system implementation.

15 Black-box testing Input test da ta Ie Inputs causing anomalous beha viour System Output test r esults Oe Outputs w hich r eveal the pr esence of defects

16 Testing guidelines Testing guidelines are hints for the testing team to help them choose tests that will reveal defects in the system Choose inputs that force the system to generate all error messages; Design inputs that cause buffers to overflow; Repeat the same input or input series several times; Force invalid outputs to be generated; Force computation results to be too large or too small.

17 Testing scenario A student in Scotland is studying American History and has been asked to write a paper on ŌFrontier mentality in the American West from 1840 to 1880Õ.To do this, she needs to find sources from a range of libraries. She logs on to the LIBSYS system and uses the search facility to discover if she can acce ss original documents from that time. She discovers sources in various US university libraries and down loads copies of some of these. However, for one document, she needs to have confirmation from her university that she is a genuine student and that use is for non-commercial purposes. The s tudent then uses the facility in LIBSYS that can request such permission and registers her request. If granted, the document will be down loaded to the registered libraryõs server and printed for her. She receives a message from LIBSYS telling her that she will receive an message when th e printed docu ment is available for collection.

18 System tests 1. Test the login mechanism using correct and incorrect logins to check that valid users are accepted and invalid users are rejected. 2. Test the search facility using different queries against known sources to check that the search mechanism is actually finding documents. 3. Test the system presentation facility to check that information about documents is displayed properly. 4. Test the mechanism to request permission for downloading. 5. Test the response indicating that the downloaded document is available.

19 Use cases Use cases can be a basis for deriving the tests for a system. They help identify operations to be tested and help design the required test cases. From an associated sequence diagram, the inputs and outputs to be created for the tests can be identified.

20 Collect weather data sequence chart :CommsController :WeatherStation :WeatherData request (repor t) acknowledge () repor t () summarise () reply (repor t) send (repor t) acknowledge ()

21 Performance testing Part of release testing may involve testing the emergent properties of a system, such as performance and reliability. Performance tests usually involve planning a Performance tests usually involve planning a series of tests where the load is steadily increased until the system performance becomes unacceptable.

22 Stress testing Exercises the system beyond its maximum design load. Stressing the system often causes defects to come to light. Stressing the system test failure behaviour.. Systems should not fail catastrophically. Stress testing checks for unacceptable loss of service or data. Stress testing is particularly relevant to distributed systems that can exhibit severe degradation as a network becomes overloaded.

23 Component testing Component or unit testing is the process of testing individual components in isolation. It is a defect testing process. Components may be: Individual functions or methods within an object; Object classes with several attributes and methods; Composite components with defined interfaces used to access their functionality.

24 Object class testing Complete test coverage of a class involves Testing all operations associated with an object; Setting and interrogating all object attributes; Exercising the object in all possible states. Inheritance makes it more difficult to design object class tests as the information to be tested is not localised.

25 Weather station object interface WeatherStation identifier repor tweather () calibrate (instruments) test () star tup (instruments) shutdown (instruments)

26 Weather station testing Need to define test cases for reportweather, calibrate, test, startup and shutdown. Using a state model, identify sequences of state transitions to be tested and the event sequences to cause these transitions For example: Waiting -> Calibrating -> Testing -> Transmitting -> Waiting

27 Interface testing Objectives are to detect faults due to interface errors or invalid assumptions about interfaces. Particularly important for object-oriented development as objects are defined by their interfaces.

28 Cont Test cases A B C

29 Interface types Parameter interfaces Data passed from one procedure to another. Shared memory interfaces Block of memory is shared between procedures or functions. Procedural interfaces Sub-system encapsulates a set of procedures to be called by other sub-systems. Message passing interfaces Sub-systems request services from other sub-system.s

30 Interface misuse Interface errors A calling component calls another component and makes an error in its use of its interface e.g. parameters in the wrong order. Interface misunderstanding A calling component embeds assumptions about the behaviour of the called component which are incorrect. Timing errors The called and the calling component operate at different speeds and out-of-date information is accessed.

31 Interface testing guidelines Design tests so that parameters to a called procedure are at the extreme ends of their ranges. Always test pointer parameters with null pointers. Design tests which cause the component to fail. Use stress testing in message passing systems. In shared memory systems, vary the order in which components are activated.

32 Software System Implementation W.C.Uduwela Department of Mathematics and Computer Science

33 Introduction Can be defines with major set of goals associated with it; Making new system available to prepared set of users (Deployment) Positioning on-going support and maintenance of the system within the performing organization (Transition)

34 System Deployment It consists of; Executing all steps need to educate the consumer on the use of the new system Placing the newly developed system in to production (in real time business environment) Confirming that all data required at the start of operations is available and accurate Validating that business system are functioning properly

35 System Transition It support responsibilities involves changing from a system development to a system support and maintenance mode of operation. Ownership also move from project team to the performaing organization

36 System Implementation vs Other phases of SDLC Project issues in other phases that arise have little or no impact on day to day business Any misuse at the system implementation almost certainly translate into direct operational and/or financial impact on the performing org. Therefore careful planning, executing and management of system Implementation activities that the project team can minimize the likelihood of these occurrence

37 Processes of System Implementation Prepare for system Implementation (preparation of production environment and consumer communities) Deploy Software System Transition to Performing Organization

38 Prepare for system Implementation All the possible steps are taken to ensure that the upcoming system deployment and transition occurs smoothly, efficiently, and flawlessly Prepare the consumer by giving training to be positioned them to utilize the system It is essential that everyone involved be absolutely synchronized with the deployment plan and with each other. Performance of the deployment efforts impact Ex: Consumer may experience the new system Technical service and Technical support personnel

39 Deploy Software System All activities required are performed to successfully install the new system and make it available to the consumers This is the culmination of the all prior efforts It may impact the technical, operational and cultural aspects of the organization User training familiarize themselves with the system and will help to establish their expectation regarding what the system will and will not do

40 Cont During deployment, project team members may often be required to work extra hours to meet aggressive timeframes or additional staff may be brought in temporarily to assist with large data entry effort As the system enabled and the project team validates that the application is the performing to expectations there may be times certain system functions seem suspect.

41 Transition to Performing Organization Successfully prepare the performing organization to assume responsibility for maintaining and supporting the implemented software system There should be two team that supporting an operational system and for the new development separately To enable this project team should provide support to the performing organization with a combination of technical documentation, training, and hands-on assistance to enable them t provide an acceptable level of operational support to the consumers

42 Software Maintenance W.C.Uduwela Department of Mathematics and Computer Science

43 Introduction General process of changing a system it has been delivered Change may be Simple change to correct cording errors Correct design error Correct Specification Accommodate new requirements Changes are implemented by Modifying existing system component Adding new component

44 Three types of S/W maintenance Maintenance to repair s/w faults (corrective maintenance) Coding error Cheap to correct Design error more expensive Requirement error most expensive Maintenance to adapt the s/w to a different operating environment (adaptive maintenance) H/W, operating system or support s/w changes Application system able to cope with these environment changes

45 Cont Maintenance to add to or modify the system s functionality (perfective maintenance) This need when the system requirements change in response to organization or business change. Require more effort than others Preventive maintenance Maintenance to increase the software maintainability or reliability to prevent problems in the future

46 Cont There is not a clear-cut distinction between those types of maintenance in practice Maintenance cost as a proportion of development cost vary from one application domain to another Embedded real time system maintenance cost = 4 * ( development cost of it) Cost effective to invest effort in designing and implementing a system to reduce maintenance costs

47 Nature of the Maintenance Phase S/W maintenance cost > ½ (the total s/w development cost) without software maintenance, it is impossible to change the problems within the product after its release Understanding the characteristics (size, age, structure) of software will facilitate maintaining the software more efficiently

48 Maintenance Process Models Different models are required that recognizes the requirement to build maintainability into the system There are four models 1. Boehm s model 2. Obstron s model 3. Iterative enhancement model 4. Reuse oriented model

49 Osborne s model It is concerned with the reality of the maintenance environment Technical problems that arise during maintenance are due to poor communication and control between management It recommends four strategies to address these issues 1. Maintenance requirements need to be included in the change specification. 2. A quality assurance program is required to establish quality assurance requirements. 3. A metrics needs to be developed in order to verify that the maintenance goals have been met. 4. Managers need to be provided with feedback through performance reviews.

50 Iterative Enhancement Model considers that changes made to the system during the software lifetime make up an iterative process This model was adapted from development to maintenance The model has three stages. First, the system has to be analyzed. Next, proposed modifications are classified. Finally the changes are implemented. not effective when the documentation of the system is not complete

51 Reuse Oriented Model It assumes that existing program components could be reused steps for the reuse model are identifying the parts of the old system which have the potential for reuse, fully understanding the system parts, modifying the old system parts according to the new requirements, integrating the modified parts into the new system

52 Software Maintenance Tasks Tasks involved in the software maintenance can be grouped into five categories 1. analysis, 2. design, 3. implementation, 4. testing, 5. documentation

53 Analysis consist of impact analysis, cost benefit analysis Impact analysis and cost benefit analysis consist of analyzing different implementation alternatives and comparing their effect on schedule, cost, and operation Isolation refers to the time spent trying to understand the problem or the proposed enhancements to the system

54 Design consists of redesigning the system based on the understanding of the necessary changes.

55 Implementation entails code and unit testing Unit testing is performed by the maintainer who has made the changes

56 Testing consists of integration, acceptance and regression testing Integration testing refers to the time spent on the integration of the components acceptance testing entails verifying that the changed system adheres to the user requirements Regression testing refers to the time spent ensuring that the changes did not affect the functionality of the other parts of the software

57 Documentation consists of system, user and other documentation System documentation refers to the time spent writing or revising the system description document User documentation entails writing or revising the user s guide and other formal documentation, excluding system documentation. Documentations are very important

58 Computer Aided Software Engineering Tools W.C.Uduwela Dep. Mathematics & Computer Science

59 Introduction In software development organization, the Error ridden, over technique used by each developer could vary budget, late Difficult to integrate system and data or to quickly construct new system Therefore Information System professional suggest to develop common technique standard methodology automated tools CASE

60 CASE: Computer Aided Software Engineering Software Engineers view: Make the life easier Organization view: Improve the quality of the systems developed Increase the speed with which systems are designed and developed Ease and improve the testing process through the use of automated checking Improve the integration of development activities via common methodologies Improve the quality and completeness of documentation Help standardize the development process Improve the management of the project Simplify program maintenance Promote reusability of modules and documentation Improve software portability across environments

61 Purpose of Using CASE To make much easier to perform a single design philosophy within an organization with many projects, systems, and people Because it manage the complexities of Information System and helps assure the quality system are constructed on time and within budget

62 Factors Influencing CASE adaption Expensive technology. Therefore large scale system builders are capable of investing Return on Investment. (Big benefits in the late stage of the SDLC- construction to maintanance) Although CASE supports to reduce the overall process, many users and managers are often discouraged by the long duration of planning, analysis, and design. So interest is low

63 Cont CASE tools Cannot easily share information between tools There is a difficulty provide CASE tools that support all activities of SDLC Adaption of CASE is highly related to the use of a formal systems development process Long term prediction for CASE is very good (Functionality Cost ) CASE tools helps for reengineering and reverse engineering process.

64 Why organizations reject CASE tools Organization does not have standard methodology for developing systems. The high cost of purchasing CASE The high cost of training people Low organizational confidence in the IS dept. to deliver high-quality systems on time and within budget Lack of methodology standards within the organization Viewing CASE as a threat to job security Lack of confidence in CASE products

65 Component of CASE

66 General types of CASE tools Diagramming tools Enable system process, data, and control structures to be represented graphically Computer display Help to prototype how system look and feel Report generator System analyst to identify data requirement and relationships Analysis tools Automatically check for incomplete, inconsistent or incorrect specifications in diagrams forms and reports

67 Cont Central repository Integrated storage of specification, diagrams, reports and project management information Document generator Helps to produce both technical and user documentation in standard format Code generator Enables the automatic generation of program and DB definition code directly from the design documents, diagrams, forms and reports

68 Summary of how CASE is commonly used within each SDLC phase

69 Traditional Vs CASE base development Traditional Emphasis on coding and Testing Paper-based specification Manual coding of programs Manual documenting Intensive software testing Maintain code and documentation

70 Cont CASE based Emphasis on analysis and design Rapid interactive prototyping Automated code generation Automated documentation generation Automated design checking Maintain design specifications

71 CASE diagramming tools

72 Cont

73 CASE Form and Report Generator Tools Two purposes: 1. To create, modify, and test prototypes of computer display forms and reports and 2. To identify which data items to display or 2. To identify which data items to display or collect for each form or report.

74 CASE Analysis Tools Types of analyses vary depending upon the organization's development methodology and the features of the CASE environment in use CASE analysis functions focus primarily on CASE analysis functions focus primarily on data structures and usage and on diagram completeness and consistency

75 CASE Repository integrated CASE tools have a common user interface and can share system representations without systems analysts having to convert between different formats used by different tools. two primary segments: the information repository and the data dictionary. information repository combines information about an organization's business information and its application portfolio and provides automated tools to manage and control access to the repository

76 Cont.. data dictionary is a computer software tool used to manage and control access to the information repository It provides facilities for recording, storing, and It provides facilities for recording, storing, and processing descriptions of an organization's significant data and data processing resources

77 Cont

78 Advantages of a CASE Repository two additional advantages of using a comprehensive CASE repository that relate to project management and reusability

79 CASE Documentation Generator Tools SDLC documentation includes textual descriptions of needs, solution trade-offs, diagrams of data and processes, prototype forms and reports, program specifications, and user documentation including application and reference materials Provide a method for managing the vast amounts of documentation created during SDLC

80 CASE code generation tools Produce high-level program source code from diagrams and forms used to represent the system

81 Emerging Development Tools Object-Oriented Development Tools Evolution and Future of Development Tools