DOCSLIB.ORG

More System Tests Principles of System Testing Sources of Software

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
More System Tests Principles of System Testing Sources of Software CH09: Testing the System More System Tests • to ensure the system does what the customer wants it • * Acceptance Testing to do: • * Installation Testing • * Principles of System Testing • * Automated System Testing • * Function Testing • * Test Documentation • * Performance Testing • * Testing Safety-critical systems • * Reliability, Availability, and Maintainability TECH Computer Science Principles of System Testing Sources of Software Faults Requirement Incorrect, missing or unclear requirements • Sources of Software Faults s Incorrect or unclear translation analysis System • System Testing Process Incorrect or unclear design specification design • Process Objectives Program Incorrect or unclear design specification • Configuration Management design Misinterpretation of system design • Test Team Program Misinterpretation of program design implementation Incorrect documentation Incorrect syntax or semantics Unit/integration Incomplete test procedures testing New faults introduced when old ones correcte System Incomplete test procedures testing Incorrect user documentation Maintenance Poor human factors New faults introduced when old one corrected Changes in requirements System Testing Process Process Objectives System Other Customer User • A function test checks that the integrated system functional software requirementsenvironment requirements requirementsspecification performs its functions as specified in the requirements. • A performance test compares the integrated components with the nonfunctional system requirements, Integrated Function Performance Acceptance Installation SYSTEM 4such as security, accuracy, speed, and reliability modules test test test test IN USE! Functioning Verified, Accepted system validated system software Verified vs. Validated System Tests for Customers • A verified system meets the requirement • An acceptance test assures the system meet the specifications (designer’s view). customers’ satisfaction. • A validated system meets the requirement definitions • An installation test assures the system is installed (customer’s view). correctly and working at the actual customer’s hardware. Configuration Management Version and Release • A system configuration is a collection of system • A configuration for a particular system is sometimes components delivered to a particular customer or called a version. operating system. • A new release of the software is an improved (?) • Configuration management helps us keep track on system intended to replace the old one. the difference system configurations. • A regression test is a test applied to a new version or 4Also keep track of change: called change control release to verify that it still performs the same functions in the same manner as an older one. Tracking the Changes: Deltas, Separate files, and Conditional compilation Test Team • Separate files: Keep separate files for each different • Everybody needs to be involved. version or release. • Developers usually do unit and integration testing. • Deltas: Keep one main version. Other versions are • Testers (testing group) do functional and stored as differences from the main version. The performance tests. difference file is called a delta. • Testers will ask analysts or front-end people to clarify • Conditional compilation: One single code addresses requirements. all version. Use compiler to determine which • Users, technical writers, ... statements apply to which versions. Function Testing Performance Testing • Test what the system is supposed to do based on the • addresses nonfunctional requirements. system’s functional requirements. Test should: • Types include: 4have a high probability of detecting a fault 4Stress tests, Volume tests -- users and data 4use a test team independent of the designers and 4Configuration test -- software and hardware programmers configurations 4know the expected actions and output 4Compatibility test -- between systems 4test both valid and invalid input 4Regression tests -- between versions 4never modify the system just to make testing easier 4Security test 4have stopping criteria Lot more performance tests Reliability, Availability, and Maintainability 4Timing test -- respond time • Definitions 4Environmental test -- perform at installation site • Failure Data 4Quality tests -- reliability, availability • Measuring Reliability, Availability, and 4Recovery tests -- restart Maintainability 4Maintenance tests -- diagnostic tools and tracing • Reliability Stability and Growth 4documentation tests -- e.g. follow the installation guide 4Human factors test, usability tests. • Reliability Prediction • Importance of the operational Environment Definitions More formal definitions • Reliability involves behavior over a period of time. 4Software reliability is the probability that a system will operate without failure under given condition for a give • Availability describes something at a given point in time interval. time. 4Software availability is the probability that a system is • Maintainability describes what need to be done to operating successfully according to specification at a keep the system functioning. given point in time. 4Software maintainability is the probability that a maintenance activity can be carried out within a stated time interval and using stated procedures and resources. Failure Data MTTF, MTTR, MTBF • Reliability, availability, and maintainability are • Mean time to failure (MTTF) is the average value of measured based on the working history of a complete inter-failure times. system. • Mean time to repair (MTTR) is the average value of • Failure data must be kept to allow the measurements: time taking to fix each failure. 4time between each failure (“inter-failure time”) • Mean time between failures (MTBF): 4time for each maintenance • MTBF = MTTF + MTTR Measuring Reliability, Availability, and Maintainability Reliability Stability and Growth • Reliability = MTBF/(1+MTBF) • tell us whether the software is improving • Availability = MTBF/(MTBF + MTTR) • If the inter-failure times stay the same, • Maintainability = 1/(1 + MTTR) • then we have reliability stability!!! • If the inter-failure times increase, • then we have reliability growth (getting better)!!! Reliability Prediction Importance of the operational Environment • Use historical information about failures to build a • Capture operational profile that describes likely user predictive models of reliability. input over time. • = assuming the change in system behavior is the same • e.g. % of create, % of delete, or % of modify used by by fixing one fault as by fixing another a user • - fixing one fault might introduce a lot more fault • (statistical testing) Test cases are created to test them (predictive models can not take account of this according to the %. problem) 4Testing concentrates on the parts of the system most likely to be used 4Reliability from these test gives the reliability as seen by the user. Acceptance Testing Alpha and Beta tests • Now the customer leads testing and defines the cases • In house test is called an alpha test. to be tested. • The customer’s pilot test is called beta test. • Benchmark test uses a set of test cases that represent • Parallel testing: the new system operates in parallel typical conditions of usage. with the previous version. (Something to fall back to • Pilot test installs the system on an experimental basis in case the new one does not work!) and rely on the everyday working of the system to test all functions. Installation Testing Automated System Testing • Final round of testing! • Simulator presents to a system all characteristics of a 4involves installing the system at customer’s sites. device or system without actually having the device • After installation, run regression test (most important or system available. test cases) to insure the software is working “in the • Sometimes a device simulator is more helpful than field”. the device itself. • When the customer is satisfied with the results, • Record and Play-back testing tools to simulate users. testing is complete and the system is formally delivered. • Done for now!!! Test Documentation Test Analysis Report • Test Plans (covered earier) • When a test has been administered, we analyze the • Test Analysis Report results to determine if the function or performance • Problem Report Forms tested meets the requirements. Anaysis Report: 4documets the results of tests 4if a failure occurs, it provides information needed to duplicate the fauilure and to locate and fix the source of the problem. 4provides info to determine if the probject is complete 4establishes confidnece in the system’s performance Problem Report Forms Discrepancy report form • capture data about faults and failures in problem DISCREPANCY REPORT FORM DRF Number:__________________________________________ Tester name:_________________ report forms Date: ___________________________________ Time: ___________________________ Test Number: ______________________________ • discrepancy report form (it is called MR Script step executed when failure occurred: __________________________________________________ Description of failure: _____________________________________________________________________ (modification request) in Lucent) _______________________________________________________________________________________ _______________________________________________________________________________________ 4is a problem report that describes occurrences of _______________________________________________________________________________________
Load more

Recommended publications
  • Studying the Feasibility and Importance of Software Testing: an Analysis
    Dr. S.S.Riaz Ahamed / Internatinal Journal of Engineering Science and Technology Vol.1(3), 2009, 119-128 STUDYING THE FEASIBILITY AND IMPORTANCE OF SOFTWARE TESTING: AN ANALYSIS Dr.S.S.Riaz Ahamed Principal, Sathak Institute of Technology, Ramanathapuram,India. Email:[email protected], [email protected] ABSTRACT Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and coding. Software testing is the process of testing the functionality and correctness of software by running it. Software testing is usually performed for one of two reasons: defect detection, and reliability estimation. The problem of applying software testing to defect detection is that software can only suggest the presence of flaws, not their absence (unless the testing is exhaustive). The problem of applying software testing to reliability estimation is that the input distribution used for selecting test cases may be flawed. The key to software testing is trying to find the modes of failure - something that requires exhaustively testing the code on all possible inputs. Software Testing, depending on the testing method employed, can be implemented at any time in the development process. Keywords: verification and validation (V & V) 1 INTRODUCTION Testing is a set of activities that could be planned ahead and conducted systematically. The main objective of testing is to find an error by executing a program. The objective of testing is to check whether the designed software meets the customer specification. The Testing should fulfill the following criteria: ¾ Test should begin at the module level and work “outward” toward the integration of the entire computer based system.
    [Show full text]
  • Types of Software Testing
    Types of Software Testing We would be glad to have feedback from you. Drop us a line, whether it is a comment, a question, a work proposition or just a hello. You can use either the form below or the contact details on the rightt. Contact details [email protected] +91 811 386 5000 1 Software testing is the way of assessing a software product to distinguish contrasts between given information and expected result. Additionally, to evaluate the characteristic of a product. The testing process evaluates the quality of the software. You know what testing does. No need to explain further. But, are you aware of types of testing. It’s indeed a sea. But before we get to the types, let’s have a look at the standards that needs to be maintained. Standards of Testing The entire test should meet the user prerequisites. Exhaustive testing isn’t conceivable. As we require the ideal quantity of testing in view of the risk evaluation of the application. The entire test to be directed ought to be arranged before executing it. It follows 80/20 rule which expresses that 80% of defects originates from 20% of program parts. Start testing with little parts and extend it to broad components. Software testers know about the different sorts of Software Testing. In this article, we have incorporated majorly all types of software testing which testers, developers, and QA reams more often use in their everyday testing life. Let’s understand them!!! Black box Testing The black box testing is a category of strategy that disregards the interior component of the framework and spotlights on the output created against any input and performance of the system.
    [Show full text]
  • Web Gui Testing Checklist
    Web Gui Testing Checklist Wes recrystallizing her quinone congruously, phytophagous and sulphonic. How imponderable is Schroeder when barbate whileand soft-footed Brewer gliff Zachery some incisure yakety-yak affluently. some chatoyancy? Fulgurating and battiest Nealson blossoms her amontillados refine Wbox aims to the field to be able to the automated support data, testing web gui checklist Planned testing techniques, including scripted testing, exploratory testing, and user experience testing. This gui content will the css or dynamic values? Test all input fields for special characters. For instance, create test data assist the maximum and minimum values in those data field. Assisted by timing testing is not tested to the order to achieve true black art relying on gui testing web checklist will best. The web hosting environments you start all web testing gui checklist can provide tests has had made. The gui testing procedures are the weak factors causing delays in agile here offering, gui testing web? At anytime without giving us a testing web gui checklist can also has on. How gui testing checklist for a gui testing web checklist to induce further eliminating redundant if there is transmitted without the below to use of jobs with. Monkey testing tool that an application or even perform testing web gui changes some test android scripts behind successful only allows an. Discusses the preceding css or if a sql injections through an application penetration testing on gui testing web? How much regression testing is enough? Fully automated attack simulations and highly automated fuzzing tests are appropriate here, and testers might also use domain testing to pursue intuitions.
    [Show full text]
  • Testing Guide 4Deets
    TESTING GUIDE Automated Testing for SuccessFactors Introduction This guide will give you an overview of the different aspects of testing your SuccessFactors environment. As most employees interact in some way or form with the system, it’s crucial to test your system regularly and around crucial events to make sure you provide an excellent employee experience. The following topics will be explored: • Testing During An Implementation • Testing For Configuration Changes • Testing For Quarterly Releases • Manual vs. Automated Testing © 2019 Page | 2 Automated Testing For SuccessFactors Testing During An Implementation During an implementation, testing is critical to make sure the system is designed and configured according to expectations. One of the most known test is User Acceptance Testing (UAT) in which a client signs off that the system works as expected. Before UAT, there are many different tests you would like to perform. These tests are done during different phases of a project. Some only once, others multiple times. Let’s start with looking at what phases there are during a SuccessFactors implementation. This may differ slightly, but all SuccessFactors implementations basically follow the same path. The reason for this is that the Agile methodology, which is the preferred method defined by SAP, needs to be followed by SAP professional services and all the certified implementation partners. This methodology has been proven to be most successful. The Agile methodology is an iterative approach. Iterative approach is a way of breaking down the system development of a large application into smaller chunks. In iterative development, functionality is designed, configured and tested in repeated cycles.
    [Show full text]
  • Software Testing Training Module
    MAST MARKET ALIGNED SKILLS TRAINING SOFTWARE TESTING TRAINING MODULE In partnership with Supported by: INDIA: 1003-1005,DLF City Court, MG Road, Gurgaon 122002 Tel (91) 124 4551850 Fax (91) 124 4551888 NEW YORK: 216 E.45th Street, 7th Floor, New York, NY 10017 www.aif.org SOFTWARE TESTING TRAINING MODULE About the American India Foundation The American India Foundation is committed to catalyzing social and economic change in India, andbuilding a lasting bridge between the United States and India through high impact interventions ineducation, livelihoods, public health, and leadership development. Working closely with localcommunities, AIF partners with NGOs to develop and test innovative solutions and withgovernments to create and scale sustainable impact. Founded in 2001 at the initiative of PresidentBill Clinton following a suggestion from Indian Prime Minister Vajpayee, AIF has impacted the lives of 4.6million of India’s poor. Learn more at www.AIF.org About the Market Aligned Skills Training (MAST) program Market Aligned Skills Training (MAST) provides unemployed young people with a comprehensive skillstraining that equips them with the knowledge and skills needed to secure employment and succeed on thejob. MAST not only meets the growing demands of the diversifying local industries across the country, itharnesses India's youth population to become powerful engines of the economy. AIF Team: Hanumant Rawat, Aamir Aijaz & Rowena Kay Mascarenhas American India Foundation 10th Floor, DLF City Court, MG Road, Near Sikanderpur Metro Station, Gurgaon 122002 216 E. 45th Street, 7th Floor New York, NY 10017 530 Lytton Avenue, Palo Alto, CA 9430 This document is created for the use of underprivileged youth under American India Foundation’s Market Aligned Skills Training (MAST) Program.
    [Show full text]
  • Testing Management Plan
    AHCA Florida Health Care Connections (FX) <<Insert Project Name Here>> Testing Management Plan Version: 300 Date: Month dd, yyyy Author: [Author] Submitted To: AHCA FX Project Management Revision History DATE VERSION DESCRIPTION AUTHOR <<Insert Project Name Here>> Testing MM/DD/YYYY 001 Management Plan first draft version Modifications to the approved baseline version (100) of this artifact must be made in accordance with the Artifact Management Standards. Quality Review History DATE REVIEWER COMMENTS MM/DD/YYYY Agency for Health Care Administration Page ii <<Insert Project Name Here>> Testing Management Plan Table of Contents Section 1 Introduction ............................................................................................................ 1 1.1 Purpose ........................................................................................................................ 1 1.2 Scope Statement .......................................................................................................... 1 1.3 Goals and Objectives ................................................................................................... 2 1.4 Referenced Documents ................................................................................................ 2 Section 2 Roles and Responsibilities .................................................................................... 3 Section 3 Assumptions, Contraints, and Risks ...................................................................... 4 3.1 Assumptions ................................................................................................................
    [Show full text]
  • A Brief Essay on Software Testing
    1 A Brief Essay on Software Testing Antonia Bertolino, Eda Marchetti Abstract— Testing is an important and critical part of the software development process, on which the quality and reliability of the delivered product strictly depend. Testing is not limited to the detection of “bugs” in the software, but also increases confidence in its proper functioning and assists with the evaluation of functional and nonfunctional properties. Testing related activities encompass the entire development process and may consume a large part of the effort required for producing software. In this chapter we provide a comprehensive overview of software testing, from its definition to its organization, from test levels to test techniques, from test execution to the analysis of test cases effectiveness. Emphasis is more on breadth than depth: due to the vastness of the topic, in the attempt to be all-embracing, for each covered subject we can only provide a brief description and references useful for further reading. Index Terms — D.2.4 Software/Program Verification, D.2.5 Testing and Debugging. —————————— u —————————— 1. INTRODUCTION esting is a crucial part of the software life cycle, and related issues, we can only briefly expand on each argu- T recent trends in software engineering evidence the ment, however plenty of references are also provided importance of this activity all along the development throughout for further reading. The remainder of the chap- process. Testing activities have to start already at the re- ter is organized as follows: we present some basic concepts quirements specification stage, with ahead planning of test in Section 2, and the different types of test (static and dy- strategies and procedures, and propagate down, with deri- namic) with the objectives characterizing the testing activity vation and refinement of test cases, all along the various in Section 3.
    [Show full text]
  • Software Engineering
    SOFTWARE ENGINEERING FUNDAMENTALS OF SOFTWARE TESTING Software testing is the evaluation of a system with the intention of finding an error or fault or a bug. It also checks for the functionalities of the system so that it meets the specified requirements. LEARNING OBJECTIVES • To execute a program with the intent of finding an error. • To check if the system meets the requirements and be executed successfully in the intended environment. • To check if the system is “Fit for purpose”. • To check if the system does what it is expected to do. STAGES OF TESTING Various testing is done during various phases of the development cycle such as: Module or unit testing. Integration testing, Function testing. Performance testing. Acceptance testing. Installation testing. UNIT TESTING Unit testing is the testing and validation at the unit level. Unit testing validates and tests the following: Algorithms and logic Data structures (global and local) Interfaces Independent paths Boundary conditions Error handling Formal verification. Testing the program itself by performing black box and white box testing. INTEGRATION TESTING One module can have an adverse effect on another. Sub-functions, when combined, may not produce the desired major function. Individually acceptable imprecision in calculations may be magnified to unacceptable levels. Interfacing errors not detected in unit testing may appear in this phase. Timing problems (in real-time systems) and resource contention problems are not detectable by unit testing. Top-Down Integration The main control module is used as a driver, and stubs are substituted for all modules directly subordinate to the main module. Depending on the integration approach selected (depth or breadth first), subordinate stubs are replaced by modules one at a time.
    [Show full text]
  • Software Testing: Way to Develop Quality Software Product 1Dipti Pawade, 2Harshada Sonkamble, 3Pranchal Chaudhari, 4Shubhangi Rathod 1,2,3Dept
    ISSN : 0976-8491 (Online) | ISSN : 2229-4333 (Print) IJCST VOL . 4, Iss UE SPL - 1, JAN - MAR C H 2013 Software Testing: Way to Develop Quality Software Product 1Dipti Pawade, 2Harshada Sonkamble, 3Pranchal Chaudhari, 4Shubhangi Rathod 1,2,3Dept. of I T, K. J. Somaiya College of Engineering, Mumbai, India 4Dept. of IT, P. I. I. T. M. S. R., Navi Mumbai, India Abstract reaction to the input. The testing is a process of comparing the Software testing is one of the most important phase of software behaviour of the software against oracles principles by which one development life cycle. No one can underestimate the importance can recognize a problem. The good practice is to test software of software testing process on software quality assurance. as early as it has been written. The testing concept is evolved Organization pays 40% of its efforts on testing process. A powerful with time. Table 1 illustrate the concept evolution of testing [1]. testing technique results in reduced software development cost Software testing life cycle comprises of the different phases [2] and time and improved performance. That is why choosing an mentioned in Table 2. appropriate testing technique is very important. In this paper we have discussed various testing approaches and methods, their Table 2: Software Testing Life Cycle peculiarities and finally discussed functional and non-functional Phase Activity testing. Phase I: Software requirements/design is Requirements/ reviewed in detail and basic idea of Keywords Design Review what needs to be tested is derived. Testing Evolution, Software Testing Life Cycle, Testing Approach, Testing Technique, Functional Testing, Non-functional Testing Phase II: Detailed test plan is derived.
    [Show full text]
  • Testing Guidelines
    Guidance Testing Guidelines Purpose This document provides guidelines for testing changes to the BSC Software, Systems and Processes. It also provides a high level view of test procedures that are followed by various parties involved in testing. The management of testing and test deliverables is detailed in the Test Management procedure (Reference 1). The scope of testing for each software release is detailed in the relevant Release Test Strategy document, which is developed by ELEXON and the relevant Service Providers. The scope is agreed by all test participants and captured in the Test Strategy. This document is specifically written as a guideline for testing the BSC Systems. However, the principles described may be used when planning for testing of other software systems. Contents 1. Testing Process Overview ...................................................................................................... 2 2. Application Manager and Developer Testing Overview ........................................................ 4 3. Business Process Operator Testing Overview ....................................................................... 9 4. Terms Used ............................................................................................................................ 13 5. References ............................................................................................................................. 13 6. Appendix A – Test Results ...................................................................................................
    [Show full text]
  • Different Types of Testing
    Different Types of Testing Performance testing a. Performance testing is designed to test run time performance of software within the context of an integrated system. It is not until all systems elements are fully integrated and certified as free of defects the true performance of a system can be ascertained b. Performance tests are often coupled with stress testing and often require both hardware and software infrastructure. That is, it is necessary to measure resource utilization in an exacting fashion. External instrumentation can monitor intervals, log events. By instrument the system, the tester can uncover situations that lead to degradations and possible system failure Security testing If your site requires firewalls, encryption, user authentication, financial transactions, or access to databases with sensitive data, you may need to test these and also test your site's overall protection against unauthorized internal or external access Exploratory Testing Often taken to mean a creative, internal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it Benefits Realization tests With the increased focus on the value of Business returns obtained from investments in information technology, this type of test or analysis is becoming more critical. The benefits realization test is a test or analysis conducted after an application is moved into production in order to determine whether the application is likely to deliver the original projected benefits. The analysis is usually conducted by the business user or client group who requested the project and results are reported back to executive management Mutation Testing Mutation testing is a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected.
    [Show full text]
  • Evaluating Testing with a Test Level Matrix
    FSW QA Testing Levels Definitions Copyright 2000 Freightliner LLC. All rights reserved. FSW QA Testing Levels Definitions 1. Overview This document is used to help determine the amount and quality of testing (or its scope) that is planned for or has been performed on a project. This analysis results in the testing effort being assigned to a particular Testing Level category. Categorizing the quality and thoroughness of the testing that has been performed is useful when analyzing the metrics for the project. For example if only minimum testing was performed, how come so many person-hours were spent testing? Or if the maximum amount of testing was performed, how come there are so many trouble calls coming into the help desk? 2. Testing Level Categories This section provides the basic definitions of the six categories of testing levels. The definitions of the categories are intentionally vague and high level. The Testing Level Matrix in the next section provides a more detailed definition of what testing tasks are typically performed in each category. The specific testing tasks assigned to each category are defined in a separate matrix from the basic category definitions so that the categories can easily be re-defined (for example because of QA policy changes or a particular project's scope - patch release versus new product development). If it is decided that a particular category of testing is required on a project, but a testing task defined for completion in that category is not performed, it will be noted in the Test Plan (if it exists) and in the Testing Summary Report.
    [Show full text]