SystemTestingTestIEN2.docx

1、SystemTestingTestIEN2Department of Information TechnologyQuality Assurance and System TestingICAITT083B Develop and conduct client acceptance testingICAITT084A Perform stress and loading test of an integrated platformICAITB212A Implement quality assurance process for web sitesPrepared by Steven Dimo

2、sTABLE OF CONTENTSTopic 1: Develop criteria Develop standards for the documentation, which will include performance measures, structural quality, content accuracy and consistency- What is system testing? 5- Program development 6- Testing Process 7- What is Quality Assurance? 8 Adopt quality assuranc

3、e with documentation- Testing Templates 9Topic 2: Prepare the test environment Identify acceptance criteria and develop a test plan- Testing 12- Types of testing 12- Example 12- Exercise 14- Levels of testing 14- Other tests 15- White box and black box testing 15 White Box Testing 15 Black Box Testi

4、ng 15- Pseudocode 17- Structured Programming 17- Control Structures 18 The If statement 18 The If-Else statement 19 The While loop 19 The Do While loop 20 The For loop 22- Algorithms 23- Desk checking using a trace table 23- Exercises 25Topic 3: Diagnose and evaluate test results Develop and apply c

5、ontinuous improvement processes- What is continuous improvement? 26- Quality assurance 26- Quality assurance standards 27- Quality management standards 27- The ISO 9000 series of QA standards 28- How to implement a QA system 28- Test compliance matrix 29 Develop and undertake functional test on soft

6、ware- Test strategy 30- Test data 31- The testing process 32- Test cases 31- Test plan 32- Planning and preparing for testing 33 Purpose 33 Objective 33- Design testing approach 34- Planning the test 35 Roles 36- Testing phases 36 Purpose 36 Objectives 36 Activities 36- The plan 37 Track the perform

7、ance against benchmark- Cohesion 38- Types of cohesion 39- Coupling 41- Types of coupling 41- Example 42 Identify discrepancies in results and resolve faults- Testing and debugging 43- What is testing and what is debugging 43- When to test? 43- Types of errors 44- Who tests? 44- Principles of testin

8、g 45- The programming process 46- Example 46- Exercise Plants Are Us 49 Documenting the testing process- System testing 50- Program testing 50- Software Application Testing 52- Seven different types of testing 52 Drivers and stubs 53- Walkthrough 54Topic 4: Sign off system testing Confirm system tes

9、ting with the client- User acceptance review 57- What is acceptance testing? 57- Documentation 58 Appendix A: Example of a Test Plan 60 Appendix B: Solution to the Exercises (on page 25) 65DEVELOP CRITERIATopic 1: Develop criteria Develop standards for the documentation, which will include performan

10、ce measures, structural quality, content accuracy and consistencyWHAT IS SYSTEM TESTING?The purpose of software testing is reliability, which requires error detection and removal. Software testing cannot turn a poorly designed software program into a good one, but it can help determine the level of

11、reliability before the software is released.Software testing is a process that should follow a pattern and well-defined plan. Target software is subjected to test cases and strategies, which generate test results. These test results are evaluated and errors are debugged and correction is made to the

12、 software.The types of errors that testers are likely to encounter are: Fatal Errors, which are of three types:1. Crash, in which the program terminates abnormally.2. Logic, in which a program does not perform a function properly.3. Hang, in which a program or a portion, of the program appears to lo

13、op indefinitely. Serious Errors, which produce incorrect output. Minor Errors, which cause user dissatisfaction.What this means is software testing is the process that should follow a well-defined plan. Testing should subject the target software to test cases and strategies, which generate test resu

14、lts. Test cases are in fact procedures that examine the software and will produce results that will lead to the acceptance, modification or rejection of the software.The areas in which test cases are developed should include: Field Record, the entry, storage, retrieval and processing of records. Fil

15、e, the opening, retrieval, use and closing of files. Data entry, testing for inaccurate, incomplete or obsolete data. Validation is required for the entry of proper data according to design specification. Controls, which check all embedded controls ensuring the accuracy, completeness and authorised

16、processing of transactions. Program flow determines that the software performs sequence, selection and repetition is constructed properly.The quality and efficiency of testing is largely dependent on the development and application of test cases and should adhere to the following format:PROGRAM DEVE

17、LOPMENTA feature of program design is to produce: Small module size, that is, easy to write, test and change. Modular independence, that is, a module does not have to know how another module works (loose coupling).A system is easier to write and test if it is divided into modules. Each module will,

18、eventually, be coded.TESTING PROCESSTesting can be defined as the process of examining a product and then determine what defects it contains, if any. Of course this can only be done once the software has been constructed. The process is:As information system is an integrated collection of software c

19、omponents. Components can be tested individually or in groups and can be correlated to a specific phase of SDLC, that is:Planning for testing can then occur during each phase, for example:An important part of developing tests is specifying test cases and data. A test case is a formal description of:

20、 The starting state One or more events to which the software must respond The expected response or ending stateBoth starting state and event are represented by a set of test data. These will be discussed later in much more detail.QUALITY ASSURANCEQuality Assurance (QA) is the process of ensuring tha

21、t an information system meets minimal quality standards as determined by the user, staff and management. QA is performed throughout the lifecycle of the project so as to ensure that the system has been built correctly from the start or detect the errors as soon as possible.QA activities should be us

22、ed to identify gaps or inconsistencies within the system requirements. The role of QA should enable you in designing and implementing bug free programs. Often a drawback in Quality Assurance is it is overlooked or not a great deal of emphasis is placed on it and this lapse occurs for several reasons

23、, which include: Schedule pressure QA requires development personnel to open their work to thorough examination and criticism by others.By formally integrating QA into a project and scheduling it form the beginning enables QA to be stated, measured and anything within the scope of the project that d

24、oes not meet those standards will then have an impact on both the budget and the schedule.Other reasons for establishing QA in the development processes contributes to the building an environment of openness, and mutual respect amongst project participants. QA enables you to detect during implementa

25、tion phase go through to acceptance testing and in some cases errors are detected after the system becomes operational. Adopt quality assurance with documentationTESTING TEMPLATESTEST DESIGN FORM Test Id:System Name:Test data source:Special requirements:Item for test:Item ID number:Test No.Action to

26、 be takenExpected resultsTest designer:Approved by:Date:Page of MODULE TEST RESULTS FORMClient/System: Version: Module: Run: Testers Name: Page: Signature: Date: TestNumberPassInitialsIncidentNumberTestNumberPassInitialsIncidentNumberTestNumberPassInitialsIncidentNumberMODULE TEST VERIFICATION DETAI

27、LSClient/System: Version: The following modules, which have been tested and signed off by the Module testers, have been reviewed and accepted by:POSITION NAME SIGNATURE DATEProject Leader _ _ _Module NameRunModule TestersNameSignaturePREPARE THE TEST ENVIRONMENTTopic 2: Prepare the test environment Identify acceptance criteria and develop a test planTESTINGTesting is one part of quality assurance, used to determine that standards of corr