DOCSLIB.ORG

HP Functional Testing Software Data Sheet

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
HP Functional Testing Software Data Sheet HP Functional Testing software Data sheet With HP Functional Testing you can automate functional and regression testing for every modern software application and environment, extend testing to a wider range of teams, and accelerate the testing process—so you can improve application quality and still make your market window. Simplifies test creation and HP Functional Testing makes it easy to insert, modify, data-drive, and remove test steps. It features: maintenance • Keyword capabilities: Using keywords, testers HP Functional Testing is advanced, automated can build test cases by capturing flows directly testing software for building functional and regression from the application screens and applying robust test suites. It captures, verifies, and replays user record/replay capturing technology. interactions automatically and helps testers quickly • Automatic updating: With new application builds, identify and report on application effects, while you only need to update one reference in the shared providing sophisticated functionality for tester repository and the update is propagated to all collaboration. The product includes HP QuickTest referencing tests. Professional and all of its add-ins. It is sold stand-alone or as part of the broader HP Unified • Easy data-driving: You can quickly data-drive any Functional Testing solution, which couples object definition, method, checkpoint, and output HP Functional Testing with HP Service Test to value through the integrated data table. address both GUI and non-GUI testing. • Timely advice: In execution mode, a pop-up wizard provides guidance on how to change the test in real time, so the execution doesn’t fail where an application has changed. Figure 1: The Keyword View in HP Functional Testing mirrors the Expert View allowing you to edit scripts from either Expands your modern application • Using the attribute /* notation to identify an object based on an event associated with a testing capabilities web-based object HP Functional Testing provides functional and • Using the new EmbedScript/EmbedScriptFromFile regression test automation for every major software and RunScript/RunScriptFromFile functions to application and environment, including advanced perform operations on, or retrieve data from, the Web 2.0 toolkits, leading Rich Internet Application (RIA) browser pages in your application development technologies, Web services, enterprise resource planning (ERP) and customer relationship In addition, HP Functional Testing supports major management (CRM) applications. applications and environments such as Oracle, SAP, Seibel, Windows® Presentation Foundation, Delphi, The product allows test execution on multiple browsers PowerBuilder, ASP .Net, J2EE, and more. And by and comes with comprehensive support for Web 2.0 upgrading to the HP Unified Functional Testing technologies such as GWT, Dojo, YUI, Silverlight, Flex, solution, you can conduct multi-layer testing for and Ajax. Testers can also provide high-level support both GUI-based applications and non GUI-based for third-party and custom Web controls that are not components in a single test scenario. supported out of the box. The Extensibility Accelerator, a separate utility included with HP Functional Testing, Extends automation testing to more speeds the development of support for additional Web toolkits. teams in your organization New testing capabilities for working with web-based HP Functional Testing empowers more people to objects include: create sophisticated test suites with minimal training. It supports three methods to create and maintain • Recording steps on Mozilla Firefox and using the automated tests: Object property to access the Firefox DOM • Keyword-driven: The Keyword View allows • Instructing HP Functional Testing to identify a Web business analysts to create tests with no object in the application based on its XPath location programming and no scripting skill requirements. or CSS definition 2 Figure 2: The Extensibility Accelerator The user simply selects the application window and • New log tracking functionality helps you work with object names from a dropdown list, picks an action developers to pinpoint the cause of unexpected to perform and data to use. Test plan documentation behavior in your Windows-based application. is created automatically. Role-based reporting • Recording: Testers can create test steps via an HP Functional Testing provides reports that extend to integrated recording capability, document each a broad audience of users and stakeholders. Results step in simple language, and view an integrated are displayed in a set of flexible panes that allow screenshot through the Active Screen feature. users to customize the view for their particular needs, • Scripting: Power users have full access to the and all reports can be exported to PDF, HTML, and underlying test and object properties through an Microsoft® Word documents. Reports include: integrated scripting and debugging environment that • A high-level summary, with multi-level detailed views is synchronized with the Keyword View. including pie charts and statistics for both the current New and inexperienced testers can take advantage of and previous runs, a quick link to the previous run built-in processes to guide the creation of meaningful results, and more. and robust tests; and you can customize the guidance to • The option to customize reports with user-defined fit with your processes. For example, you can manage images and screenshots to facilitate error reproduction. how tests are created, enforce standardized file • A recovery capability for corrupted reports that locations, and implement consistent review processes. saves rerun time due to corrupted report files. Collaborate across workgroups • The ability to include client performance-related HP Functional Testing is specifically designed for errors (example, memory leakage) and link directly collaboration across tester workgroups. from the report to the related test script. • The XML-based Object Repository Manager lets Key features and benefits users collaborate and share application object • Comprehensive Web 2.0 and RIA support with easy definitions, and keeps object-level changes extension to additional technologies and toolkits. synchronized throughout test creation efforts. • Keyword-driven technology for faster test creation, • Users can share function libraries, application asset easier maintenance, and more powerful data-driving. definitions, and data-driven spreadsheets. • Fast, easy access to meta test data such as test flow, • Multiple object repositories are managed with ease to actions, and test assets. facilitate building automated frameworks and libraries. 3 • Smart object recognition for reliable and unattended HP Quality Center test configuration functionality script execution. unbinds data from tests allowing users to share • Objects identified visually based on their location to common data sources across tests, filter data to fit nearby objects enabling reliable identification. testing needs and increase requirements traceability; you can easily increase requirements coverage and • Ability to create consistent, repeatable, standardized traceability by filtering data sets according to test testing practices and shareable assets across teams. requirements and allow reporting on the iteration level. • Ability to handle unforeseen application events facilitates 24x7 testing. Combine automated and manual testing with HP Business Process Testing • Automatic defect reproduction and problem Combining HP Functional Testing with HP Business identification reduces time to resolve defects. Process Testing software provides functional test case • Single-step test creation and test documentation design for both automated and manual testing. HP increases productivity. enables non-technical subject-matter experts (SMEs) to be • Time-saving interface manages test checkpoints and an integral part of the quality optimization process by: output objects, as well as share object repositories. • Automating the creation of test plans and streamlining • Quick test panes make test asset information more test maintenance for application change. visible and easy to access. • Reducing the overhead of automated test • Rapid defect isolation and diagnosis with maintenance and combining test automation and integrated reports. documentation into a single effort. • Unicode support for multi-lingual application testing. • Letting SMEs and business managers measure the quality of application deliverables from abstract Complements other HP Software solutions business definitions defined within the HP Business HP Functional Testing software is fully integrated with Process Testing framework. other world-class solutions from HP Software, giving you access to a comprehensive range of capabilities throughout the application lifecycle. About HP BTO Application Solutions Complete test management with HP Quality Center HP’s application solutions help ensure modernization HP Quality Center provides a centralized, initiatives deliver business outcomes instead of web-based location for complete test management, failing under the burden of outdated, legacy delivery from requirements through tests to defects, with mechanisms. Where rival solutions mistake the real-time traceability and analysis. software development lifecycle for a total picture of the application, HP sees core delivery in the The software allows users to manage, link and trace context of the complete application lifecycle—from test
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]
  • Customer Success Story
    Customer Success Story Interesting Dilemma, Critical Solution Lufthansa Cargo AG The purpose of Lufthansa Cargo AG’s SDB Lufthansa Cargo AG ordered the serves more than 500 destinations world- project was to provide consistent shipment development of SDB from Lufthansa data as an infrastructure for each phase of its Systems. However, functional and load wide with passenger and cargo aircraft shipping process. Consistent shipment data testing is performed at Lufthansa Cargo as well as trucking services. Lufthansa is is a prerequisite for Lufthansa Cargo AG to AG with a core team of six business one of the leaders in the international air efficiently and effectively plan and fulfill the analysts and technical architects, headed cargo industry, and prides itself on high transport of shipments. Without it, much is at by Project Manager, Michael Herrmann. stake. quality service. Herrmann determined that he had an In instances of irregularities caused by interesting dilemma: a need to develop inconsistent shipment data, they would central, stable, and optimal-performance experience additional costs due to extra services for different applications without handling efforts, additional work to correct affecting the various front ends that THE CHALLENGE accounting information, revenue loss, and were already in place or currently under poor feedback from customers. construction. Lufthansa owns and operates a fleet of 19 MD-11F aircrafts, and charters other freight- With such critical factors in mind, Lufthansa Functional testing needed to be performed Cargo AG determined that a well-tested API on services that were independent of any carrying planes. To continue its leadership was the best solution for its central shipment front ends, along with their related test in high quality air cargo services, Lufthansa database.
    [Show full text]
  • Leading Practice: Test Strategy and Approach in Agile Projects
    CA SERVICES | LEADING PRACTICE Leading Practice: Test Strategy and Approach in Agile Projects Abstract This document provides best practices on how to strategize testing CA Project and Portfolio Management (CA PPM) in an agile project. The document does not include specific test cases; the list of test cases and steps for each test case are provided in a separate document. This document should be used by the agile project team that is planning the testing activities, and by end users who perform user acceptance testing (UAT). Concepts Concept Description Test Approach Defines testing strategy, roles and responsibilities of various team members, and test types. Testing Environments Outlines which testing is carried out in which environment. Testing Automation and Tools Addresses test management and automation tools required for test execution. Risk Analysis Defines the approach for risk identification and plans to mitigate risks as well as a contingency plan. Test Planning and Execution Defines the approach to plan the test cases, test scripts, and execution. Review and Approval Lists individuals who should review, approve and sign off on test results. Test Approach The test approach defines testing strategy, roles and responsibilities of various team members, and the test types. The first step is to define the testing strategy. It should describe how and when the testing will be conducted, who will do the testing, the type of testing being conducted, features being tested, environment(s) where the testing takes place, what testing tools are used, and how are defects tracked and managed. The testing strategy should be prepared by the agile core team.
    [Show full text]
  • Functional Testing Functional Testing
    From Pressman, “Software Engineering – a practitionerʼs approach”, Chapter 14 and Pezze + Young, “Software Testing and Analysis”, Chapters 10-11 Today, weʼll talk about testing – how to test software. The question is: How do we design tests? And weʼll start with Functional Testing functional testing. Software Engineering Andreas Zeller • Saarland University 1 Functional testing is also called “black- box” testing, because we see the program as a black box – that is, we ignore how it is being written 2 in contrast to structural or “white-box” testing, where the program is the base. 3 If the program is not the base, then what is? Simple: itʼs the specification. 4 If the program is not the base, then what is? Simple: itʼs the specification. Testing Tactics Functional Structural “black box” “white box” • Tests based on spec • Tests based on code • Test covers as much • Test covers as much specified behavior implemented behavior as possible as possible 5 Why Functional? Functional Structural “black box” “white box” • Program code not necessary • Early functional test design has benefits reveals spec problems • assesses testability • gives additional explanation of spec • may even serve as spec, as in XP 6 Structural testing can not detect that some required feature is missing in the code Why Functional? Functional testing applies at all granularity levels (in contrast to structural testing, which only applies to Functional Structural unit and integration testing) “black box” “white box” • Best for missing logic defects Common problem: Some program logic was simply forgotten Structural testing would not focus on code that is not there • Applies at all granularity levels unit tests • integration tests • system tests • regression tests 7 2,510,588,971 years, 32 days, and 20 hours to be precise.
    [Show full text]
  • Devsecops DEVELOPMENT & DEVOPS INFRASTRUCTURE
    DevSecOps DEVELOPMENT & DEVOPS INFRASTRUCTURE CREATE SECURE APPLICATIONS PARASOFT’S APPROACH - BUILD SECURITY IN WITHOUT DISRUPTING THE Parasoft provides tools that help teams begin their security efforts as DEVELOPMENT PROCESS soon as the code is written, starting with static application security test- ing (SAST) via static code analysis, continuing through testing as part of Parasoft makes DevSecOps possible with API and the CI/CD system via dynamic application security testing (DAST) such functional testing, service virtualization, and the as functional testing, penetration testing, API testing, and supporting in- most complete support for important security stan- frastructure like service virtualization that enables security testing be- dards like CWE, OWASP, and CERT in the industry. fore the complete application is fully available. IMPLEMENT A SECURE CODING LIFECYCLE Relying on security specialists alone prevents the entire DevSecOps team from securing software and systems. Parasoft tooling enables the BENEFIT FROM THE team with security knowledge and training to reduce dependence on PARASOFT APPROACH security specialists alone. With a centralized SAST policy based on in- dustry standards, teams can leverage Parasoft’s comprehensive docs, examples, and embedded training while the code is being developed. ✓ Leverage your existing test efforts for Then, leverage existing functional/API tests to enhance the creation of security security tests – meaning less upfront cost, as well as less maintenance along the way. ✓ Combine quality and security to fully understand your software HARDEN THE CODE (“BUILD SECURITY IN”) Getting ahead of application security means moving beyond just test- ✓ Harden the code – don’t just look for ing into building secure software in the first place.
    [Show full text]
  • Continuous Quality and Testing to Accelerate Application Development
    Continuous Quality and Testing to Accelerate Application Development How to assess your current testing maturity level and practice continuous testing for DevOps Continuous Quality and Testing to Accelerate Application Development // 1 Table of Contents 03 Introduction 04 Why Is Continuous Quality and Testing Maturity Important to DevOps? 05 Continuous Testing Engineers Quality into DevOps 07 Best Practices for Well- Engineered Continuous Testing 08 Continuous Testing Maturity Levels Level 1: Chaos Level 2: Continuous Integration Level 3: Continuous Flow Level 4: Continuous Feedback Level 5: Continuous Improvement 12 Continuous Testing Maturity Assessment 13 How to Get Started with DevOps Testing? 14 Continuous Testing in the Cloud Choosing the right tools for Continuous Testing On-demand Development and Testing Environments with Infrastructure as Code The Right Tests at the Right Time 20 Get Started 20 Conclusion 21 About AWS Marketplace and DevOps Institute 21 Contributors Introduction A successful DevOps implementation reduces the bottlenecks related to testing. These bottlenecks include finding and setting up test environments, test configurations, and test results implementation. These issues are not industry specific. They can be experienced in manufacturing, service businesses, and governments alike. They can be reduced by having a thorough understanding and a disciplined, mature implementation of Continuous Testing and related recommended engineering practices. The best place to start addressing these challenges is having a good understanding of what Continuous Testing is. Marc Hornbeek, the author of Engineering DevOps, describes it as: “A quality assessment strategy in which most tests are automated and integrated as a core and essential part of DevOps. Continuous Testing is much more than simply ‘automating tests.’” In this whitepaper, we’ll address the best practices you can adopt for implementing Continuous Quality and Testing on the AWS Cloud environment in the context of the DevOps model.
    [Show full text]
  • Performance Engineering in Scrum
    PERFORMANCE ENGINEERING IN SCRUM Balasubramanian, Infosys Technologies Limited This paper describes how performance engineering as a software discipline should be planned and executed in an agile development cycle. The intention of this paper is not to explain in detail the agile methodology or Performance engineering, even though it provides a high level description of the same. It is expected that the readers have a basic understanding of agile methodologies and performance engineering. Introduction Agile as a software development methodology is fast becoming a popular approach due to its ability to react to business changes. While there are still fears about adopting an agile approach to software development, the industry is clearly seeing a rise in agile adoption. Every year, thousands of dollars are being spent to fix poorly performing applications. This has made the software industry to relook at the way performance engineering is executed. A more proactive approach to architect and design for performance is now planned than a reactive post-mortem like approach. There needs to be a clear direction in identifying the various activities of performance engineering and executing them in logical sequence during an agile development process. This paper aims at suggesting one such approach by indicating various performance engineering activities across an agile development process. Overview of Agile Traditionally software has been developed using a waterfall approach. While this suited the initial days, as business complications grew and demand for time to market increased, waterfall model did not deliver the required results. Agile methodology was born out the need to respond to rapidly changing business requirements and deliver increments of shippable application with time to market as the primary focus.
    [Show full text]
  • A Confused Tester in Agile World … Qa a Liability Or an Asset
    A CONFUSED TESTER IN AGILE WORLD … QA A LIABILITY OR AN ASSET THIS IS A WORK OF FACTS & FINDINGS BASED ON TRUE STORIES OF ONE & MANY TESTERS !! J Presented By Ashish Kumar, WHAT’S AHEAD • A STORY OF TESTING. • FROM THE MIND OF A CONFUSED TESTER. • FEW CASE STUDIES. • CHALLENGES IDENTIFIED. • SURVEY STUDIES. • GLOBAL RESPONSES. • SOLUTION APPROACH. • PRINCIPLES AND PRACTICES. • CONCLUSION & RECAP. • Q & A. A STORY OF TESTING IN AGILE… HAVE YOU HEARD ANY OF THESE ?? • YOU DON’T NEED A DEDICATED SOFTWARE TESTING TEAM ON YOUR AGILE TEAMS • IF WE HAVE BDD,ATDD,TDD,UI AUTOMATION , UNIT TEST >> WHAT IS THE NEED OF MANUAL TESTING ?? • WE WANT 100% AUTOMATION IN THIS PROJECT • TESTING IS BECOMING BOTTLENECK AND REASON OF SPRINT FAILURE • REPEATING REGRESSION IS A BIG TASK AND AN OVERHEAD • MICROSOFT HAS NO TESTERS NOT EVEN GOOGLE, FACEBOOK AND CISCO • 15K+ DEVELOPERS /4K+ PROJECTS UNDER ACTIVE • IN A “MOBILE-FIRST AND CLOUD-FIRST WORLD.” DEVELOPMENT/50% CODE CHANGES PER MONTH. • THE EFFORT, KNOWN AS AGILE SOFTWARE DEVELOPMENT, • 5500+ SUBMISSION PER DAY ON AVERAGE IS DESIGNED TO LOWER COSTS AND HONE OPERATIONS AS THE COMPANY FOCUSES ON BUILDING CLOUD AND • 20+ SUSTAINED CODE CHANGES/MIN WITH 60+PEAKS MOBILE SOFTWARE, SAY ANALYSTS • 75+ MILLION TEST CASES RUN PER DAY. • MR. NADELLA TOLD BLOOMBERG THAT IT MAKES MORE • DEVELOPERS OWN TESTING AND DEVELOPERS OWN SENSE TO HAVE DEVELOPERS TEST & FIX BUGS INSTEAD OF QUALITY. SEPARATE TEAM OF TESTERS TO BUILD CLOUD SOFTWARE. • GOOGLE HAVE PEOPLE WHO COULD CODE AND WANTED • SUCH AN APPROACH, A DEPARTURE FROM THE TO APPLY THAT SKILL TO THE DEVELOPMENT OF TOOLS, COMPANY’S TRADITIONAL PRACTICE OF DIVIDING INFRASTRUCTURE, AND TEST AUTOMATION.
    [Show full text]
  • Accelerate Software Innovation Through Continuous Quality
    Accelerate Software Innovation Through Continuous Quality 1 Software quality is recognized as the #1 issue IT executives are trying to mitigate. Enterprise organizations strive to accelerate the delivery of a compelling user experience to their customers in order to drive revenue. Software quality is recognized as the #1 issue IT executives are trying to mitigate. QA teams know they have issues and are actively looking for solutions to save time, increase quality, improve security, and more. The most notable difficulties are in identifying the right areas to test, the availability of flexible and reliable test environments and test data, and the realization of benefits from automation. You may be facing many challenges with delivering software to meet the high expectations for quality, cost, and schedule driven by the business. An effective software testing strategy can address these issues. If you’re looking to improve your software quality while achieving your business goals, Parasoft can help. With over 30 years of making testing easier for our customers, we have the innovation you need and the experience you trust. Our extensive continuous quality suite spans every testing need and enables you to reach new heights. 3 QUALITY-FIRST APPROACH You can’t test quality into an application at the end of the software development life cycle (SDLC). You need to ensure that your software development process and practices put a priority on quality- driven development and integrate a comprehensive testing strategy to verify that the application’s functionality meets the requirements. Shift testing left to the start of your development process to bring quality to the forefront.
    [Show full text]
  • API Testing Guide an Automated Approach to API Testing Transformation
    API Testing Guide An automated approach to API testing transformation. From Monolith to Microservice The consumerization of IT has changed the way we write applications today. Instead of building a single, monolithic system that is installed on a server in a back office or call center, modern When testing APIs, testers are faced with applications are scattered within mobile devices and web browsers numerous discrete units of work. Some so users can gain access to services at anytime from anywhere. of these APIs may have been created by a third party, while the possible And modern applications are no longer self-contained; they are ordering and combinations of different composed of multiple service components that are tied together versions of APIs can cause the number of at runtime. Therefore, the end-user experience is not powered by combinations that need to be tested to the elegant UIs we all use, but by APIs that facilitate interactions skyrocket to an impossible number. between code modules, applications and back-end IT systems. The ability to identify these combinations Because of this, the way we test must change. Quality assurance and then reduce them to a realistic (QA) and development teams must expand their capacity to test number without compromising quality each layer of the application, as well as the end-to-end business requires testers to adopt a transactions. Modern applications then require comprehensive API new model-based approach and invest in testing in addition to traditional UI testing. But API testing presents automation technologies. many challenges for testers. It requires a new approach—one that is automated wherever possible and inherently data-driven.
    [Show full text]
  • Continuous Testing
    THE ULTIMATE GUIDE TO CONTINUOUS TESTING Everything you need to know to shift-left testing and reach testing maturity CONTINUOUS TESTING: TODAY’S GOLDEN STANDARD At Abstracta, we believe that Agile development, There are several software quality assurance activi- along with the practices that it promotes such as ties to focus on that will help you in your efforts to continuous integration, continuous testing and reach an efficient continuous integration environ- continuous delivery (CI/CT/CD), is the key to remai- ment, allowing for the quality checks you want to ning competitive in today’s technological landscape. have in each build. For an Agile environment to flourish in your organi- In this guide, we will tackle the various areas in zation, testing needs to happen earlier on in develo- which we can group these activities so you may pment than it does in traditional development envi- have a clear picture of what your team must work ronments like waterfall. We call this “shift-left on in order to make progress in your testing matu- testing” and it’s imperative for Agile teams to truly rity and, ultimately, reach continuous testing! succeed. Let’s Begin! TABLE OF CONTENTS ABOUT THE AUTHOR Introduction Federico Toledo is a co-founder and director of Abstracta and holds a PhD in The Source Code Computer Science from UCLM, Spain. Environments and Infrastructure With over 10 years of experience in quality engineering, he's helped many companies Bug and Incident Management to successfully improve their application Test Management quality. He is dedicated to testing educa- Functional Testing tion, having written one of the first books in Spanish on testing and formed Abstrac- Test Automation ta Academy.
    [Show full text]
  • Intro to Software Testing
    Introduction to Software Testing CS 3250 Software Testing [Ammann and Offutt, “Introduction to Software Testing,” Ch. 1, Ch. 2.1] Fall 2021 – University of Virginia © Praphamontripong 1 Bug? “ ‘Bug’ – as such little faults and difficulties are called – show themselves, and months of anxious watching, study, and labor are requisite before commercial success – or failure – is certainly reached.” [Thomas Edison, 1878] [Ref: Did You Know? Edison Coined the Term “Bug”, http://theinstitute.ieee.org/tech-history/technology-history/did- you-know-edison-coined-the-term-bug, IEEE 2013] “A software bug is an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.” [Ref: https://en.wikipedia.org/wiki/Software_bug] • “Bug” is used informally. BUG • Fault? Error? Or failure? • This course will try to use words that have precise, defined, and unambiguous meaning – and avoid using the term “bug” Fall 2021 – University of Virginia © Praphamontripong 2 Fault, Error, and Failure • Fault: a static defect in the software’s source code Cause of a problem – “fault location” • Error: An incorrect internal state that is the manifestation of some fault Erroneous program state caused by execution of the defect • Failure: External, incorrect behavior with respect to the requirements or other descriptions of the expected behavior Propagation of erroneous state to the program outputs Fall 2021 – University of Virginia © Praphamontripong 3 First Example (Testing)
    [Show full text]