Software testing - Knowledge

2637:

be as terse as "for condition x your derived result is y", although normally test cases describe in more detail the input scenario and what results might be expected. It can occasionally be a series of steps (but often steps are contained in a separate test procedure that can be exercised against multiple test cases, as a matter of economy) but with one expected result or expected outcome. The optional fields are a test case ID, test step, or order of execution number, related requirement(s), depth, test category, author, and check boxes for whether the test is automatable and has been automated. Larger test cases may also contain prerequisite states or steps, and descriptions. A test case should also contain a place for the actual result. These steps can be stored in a word processor document, spreadsheet, database, or other common repositories. In a database system, you may also be able to see past test results, who generated the results, and what system configuration was used to generate those results. These past results would usually be stored in a separate table.

1306:, with the focus on the data values beyond just the related actions of a subsystem component. The practice of component interface testing can be used to check the handling of data passed between various units, or subsystem components, beyond full integration testing between those units. The data being passed can be considered as "message packets" and the range or data types can be checked, for data generated from one unit, and tested for validity before being passed into another unit. One option for interface testing is to keep a separate log file of data items being passed, often with a timestamp logged to allow analysis of thousands of cases of data passed between units for days or weeks. Tests can include checking the handling of some extreme data values while other interface variables are passed as normal values. Unusual data values in an interface can help explain unexpected performance in the next unit. 580: 1106: 7277: 6697: 1231: 6707: 1475:, this can occur because the programmers develop and test software only on the latest version of the target environment, which not all users may be running. This results in the unintended consequence that the latest work may not function on earlier versions of the target environment, or on older hardware that earlier versions of the target environment were capable of using. Sometimes such issues can be fixed by proactively 6717: 7267: 1072:, who coined the term in 1984, defines exploratory testing as "a style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of his/her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project." 2452:

products mentioned in the definition of verification, are the output artifacts of every phase of the software development process. These products are, in fact, specifications such as Architectural Design Specification, Detailed Design Specification, etc. The SRS is also a specification, but it cannot be verified (at least not in the sense used here, more on this subject below).

1359:(using dynamic code analysis) to determine, for instance, boundary values or error messages. Manipulating input data and formatting output do not qualify as grey-box, as the input and output are clearly outside of the "black box" that we are calling the system under test. This distinction is particularly important when conducting 2456:

successfully when it correctly implements its input specification. All the specifications can be verified except the SRS because it is the first one (it can be validated, though). Examples: The Design Specification must implement the SRS; and, the Construction phase artifacts must implement the Design Specification.

2919:

The paper cited for the Bell Labs "Safeguard" project specifically disclaims having collected the fine-grained data that Boehm's data points suggest. The IBM study (Fagan's paper) contains claims that seem to contradict Boehm's graph and no numerical results that clearly correspond to his data points.

2636:

normally consists of a unique identifier, requirement references from a design specification, preconditions, events, a series of steps (also known as actions) to follow, input, output, expected result, and the actual result. Clinically defined, a test case is an input and an expected result. This can

2483:

process itself to reduce the number of faults that end up in the delivered software: the so-called defect rate. What constitutes an acceptable defect rate depends on the nature of the software; a flight simulator video game would have much higher defect tolerance than software for an actual airplane.

1673:

refers to activities that verify a specific action or function of the code. These are usually found in the code requirements documentation, although some development methodologies work from use cases or user stories. Functional tests tend to answer the question of "can the user do this" or "does this

1536:

of program changes, when the newly developed part of the software collides with the previously existing code. Regression testing is typically the largest test effort in commercial software development, due to checking numerous details in prior software features, and even new software can be developed

1333:

are important methodologies for checking software integrity, because they require less preparation time to implement, while the important bugs can be found quickly. In ad hoc testing, where testing takes place in an improvised impromptu way, the ability of the tester(s) to base testing off documented

1322:

Visual testing provides a number of advantages. The quality of communication is increased drastically because testers can show the problem (and the events leading up to it) to the developer as opposed to just describing it and the need to replicate test failures will cease to exist in many cases. The

1318:

At the core of visual testing is the idea that showing someone a problem (or a test failure), rather than just describing it, greatly increases clarity and understanding. Visual testing, therefore, requires the recording of the entire test process – capturing everything that occurs on the test system

2782:

is so expensive relative to its value that it should be used sparingly. The test automation then can be considered as a way to capture and implement the requirements. As a general rule, the larger the system and the greater the complexity, the greater the ROI in test automation. Also, the investment

2462:

Both the SRS and the software must be validated. The SRS can be validated statically by consulting with the stakeholders. Nevertheless, running some partial implementation of the software or a prototype of any kind (dynamic testing) and obtaining positive feedback from them, can further increase the

2289:

such that unit-level testing is performed while writing the product code. Test code is updated as new features are added and failure conditions are discovered (bugs fixed). Commonly, the unit test code is maintained with the project code, integrated in the build process, and run on each build and as

1113:

White-box testing (also known as clear box testing, glass box testing, transparent box testing, and structural testing) verifies the internal structures or workings of a program, as opposed to the functionality exposed to the end-user. In white-box testing, an internal perspective of the system (the

2918:

The "smaller projects" curve turns out to be from only two teams of first-year students, a sample size so small that extrapolating to "smaller projects in general" is totally indefensible. The GTE study does not explain its data, other than to say it came from two projects, one large and one small.

2812:

It is commonly believed that the earlier a defect is found, the cheaper it is to fix it. The following table shows the cost of fixing the defect depending on the stage it was found. For example, if a problem in the requirements is found only post-release, then it would cost 10–100 times more to fix

2455:

But, for the ISO 9000, the specified requirements are the set of specifications, as just mentioned above, that must be verified. A specification, as previously explained, is the product of a software development process phase that receives another specification as input. A specification is verified

2167:

VCR testing, also known as "playback testing" or "record/replay" testing, is a testing technique for increasing the reliability and speed of regression tests that involve a component that is slow or unreliable to communicate with, often a third-party API outside of the tester's control. It involves

2070:

A/B testing is a method of running a controlled experiment to determine if a proposed change is more effective than the current approach. Customers are routed to either a current version (control) of a feature, or to a modified version (treatment) and data is collected to determine which version is

1777:

Performance testing is generally executed to determine how a system or sub-system performs in terms of responsiveness and stability under a particular workload. It can also serve to investigate, measure, validate or verify other quality attributes of the system, such as scalability, reliability and

1036:

Passive testing means verifying the system's behavior without any interaction with the software product. Contrary to active testing, testers do not provide any test data but look at system logs and traces. They mine for patterns and specific behavior in order to make some kind of decisions. This is

2678:

that are intended to be used to test a software program to show that it has some specified set of behaviors. A test suite often contains detailed instructions or goals for each collection of test cases and information on the system configuration to be used during testing. A group of test cases may

2158:

Metamorphic testing (MT) is a property-based software testing technique, which can be an effective approach for addressing the test oracle problem and test case generation problem. The test oracle problem is the difficulty of determining the expected outcomes of selected test cases or to determine

1282:

to be provided to the tester, who then can simply verify that for a given input, the output value (or behavior), either "is" or "is not" the same as the expected value specified in the test case. Test cases are built around specifications and requirements, i.e., what the application is supposed to

2922:

Boehm doesn't even cite a paper for the TRW data, except when writing for "Making Software" in 2010, and there he cited the original 1976 article. There exists a large study conducted at TRW at the right time for Boehm to cite it, but that paper doesn't contain the sort of data that would support

2568:

is a document detailing the approach that will be taken for intended test activities. The plan may include aspects such as objectives, scope, processes and procedures, personnel requirements, and contingency plans. The test plan could come in the form of a single plan that includes all test types

2800:

No certification now offered actually requires the applicant to show their ability to test software. No certification is based on a widely accepted body of knowledge. Certification itself cannot measure an individual's productivity, their skill, or practical knowledge, and cannot guarantee their

1921:

The International Organization for Standardization (ISO) defines this as a "type of testing conducted to evaluate the degree to which a test item, and associated data and information, are protected so that unauthorised persons or systems cannot use, read or modify them, and authorized persons or

2045:

construction phase of the software development lifecycle. Development Testing aims to eliminate construction errors before code is promoted to other testing; this strategy is intended to increase the quality of the resulting software as well as the efficiency of the overall development process.

881:

separate from the software being tested to control the execution of tests and the comparison of actual outcomes with predicted outcomes. Test automation can automate some repetitive but necessary tasks in a formalized testing process already in place, or perform additional testing that would be

2694:

In most cases, multiple sets of values or data are used to test the same functionality of a particular feature. All the test values and changeable environmental components are collected in separate files and stored as test data. It is also useful to provide this data to the client and with the

2451:

In the case of IEEE standards, the specified requirements, mentioned in the definition of validation, are the set of problems, needs and wants of the stakeholders that the software must solve and satisfy. Such requirements are documented in a Software Requirements Specification (SRS). And, the

2132:

Property testing is a testing technique where, instead of asserting that specific inputs produce specific expected outputs, the practitioner randomly generates many inputs, runs the program on all of them, and asserts the truth of some "property" that should be true for every pair of input and

1618:

Contractual acceptance testing is performed based on the contract's acceptance criteria defined during the agreement of the contract, while regulatory acceptance testing is performed based on the relevant regulations to the software product. Both of these two tests can be performed by users or

1090:

Software testing can often be divided into white-box and black-box. These two approaches are used to describe the point of view that the tester takes when designing test cases. A hybrid approach called grey-box includes aspects of both boxes may also be applied to software testing methodology.

2466:

Some might argue that, for SRS, the input is the words of stakeholders and, therefore, SRS validation is the same as SRS verification. Thinking this way is not advisable as it only causes more confusion. It is better to think of verification as a process involving a formal and technical input

1354:

Grey-box testing (American spelling: gray-box testing) involves using knowledge of internal data structures and algorithms for purposes of designing tests while executing those tests at the user, or black-box level. The tester will often have access to both "the source code and the executable

1133:

levels of the software testing process, it is usually done at the unit level. It can test paths within a unit, paths between units during integration, and between subsystems during a system–level test. Though this method of test design can uncover many errors or problems, it might not detect

2044:

Development Testing is a software development process that involves the synchronized application of a broad spectrum of defect prevention and detection strategies in order to reduce software development risks, time, and costs. It is performed by the software developer or engineer during the

1696:. Testing will determine the breaking point, the point at which extremes of scalability or performance leads to unstable execution. Non-functional requirements tend to be those that reflect the quality of the product, particularly in the context of the suitability perspective of its users. 1081:

The type of testing strategy to be performed depends on whether the tests to be applied to the IUT should be decided before the testing plan starts to be executed (preset testing) or whether each input to be applied to the IUT can be dynamically dependent on the outputs obtained during the

708:

from testing in 1979. Although his attention was on breakage testing ("A successful test case is one that detects an as-yet undiscovered error."), it illustrated the desire of the software engineering community to separate fundamental development activities, such as debugging, from that of

1627:

Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers' site. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing before the software goes to beta testing.

1314:

The aim of visual testing is to provide developers with the ability to examine what was happening at the point of software failure by presenting the data in such a way that the developer can easily find the information he or she requires, and the information is expressed clearly.

1238:

Black-box testing (also known as functional testing) describes designing test cases without knowledge of the implementation, without reading the source code. The testers are only aware of what the software is supposed to do, not how it does it. Black-box testing methods include:

2463:

certainty that the SRS is correctly formulated. On the other hand, the software, as a final and running product (not its artifacts and documents, including the source code) must be validated dynamically with the stakeholders by executing the software and having them to try it.

1366:

By knowing the underlying concepts of how the software works, the tester makes better-informed testing choices while testing the software from outside. Typically, a grey-box tester will be permitted to set up an isolated testing environment with activities such as seeding a

2370:: It is common to have a small test program built of a subset of tests, for each integration of new, modified, or fixed software, in order to ensure that the latest delivery has not ruined anything and that the software product as a whole is still working correctly. 2133:

output. For example, every output from a serialization function should be accepted by the corresponding deserialization function, and every output from a sort function should be a monotonically increasing list containing exactly the same elements as its input.

2136:

Property testing libraries allow the user to control the strategy by which random inputs are constructed, to ensure coverage of degenerate cases, or inputs featuring specific patterns that are needed to fully exercise aspects of the implementation under test.

2793:

Significant opposition has formed out of the ranks of the context-driven school of software testing about the ISO 29119 standard. Professional testing associations, such as the International Society for Software Testing, have attempted to have the standard

1614:

In addition, the software testing should ensure that the portability of the system, as well as working as expected, does not also damage or partially corrupt its operating environment or cause other processes within that environment to become inoperative.

1375:

statements against the database and then executing queries to ensure that the expected changes have been reflected. Grey-box testing implements intelligent test scenarios, based on limited information. This will particularly apply to data type handling,

2116:

of text or screenshots of the UI, is sometimes called snapshot testing or Golden Master Testing unlike many other forms of testing, this cannot detect failures automatically and instead requires that a human evaluate the output for inconsistencies.

1545:

of the added features. They can either be complete, for changes added late in the release or deemed to be risky, or be very shallow, consisting of positive tests on each feature, if the changes are early in the release or deemed to be of low risk.

2649:

is a procedure or programming code that replicates user actions. Initially, the term was derived from the product of work created by automated regression test tools. A test case will be a baseline to create test scripts using a tool or a program.

1176:

Code coverage tools can evaluate the completeness of a test suite that was created with any method, including black-box testing. This allows the software team to examine parts of a system that are rarely tested and ensures that the most important

2569:(like an acceptance or system test plan) and planning considerations, or it may be issued as a master test plan that provides an overview of more than one detailed test plan (a plan of a plan). A test plan can be, in some cases, part of a wide " 1334:

methods and then improvise variations of those tests can result in more rigorous examination of defect fixes. However, unless strict documentation of the procedures are maintained, one of the limits of ad hoc testing is lack of repeatability.

2360:

Test result analysis: Or Defect Analysis, is done by the development team usually along with the client, in order to decide what defects should be assigned, fixed, rejected (i.e. found software working properly) or deferred to be dealt with

2103:

In software testing, conformance testing verifies that a product performs according to its specified standards. Compilers, for instance, are extensively tested to determine whether they meet the recognized standard for that language.

2735:

Several certification programs exist to support the professional aspirations of software testers and quality assurance specialists. A few practitioners argue that the testing field is not ready for certification, as mentioned in the

1842:

is to check if the user interface is easy to use and understand. It is concerned mainly with the use of the application. This is not a kind of testing that can be automated; actual human users are needed, being monitored by skilled

1114:

source code), as well as programming skills, are used to design test cases. The tester chooses inputs to exercise paths through the code and determines the appropriate outputs. This is analogous to testing nodes in a circuit, e.g.,

1532:, as degraded or lost features, including old bugs that have come back. Such regressions occur whenever software functionality that was previously working correctly, stops working as intended. Typically, regressions occur as an 2168:

making a recording ("cassette") of the system's interactions with the external component, and then replaying the recorded interactions as a substitute for communicating with the external system on subsequent runs of the test.

2767:

movement has received growing popularity since the early 2000s mainly in commercial circles, whereas government and military software providers use this methodology but also the traditional test-last models (e.g., in the

1540:

Common methods of regression testing include re-running previous sets of test cases and checking whether previously fixed faults have re-emerged. The depth of testing depends on the phase in the release process and the

2479:(SQA) process. In SQA, software process specialists and auditors are concerned with the software development process rather than just the artifacts such as documentation, code and systems. They examine and change the 2373:

Test Closure: Once the test meets the exit criteria, the activities such as capturing the key outputs, lessons learned, results, logs, documents related to the project are archived and used as a reference for future

1598:

projects. This type of testing focuses on the operational readiness of the system to be supported, or to become part of the production environment. Hence, it is also known as operational readiness testing (ORT) or

2349:

Test execution: Testers execute the software based on the plans and test documents then report any errors found to the development team. This part could be complex when running tests with a lack of programming

1400:

Most software systems have installation procedures that are needed before they can be used for their main purpose. Testing these procedures to achieve an installed software system that may be used is known as

5274:; Hayes, Jane Huffman; Zisman, Andrea; Egyed, Alexander; Grünbacher, Paul; Dekhtyar, Alex; Antoniol, Giuliano; Maletic, Jonathan (January 1, 2012). Cleland-Huang, Jane; Gotel, Orlena; Zisman, Andrea (eds.). 1736:

Destructive testing attempts to cause the software or a sub-system to fail. It verifies that the software functions properly even when it receives invalid or unexpected inputs, thereby establishing the

1650:, are released to a limited audience outside of the programming team known as beta testers. The software is released to groups of people so that further testing can ensure the product has few faults or 2721:

A test run is a collection of test cases or test suites that the user is executing and comparing the expected with the actual results. Once complete, a report or all executed tests may be generated.

1010:. Dynamic testing takes place when the program itself is run. Dynamic testing may begin before the program is 100% complete in order to test particular sections of code and are applied to discrete 1714:

as part of the software delivery pipeline to obtain immediate feedback on the business risks associated with a software release candidate. Continuous testing includes the validation of both

2419:

The terms verification and validation are commonly used interchangeably in the industry; it is also common to see these two terms defined with contradictory definitions. According to the

802:

combinations of inputs and preconditions (initial state) is not feasible, even with a simple product. Defects that manifest in unusual conditions are difficult to find in testing. Also,

1938:

is used to test the ability of an application to be translated to another language, and make it easier to identify when the localization process may introduce new bugs into the product.

2430:

Verification is the process of evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase.

1510:

consists of minimal attempts to operate the software, designed to determine whether there are any basic problems that will prevent it from working at all. Such tests can be used as

1006:

Static testing is often implicit, like proofreading, plus when programming tools/text editors check source code structure or compilers (pre-compilers) check syntax and data flow as

3529: 3378: 1291:, though usually functional. Specification-based testing may be necessary to assure correct functionality, but it is insufficient to guard against complex or high-risk situations. 5699: 2260:, testing is generally performed after the code is completed, but before the product is shipped to the customer. This practice often results in the testing phase being used as a 2278:

commonly involves testing while the code is being written and organizing teams with both programmers and testers and with team members performing both programming and testing.

2000:

A string in the target language may be longer than the software can handle. This may make the string partly invisible to the user or cause the software to crash or malfunction.

1154:– creating tests to satisfy some criteria of code coverage (for example, the test designer can create tests to cause all statements in the program to be executed at least once) 2089:, generally under normal usage conditions. Typical problems this type of testing will expose are deadlocks, race conditions and problems with shared memory/resource handling. 1216:) are executed at least once. This is helpful in ensuring correct functionality, but not sufficient since the same code may process different inputs correctly or incorrectly. 4746: 687:

in 2002 reported that software bugs cost the U.S. economy $ 59.5 billion annually. More than a third of this cost could be avoided, if better software testing was performed.

643:, comparable products, past versions of the same product, inferences about intended or expected purpose, user or customer expectations, relevant standards, applicable laws. 2444:

Validation is confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.

2807:

There are opposing views on the applicability of studies used to show the relative expense of fixing defects depending on their introduction and detection. For example:

2433:

Validation is the process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements.

1722:; the scope of testing extends from validating bottom-up requirements or user stories to assessing the system requirements associated with overarching business goals. 2267:

Some contend that the waterfall process allows for testing to start when the development project starts and to be a continuous process until the project finishes.

1886: 1786:

is primarily concerned with testing that the system can continue to operate under a specific load, whether that be large quantities of data or a large number of

1278:

Specification-based testing aims to test the functionality of software according to the applicable requirements. This level of testing usually requires thorough

566: 2309:

The sample below is common for waterfall development. The same activities are commonly found in other development models, but might be described differently.

747:

A defect that does not cause failure at one point in time may later occur due to environmental changes. Examples of environment change include running on new

1955:

Technical terminology may become inconsistent, if the project is translated by several people without proper coordination or if the translator is imprudent.

1566:

Tests are frequently grouped into these levels by where they are performed in the software development process, or by the level of specificity of the test.

3418: 3382: 3156:. ESEC/FSE'07: European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering 2007. Dubrovnik, Croatia 3531:

Systems, Software and Services Process Improvement: 22nd European Conference, EuroSPI 2015, Ankara, Turkey, September 30 -- October 2, 2015. Proceedings

2140:

Property testing is also sometimes known as "generative testing" or "QuickCheck testing" since it was introduced and popularized by the Haskell library

646:

Software testing is often dynamic in nature; running the software to verify actual output matches expected. It can also be static in nature; reviewing

520: 1323:

developer will have all the evidence he or she requires of a test failure and can instead focus on the cause of the fault and how it should be fixed.

2487:

Software testing is an activity to investigate software under test in order to provide quality-related information to stakeholders. By contrast, QA (

5380: 4550: 1319:

in video format. Output videos are supplemented by real-time tester input via picture-in-a-picture webcam and audio commentary from microphones.

1814:(often referred to as load or endurance testing) checks to see if the software can continuously function well in or above an acceptable period. 1283:

do. It uses external descriptions of the software, including specifications, requirements, and designs to derive test cases. These tests can be

6753: 5506: 4870: 3287: 5529:"NSF grant proposal to 'lay a foundation for significant improvements in the quality of academic and commercial courses in software testing'" 5440: 3232:

Crafting Test-Driven Software with Python: Write test suites that scale with your applications' needs and complexity using Python and PyTest

2597:(TM) is a document, usually in the form of a table, used to assist in determining the completeness of a relationship by correlating any two 2484:

Although there are close links with SQA, testing departments often exist independently, and there may be no SQA function in some companies.

487: 3386: 2441:

Verification is confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.

1858:

testing is done to ensure that the software is accessible to persons with disabilities. Some of the common web accessibility tests are

7313: 5740: 559: 339: 7624: 2320:. During the design phase, testers work to determine what aspects of a design are testable and with what parameters those tests work. 4843: 5528: 4772: 4735: 4458: 3592: 1881: 5713: 4975: 2783:

in tools and expertise can be amortized over multiple projects with the right level of knowledge sharing within an organization.

6450: 6422: 3781:

Lee, D.; Netravali, A.N.; Sabnani, K.K.; Sugla, B.; John, A. (1997). "Passive testing and applications to network management".

3528:

O’Connor, Rory V.; Akkaya, Mariye Umay; Kemaneci, Kerem; Yilmaz, Murat; Poth, Alexander; Messnarz, Richard (October 15, 2015).

2448:

The contradiction is caused by the use of the concepts of requirements and specified requirements but with different meanings.

2405: 2395: 657:

Software testing is often used to answer the question: Does the software do what it is supposed to do and what it needs to do?

477: 329: 3895:

Petrenko, A.; Yevtushenko, N. (2011). "Adaptive testing of deterministic implementations specified by nondeterministic FSMs".

1817:

There is little agreement on what the specific goals of performance testing are. The terms load testing, performance testing,

1804:

is a way to test software functions even when certain components (for example a file or database) increase radically in size.

7270: 7136: 7065: 6475: 5615: 5470: 5415: 5318: 5156: 5103: 5022: 4714: 4687: 4658: 4619: 4534: 4504: 4413: 4379: 4349: 4254: 4130: 4074: 4049: 4017: 3983: 3949: 3914: 3798: 3765: 3731: 3701: 3676: 3649: 3607: 3568: 3539: 3512: 3487: 3363: 3328: 3189: 3127: 2247: 1931: 552: 452: 208: 193: 1941:

Globalization testing verifies that the software is adapted for a new culture (such as different currencies or time zones).

1383:

With the concept of grey-box testing, this "arbitrary distinction" between black- and white-box testing has faded somewhat.

766:

Software testing may involve a Requirements gap – omission from the design for a requirement. Requirement gaps can often be

6959: 6862: 6326: 2550:. The actual artifacts produced are a factor of the software development model used, stakeholder and organisational needs. 1993:

Fonts and font sizes that are appropriate in the source language may be inappropriate in the target language; for example,

1658:

field to a maximal number of future users and to deliver value earlier, for an extended or even indefinite period of time (

472: 6480: 5759: 3411: 2598: 1619:

independent testers. Regulation acceptance testing sometimes involves the regulatory agencies auditing the test results.

510: 5564: 3846: 3825: 2297:

Even in organizations that separate teams by programming and testing functions, many often have the programmers perform

2192:

team or they may be integrated into one team. Software testing can also be performed by non-dedicated software testers.

1528:

Regression testing focuses on finding defects after a major code change has occurred. Specifically, it seeks to uncover

6746: 5992: 3264: 3239: 3214: 1969: 1600: 1145: 946:, also called integration and testing, abbreviated I&T, is a form of software testing in which multiple parts of a 693:

software testing because of costs is very common, with China, the Philippines, and India being preferred destinations.

419: 183: 4924: 6939: 6806: 6791: 6632: 6460: 5997: 5483: 5355: 5291: 4588: 2022: 1944:

Actual translation to human languages must be tested, too. Possible localization and globalization failures include:

1844: 1363:

between two modules of code written by two different developers, where only the interfaces are exposed for the test.

286: 3898:

In Testing Software and Systems: 23rd IFIP WG 6.1 International Conference, ICTSS 2011, Paris, France, November 7-10

7563: 6720: 5821: 4953:

ISO/IEC/IEEE 29119-1:2013 – Software and Systems Engineering – Software Testing – Part 1 – Concepts and Definitions

2970: 1338: 579: 409: 404: 160: 3148: 2605:(these often consist of marketing requirements) and detailed requirements of the product to the matching parts of 2573:" which documents overall testing approaches, which may itself be a master test plan or even a separate artifact. 1537:

while using some old test cases to test parts of the new design to ensure prior functionality is still supported.

1371:. The tester can observe the state of the product being tested after performing certain actions such as executing 635:, software testing employs principles and mechanisms that might recognize a problem. Examples of oracles include: 6108: 5201: 2547: 2538:, or measures, which are used to assist in determining the state of the software or the adequacy of the testing. 2317: 538: 2709:

The software, tools, samples of data input and output, and configurations are all referred to collectively as a

2364:

Defect Retesting: Once a defect has been dealt with by the development team, it is retested by the testing team.

7306: 7095: 7022: 7012: 6857: 6786: 6399: 6361: 6025: 5733: 5704: 2749: 2500: 1958:

Literal word-for-word translations may sound inappropriate, artificial or too technical in the target language.

1476: 617: 429: 142: 122: 1753:

page; there are also numerous open-source and free software tools available that perform destructive testing.

1637: 291: 7280: 7146: 7075: 7017: 6739: 6541: 6518: 6248: 6238: 3006: 2979: 1738: 660:

Information learned from software testing may be used to improve the process by which software is developed.

228: 218: 168: 4794: 7588: 7527: 7085: 6944: 6811: 6622: 6210: 6118: 6030: 5806: 5791: 1891: 1794:. The related load testing activity of when performed as a non-functional activity is often referred to as 1772: 1563:

Acceptance testing may be performed as part of the hand-off process between any two phases of development.

515: 243: 59: 17: 2085:

Concurrent or concurrency testing assesses the behaviour and performance of software and systems that use

7007: 7002: 6816: 6710: 6445: 5950: 2048:

Depending on the organization's expectations for software development, Development Testing might include

1719: 1680:

refers to aspects of the software that may not be related to a specific function or user action, such as

1011: 803: 767: 334: 306: 2491:) is the implementation of policies and procedures intended to prevent defects from reaching customers. 1934:

validates that the software can be used with different languages and geographic regions. The process of

1749:, is an example of failure testing. Various commercial non-functional testing tools are linked from the 1586:

OAT is used to conduct operational readiness (pre-release) of a product, service or system as part of a

7202: 7050: 7045: 6997: 6974: 6954: 6682: 6331: 5384: 4820: 4611: 3451:. IEEE Fifth International Conference on Software Testing and Validation (ICST). Montreal, QC, Canada. 2759:

Should testers learn to work under conditions of uncertainty and constant change or should they aim at

2476: 2421: 2275: 1915: 457: 301: 188: 178: 117: 5340:

Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering

7619: 7532: 7299: 7207: 7197: 6700: 6627: 6602: 6465: 6113: 5726: 5228: 3179: 2760: 2053: 1949: 1895: 1587: 831: 223: 203: 4554: 2817:

practices and cloud-based services, the cost of re-deployment and maintenance may lessen over time.

2353:

Test reporting: Once testing is completed, testers generate metrics and make final reports on their

7573: 7522: 7492: 7434: 7110: 6909: 6892: 6801: 6551: 6384: 5977: 5846: 4305: 4146: 3901:. Lecture Notes in Computer Science. Vol. 7019. Springer Berlin Heidelberg. pp. 162–178. 3012: 2991: 2958: 2399: 1952:

out of context, and the translator may choose the wrong translation for an ambiguous source string.

1689: 1507: 1496: 1240: 852: 834:– can be subjective; something that constitutes sufficient value to one person may not to another. 364: 233: 213: 5245: 7060: 6904: 6612: 6546: 6437: 6253: 5920: 5448: 4280: 2730: 2512: 2504: 2282: 2238:

Organizations that develop software, perform testing differently, but there are common patterns.

2052:, data flow analysis, metrics analysis, peer code reviews, unit testing, code coverage analysis, 1782: 1715: 1643: 1511: 1244: 1007: 492: 374: 253: 127: 2914:

The data from which this table is extrapolated is scant. Laurent Bossavit says in his analysis:

7115: 6872: 6867: 6677: 6508: 6389: 6156: 6146: 6141: 5651: 3930:

Petrenko, A.; Yevtushenko, N. (2014). "Adaptive testing of nondeterministic systems with FSM".

3280: 2516: 2415:

Validation: Have we built the right software? (i.e., do the deliverables satisfy the customer).

2291: 1972:

and the resulting string may be ungrammatical, functionally incorrect, misleading or confusing.

1677: 1560:

Acceptance testing is system-level testing to ensure the software meets customer expectations.

1533: 1472: 1436: 1294:

Black box testing can be used to any level of testing although usually not at the unit level.

1288: 1252: 1206:, which reports on whether both the True and the False branch of a given test has been executed 827: 434: 344: 296: 238: 4976:"Globalization Step-by-Step: The World-Ready Approach to Testing. Microsoft Developer Network" 4896: 4704: 4605: 4524: 4369: 4007: 3973: 3755: 3666: 3639: 3479: 7452: 7447: 6934: 6887: 6647: 6617: 6607: 6503: 6417: 6293: 6233: 6200: 6190: 6080: 6045: 6035: 5972: 5841: 5816: 5811: 5776: 5633:

The Leprechauns of Software Engineering: How folklore turns into fact and what to do about it

4675: 4648: 4494: 4403: 4339: 4120: 4039: 3721: 2941: 2814: 2313: 1583:

Sometimes, UAT is performed by the customer, in their environment and on their own hardware.

1430: 1026: 258: 74: 64: 5146: 3471: 3449:

Combinatorial Test Design in the TOSCA Testsuite: Lessons Learned and Practical Implications

7497: 7487: 7232: 7070: 6929: 6919: 6831: 6776: 6762: 6407: 6379: 6351: 6346: 6175: 6151: 6103: 6088: 6070: 6060: 6055: 6017: 5967: 5962: 5879: 5825: 5607: 3017: 2667: 2590: 2480: 2412:

Verification: Have we built the software right? (i.e., does it implement the requirements).

2264:

buffer to compensate for project delays, thereby compromising the time devoted to testing.

2189: 2086: 2049: 2018: 1911: 1595: 1591: 1440: 1402: 1393: 1038: 988: 823: 783: 771: 621: 354: 198: 132: 99: 79: 40: 1405:. These procedures may involve full or partial upgrades, and install/uninstall processes. 8: 7482: 7477: 7467: 7411: 7356: 7346: 7252: 7237: 7105: 6969: 6877: 6821: 6672: 6597: 6513: 6498: 6263: 6050: 6007: 6002: 5899: 5889: 5861: 2964: 2594: 2583: 2459:

So, when these words are defined in common terms, the apparent contradiction disappears.

2153: 2098: 2039: 2004: 1862:

Ensuring that the color contrast between the font and the background color is appropriate

1824: 1818: 1731: 1529: 1484: 1480: 1448: 1360: 1330: 1272: 1264: 1126: 1064:

is an approach to software testing that is concisely described as simultaneous learning,

1061: 1055: 1030: 995:

are referred to as static testing, whereas executing programmed code with a given set of

992: 943: 937: 883: 668: 663:

Software testing should follow a "pyramid" approach wherein most of your tests should be

349: 268: 94: 5535: 3613: 2813:

than if it had already been found by the requirements review. With the advent of modern

7537: 7512: 7472: 7462: 7406: 7242: 6882: 6637: 6536: 6412: 6369: 6278: 6220: 6205: 6195: 5987: 5786: 5421: 5361: 5271: 5076: 5028: 5007:

Proceedings of the fifth ACM SIGPLAN international conference on Functional programming

4466: 3804: 3063:. Quality Assurance Institute Worldwide Annual Software Testing Conference. Orlando, FL 2367: 2261: 2080: 2014: 1987: 1935: 1757: 1705: 1670: 1604: 1555: 1523: 1451:, old or new), or target environments that differ greatly from the original (such as a 1377: 1284: 887: 672: 640: 602: 467: 5631:

Bossavit, Laurent (November 20, 2013). "The cost of defects: an illustrated history".

5119: 4871:"The Relationship between Risk and Continuous Testing: An Interview with Wayne Ariola" 4244: 3086: 1160:

methods – intentionally introducing faults to gauge the efficacy of testing strategies

922:, a.k.a. component or module testing, is a form of software testing by which isolated 7547: 7373: 7341: 7336: 7156: 6914: 6657: 6587: 6566: 6528: 6336: 6303: 6283: 5982: 5894: 5768: 5611: 5466: 5411: 5351: 5335: 5314: 5287: 5152: 5099: 5050: 5018: 4979: 4710: 4683: 4654: 4615: 4584: 4530: 4500: 4409: 4375: 4345: 4250: 4126: 4070: 4045: 4013: 3979: 3945: 3910: 3794: 3761: 3727: 3697: 3672: 3645: 3603: 3564: 3535: 3508: 3483: 3472: 3359: 3324: 3318: 3260: 3235: 3210: 3185: 3123: 2606: 2488: 2335:

creation. Since many activities will be carried out during testing, a plan is needed.

1976: 1839: 1828: 1693: 1452: 1303: 1248: 1225: 1100: 787: 748: 701: 5425: 5080: 4773:"Operational Acceptance – an application of the ISO 29119 Software Testing standard" 4271: 3808: 1655: 729:

that causes an undesirable result. Bugs generally slow testing progress and involve

7517: 7502: 7457: 7383: 7368: 7361: 7227: 7171: 6949: 6841: 6490: 6374: 6341: 6136: 6065: 5954: 5940: 5935: 5884: 5871: 5796: 5749: 5662: 5600: 5403: 5365: 5343: 5279: 5066: 5032: 5010: 5002: 4430: 3937: 3902: 3877: 3786: 3452: 3351: 2947: 2384: 2126: 1907: 1761: 1460: 1444: 1349: 1163: 610: 424: 387: 369: 359: 2679:

also contain prerequisite states or steps and descriptions of the following tests.

7542: 7247: 7100: 7080: 6964: 6826: 6561: 6455: 6427: 6321: 6273: 6258: 6243: 6098: 6093: 6040: 5930: 5904: 5856: 5801: 5694: 4122:

Pragmatic Software Testing: Becoming an Effective and Efficient Test Professional

3906: 3850: 3829: 2935: 2779: 2769: 2535: 2524: 2257: 2251: 2113: 1980: 1750: 1742: 1711: 1542: 1464: 1182: 1178: 1157: 1115: 1000: 971: 947: 900: 874: 867: 779: 311: 263: 147: 69: 5283: 3355: 2797:

Some practitioners declare that the testing field is not ready for certification

1642:

Beta testing comes after alpha testing and can be considered a form of external

7593: 7568: 7507: 7416: 7388: 7151: 7055: 6796: 6667: 6571: 6470: 6316: 6288: 3933:

In 2014 IEEE 15th International Symposium on High-Assurance Systems Engineering

3896: 3314: 3144: 2985: 2953: 2601:

using a many-to-many relationship comparison. It is often used with high-level

1994: 1871:

Ability to use the system using the computer keyboard in addition to the mouse.

1827:

systems have strict timing constraints. To test if timing constraints are met,

1806: 1800: 1659: 1501: 1356: 1326: 1256: 1169: 1130: 967: 961: 5175: 4094: 3422: 7613: 7131: 6899: 6556: 5851: 5689: 5573: 5046: 3843: 3822: 3790: 2787: 2764: 2570: 2339: 2324: 1855: 1212:

100% statement coverage ensures that all code paths or branches (in terms of

1151: 1105: 838: 725:

Software testing typically includes handling software bugs – a defect in the

651: 636: 54: 5347: 5334:

Pinto, Leandro Sales; Sinha, Saurabh; Orso, Alessandro (November 11, 2012).

5202:"Test-Driven Development and Continuous Integration for Mobile Applications" 2967: – Proving or disproving the correctness of certain intended algorithms 1418:

Software systems may need connectivity to connect to other software systems.

7583: 7578: 7421: 7351: 7166: 7161: 7090: 6652: 6311: 4067:

Software Testing: Testing Across the Entire Software Development Life Cycle

3000: 2710: 2704: 2689: 2508: 2298: 2286: 2188:

In an organization, testers may be in a separate team from the rest of the

1787: 1746: 1651: 1647: 1260: 1213: 1122: 1042: 919: 913: 837:

Although testing for every possible input is not feasible, testing can use

625: 137: 5491: 5014: 4951: 3456: 3150:

Contract Driven Development = Test Driven Development – Writing Test Cases

1590:. OAT is a common type of non-functional software testing, used mainly in 624:, but cannot determine correctness for all scenarios. It cannot find all 601:

Software testing can provide objective, independent information about the

7598: 7442: 7378: 6642: 6268: 6180: 3941: 3556: 3029: 3023: 2646: 2602: 2354: 2065: 1983:, but is used for typing characters in the layout of the target language. 1962: 1791: 1685: 1681: 1654:. Beta versions can be made available to the open public to increase the 1468: 1141: 1065: 1015: 984: 923: 899:

Software testing can be categorized into levels based on how much of the

819: 775: 752: 726: 690: 647: 632: 5666: 5407: 5071: 5054: 3447:

Ramler, Rudolf; Kopetzky, Theodorich; Platz, Wolfgang (April 17, 2012).

3281:"The Economic Impacts of Inadequate Infrastructure for Software Testing" 2938: – The process of ensuring computer data is both correct and useful 1435:

A common cause of software failure (real or perceived) is a lack of its

7176: 7141: 6731: 6662: 6592: 6185: 5925: 5781: 4301: 4065:

Everatt, G.D.; McLeod Jr., R. (2007). "Chapter 7: Functional Testing".

3931: 2671: 2660: 2141: 730: 664: 5398:

Griffiths, M. (2005). "Teaching agile project management to the PMI".

4673: 1910:

is essential for software that processes confidential data to prevent

970:, a.k.a. end-to-end (E2E) testing, is testing conducted on a complete 6167: 6128: 5560: 5524: 3881: 3719: 3115: 3055: 3051: 2675: 2633: 2627: 2614: 2610: 2565: 2559: 2528: 2343: 2328: 2171:

The technique was popularized in web development by the Ruby library

1607:

within OAT is limited to those tests that are required to verify the

1504:

determines whether it is reasonable to proceed with further testing.

1279: 1069: 996: 815: 741: 705: 89: 1230: 1200:, which reports on the number of lines executed to complete the test 7291: 6924: 6228: 5718: 5308: 3865: 2026: 1412:

Dependent files and libraries must be allocated, loaded or located.

1368: 1268: 1019: 878: 798:

A fundamental limitation of software testing is that testing under

595: 584: 462: 414: 399: 394: 4800:. Version 3.1. International Software Testing Qualifications Board 4702: 4678:. In Borba, P.; Cavalcanti, A.; Sampaio, A.; Woodcook, J. (eds.). 4574: 4572: 4200:

consists of only one statement. All tests against a specification

3866:"Principles and methods of testing finite state machines-a survey" 3694:

Automated Defect Prevention: Best Practices in Software Management

3505:

Automated Defect Prevention: Best Practices in Software Management

3181:

Automated Defect Prevention: Best Practices in Software Management

2695:

product or a project. There are techniques to generate Test data.

1134:

unimplemented parts of the specification or missing requirements.

2520: 2332: 1810:

is a way to test reliability under unexpected or rare workloads.

3600:

SWEBOK v3.0: Guide to the Software Engineering Body of Knowledge

2982: – Organization that tests according to agreed requirements 2674:, less commonly known as a validation suite, is a collection of 6781: 5708: 5383:. Software Test & Performance Collaborative. Archived from 5227:

Brown, Chris; Cobb, Gary; Culbertson, Robert (April 12, 2002).

4569: 4273:

The Theory and Practice of Specification Based Software Testing

173: 4823:. O'Reilly Media. Section 4. End of the Software Release Cycle 3783:

Proceedings 1997 International Conference on Network Protocols

3474:

Lessons Learned in Software Testing: A Context-Driven Approach

2013:

Localized operating systems may have differently named system

6981: 5269: 4579:

Myers, G. (2004). Sandler, C; Badgett, T; Thomas, M. (eds.).

2961: – Analysis of software performed when running a program 2172: 2159:

whether the actual outputs agree with the expected outcomes.

2010:

Software may display images with text that was not localized.

734: 248: 4703:

Clapp, J.A.; Stanten, S.F.; Peng, W.W.; et al. (1995).

3527: 2357:

and whether or not the software tested is ready for release.

7192: 5336:"Understanding myths and realities of test-suite evolution" 4844:"Part of the Pipeline: Why Continuous Testing Is Essential" 4743:

ISTQB - International Software Testing Qualifications Board

4064: 2804:

Studies used to show the relative expense of fixing defects

1961:

Untranslated messages in the original language may be left

684: 606: 482: 5265: 5263: 3348:

IEEE Standard Glossary of Software Engineering Terminology

1014:

or modules. Typical techniques for these are either using

882:

difficult to do manually. Test automation is critical for

740:

Not all defects cause a failure. For example, a defect in

4682:. Springer Science & Business Media. pp. 13–14. 3032: – Software testing that focuses on web applications 2346:, test datasets, test scripts to use in testing software. 1456: 1372: 758:

A single defect may result in multiple failure symptoms.

3780: 3753: 3590: 3421:. July 1, 2005. Principle 2, Section 1.3. Archived from 2316:: Testing should begin in the requirements phase of the 2003:

Software may lack proper support for reading or writing

1925: 631:

Based on the criteria for measuring correctness from an

5507:"Software testers balk at ISO 29119 standards proposal" 5260: 4279:(dissertation thesis). Department of Computer Science, 3207:

Succeeding with Agile: Software Development Using Scrum

2389: 1887:

Section 508 Amendment to the Rehabilitation Act of 1973

1665: 1479:

operating system functionality into a separate program

978: 5342:. Association for Computing Machinery. pp. 1–11. 3715: 3713: 3691: 3502: 3142: 3020: – Stores test steps, test planning and reporting 2092: 1821:, and volume testing, are often used interchangeably. 1144:– testing of the application using public and private 1082:

application of the previous tests (adaptive testing).

761: 583:

TestingCup – Polish Championship in Software Testing,

4795:"Standard Glossary of Terms used in Software Testing" 4706:

Software Quality Control, Error Analysis, and Testing

4371:

Software Quality Control, Error Analysis, and Testing

2944: – Checking web applications in various browsers 2475:

In some organizations, software testing is part of a

2199:

started to be used to denote a separate profession.

1948:

Software is often localized by translating a list of

1076: 5624: 4642: 4640: 4638: 4522: 4037: 2996:

Pages displaying wikidata descriptions as a fallback

2975:

Pages displaying wikidata descriptions as a fallback

5714:"Software that makes Software better" Economist.com 5226: 5170: 5168: 4674:Machado, P.; Vincenzi, A.; Maldonado, J.C. (2010). 4650:

Software Testing and Continuous Quality Improvement

4496:

Software Testing and Continuous Quality Improvement

4114: 4112: 3967: 3965: 3963: 3961: 3929: 3894: 3757:

Verification and Validation in Scientific Computing

3749: 3747: 3745: 3743: 3710: 3685: 3561:

Guide to the Software Engineering Body of Knowledge

3555:Bourque, Pierre; Fairley, Richard E., eds. (2014). 3469: 3446: 3419:

International Software Testing Qualifications Board

3383:

International Software Testing Qualifications Board

2202:Notable software testing roles and titles include: 1741:of input validation and error-management routines. 5599: 4553:(white paper). Crosscheck Networks. Archived from 4488: 4486: 4484: 4001: 3999: 3997: 3995: 3720:Graham, D.; Van Veenendaal, E.; Evans, I. (2008). 3470:Kaner, Cem; Bach, James; Pettichord, Bret (2001). 3254: 5438: 4635: 4551:"SOA Testing Tools for Black, White and Gray Box" 4058: 3696:. Wiley-IEEE Computer Society Press. p. 75. 3658: 3584: 3507:. Wiley-IEEE Computer Society Press. p. 74. 7611: 5165: 4956:. International Organization for Standardization 4518: 4516: 4331: 4109: 4088: 4086: 4033: 4031: 4029: 3958: 3740: 3631: 3143:Leitner, Andreas; Ciupa, Ilinca; Oriol, Manuel; 1997:may become unreadable, if the font is too small. 5566:Measuring the Effectiveness of Software Testers 5441:"Agile Software Development for an Agile Force" 5098:. Addison-Wesley Professional. pp. 23–39. 4904:. Pacific Northwest Software Quality Conference 4898:DevOps: Are You Pushing Bugs to Clients Faster? 4895:Ariola, Wayne; Dunlop, Cynthia (October 2015). 4868: 4696: 4604:Ammann, Paul; Offutt, Jeff (January 28, 2008). 4481: 4438:(MSc thesis). Helsinki University of Technology 4249:(2nd ed.). Indianapolis: Sams Publishing. 3992: 3978:. Tata McGraw-Hill Education. pp. 108–11. 3385:. March 31, 2011. Section 1.1.2. Archived from 3342: 3340: 3122:(2nd ed.). New York: John Wiley and Sons. 3114: 2546:A software testing process can produce several 2112:Creating a display expected output, whether as 1766: 1710:Continuous testing is the process of executing 983:There are many approaches to software testing. 5333: 5093: 5045: 5000: 4667: 4526:Core Software Security: Security at the Source 3760:. Cambridge University Press. pp. 154–5. 3641:Software Development and Professional Practice 3554: 3288:National Institute of Standards and Technology 3177: 2294:is to support development and reduce defects. 1979:that has no function on the source language's 1968:Some messages may be created automatically at 1415:Valid hardware configurations must be present. 1302:Component interface testing is a variation of 1137:Techniques used in white-box testing include: 1121:While white-box testing can be applied at the 7307: 6747: 5758:Note: This template roughly follows the 2012 5734: 5661:. Vol. 41, no. 8. pp. 99–101. 5310:IEEE standard for software test documentation 4978:. Microsoft Developer Network. Archived from 4869:Philipp-Edmonds, Cameron (December 5, 2014). 4513: 4083: 4026: 3863: 3309: 3307: 3305: 2470: 2404:Software testing is used in association with 1576:Contractual and regulatory acceptance testing 841:to maximize coverage while minimizing tests. 806:dimensions of quality (how it is supposed to 560: 5461:An example is Mark Fewster, Dorothy Graham: 4894: 4818: 4603: 4337: 3971: 3548: 3412:"Certified Tester Foundation Level Syllabus" 3379:"Certified Tester Foundation Level Syllabus" 3337: 2683: 2424:Glossary of Software Engineering Terminology 2107: 1790:. This is generally referred to as software 755:, and interacting with different software. 4646: 4499:(3rd ed.). CRC Press. pp. 68–73. 4492: 4097:. Bullseye Testing Technology. Introduction 4005: 3664: 2988: – Testing software without automation 2801:competence, or professionalism as a tester. 1490: 1355:binary." Grey-box testing may also include 717:Software testing is typically goal driven. 7314: 7300: 6754: 6740: 5741: 5727: 5504: 5151:. Addison-Wesley Professional. p. 3. 4680:Testing Techniques in Software Engineering 4676:"Chapter 1: Software Testing: An Overview" 4653:(3rd ed.). CRC Press. pp. 92–6. 4092: 4069:. John Wiley & Sons. pp. 99–121. 4044:. Cambridge University Press. p. 26. 3637: 3302: 2290:part of regression testing. Goals of this 567: 553: 5606:(2nd ed.). Microsoft Press. p. 5597: 5397: 5070: 4835: 4578: 4118: 3591:Bourque, P.; Fairley, R.D., eds. (2014). 2437:And, according to the ISO 9000 standard: 2071:better at achieving the desired outcome. 1471:). For example, in the case of a lack of 6945:Software development process/methodology 6761: 5698:) is being considered for deletion. See 5630: 5248:(coursework). Carnegie Mellon University 5176:"What is Test Driven Development (TDD)?" 4922: 4841: 4428: 4363: 4361: 4125:. John Wiley & Sons. pp. 44–6. 3173: 3171: 3118:; Falk, Jack; Nguyen, Hung Quoc (1999). 3110: 3108: 3106: 3104: 3089:(coursework). Carnegie Mellon University 2731:Certification § In software testing 2499:Quality measures include such topics as 2241: 2056:, and other software testing practices. 1922:systems are not denied access to them." 1850: 1424: 1409:A user must select a variety of options. 1229: 1104: 1029:, whereas dynamic testing also involves 926:is tested to validate expected behavior. 578: 5246:"Verification/Validation/Certification" 4862: 4408:. Pearson Education India. p. 18. 4344:. Pearson Education India. p. 63. 4269: 4012:. J. Ross Publishing. pp. 224–41. 3692:Kolawa, Adam; Huizinga, Dorota (2007). 3668:Creating a Software Engineering Culture 3503:Kolawa, Adam; Huizinga, Dorota (2007). 3178:Kolawa, Adam; Huizinga, Dorota (2007). 1882:Americans with Disabilities Act of 1990 1638:Software release life cycle § Beta 1386: 704:initially introduced the separation of 14: 7612: 6451:Knowledge representation and reasoning 5652:"Seven Principles of Software Testing" 5230:Introduction to Rapid Software Testing 5144: 5094:Gregory, Janet; Crispin, Lisa (2014). 4709:. Nova Data Corporation. p. 254. 4401: 4395: 4242: 4236: 3785:. IEEE Comput. Soc. pp. 113–122. 3229: 3044: 2576: 2534:There are a number of frequently used 2396:Verification and validation (software) 2147: 2033: 1868:Alternate Texts for multimedia content 1725: 1459:application intended to be run on the 930: 857:Testing can be categorized many ways. 521:Electrical and electronics engineering 7295: 6735: 6476:Philosophy of artificial intelligence 5722: 5649: 5559: 5523: 5400:Agile Development Conference (ADC'05) 5378: 5001:Claessen, Koen; Hughes, John (2000). 4916: 4888: 4770: 4730: 4728: 4726: 4367: 4358: 4306:"Risk and Requirements-Based Testing" 3313: 3184:. Wiley-IEEE Computer Society Press. 3168: 3101: 3080: 3078: 3050: 2822: 2582:These paragraphs are an excerpt from 2248:Capability Maturity Model Integration 2074: 1932:internationalization and localization 1926:Internationalization and localization 1699: 1646:. Versions of the software, known as 1549: 1517: 1194:, which reports on functions executed 1185:can be reported as a percentage for: 1181:have been tested. Code coverage as a 7321: 7266: 6960:Software verification and validation 6863:Component-based software engineering 5802:Energy consumption (Green computing) 5748: 5306: 5243: 5237: 4819:O'Reilly, Tim (September 30, 2005). 4543: 4300: 3726:. Cengage Learning. pp. 57–58. 3204: 2973: – term in software engineering 2790:software testing standard justified? 2390:Software verification and validation 2270: 1834: 1666:Functional vs non-functional testing 1573:Operational acceptance testing (OAT) 1219: 1148:(application programming interfaces) 1094: 979:Static, dynamic, and passive testing 860: 27:Checking software against a standard 6481:Distributed artificial intelligence 5760:ACM Computing Classification System 5705:Software testing tools and products 5126:. Testing Phase in Software Testing 4752:from the original on March 24, 2022 3754:Oberkampf, W.L.; Roy, C.J. (2010). 3084: 2338:Test development: Test procedures, 2120: 2093:Conformance testing or type testing 1902: 1343: 1275:, and specification-based testing. 762:Ensuring requirements are satisfied 744:will not be considered a failure. 675:should have the lowest proportion. 616:Software testing can determine the 24: 5993:Integrated development environment 5643: 5447:(April 2004). STSC. Archived from 4925:"Shift Left and Put Quality First" 4923:Auerbach, Adam (October 2, 2014). 4771:Woods, Anthony J. (June 5, 2015). 4723: 3671:. Addison-Wesley. pp. 211–2. 3255:Fernandes da Costa, Lucas (2021). 3075: 3026: – Software testing technique 3003: – Software testing technique 2994: – software testing technique 1986:Software may lack support for the 1601:Operations readiness and assurance 1085: 1077:Preset testing vs adaptive testing 960:This paragraph is an excerpt from 936:This paragraph is an excerpt from 912:This paragraph is an excerpt from 866:This paragraph is an excerpt from 25: 7636: 6940:Software configuration management 6807:Search-based software engineering 6792:Experimental software engineering 6461:Automated planning and scheduling 5998:Software configuration management 5702:to help reach a consensus. › 5681: 5276:Software and Systems Traceability 4842:Auerbach, Adam (August 3, 2015). 4775:(Whitepaper). Capgemini Australia 4456: 4429:Lönnberg, Jan (October 7, 2003). 3844:A Tutorial in Exploratory Testing 3823:A Tutorial in Exploratory Testing 3009: – Quality control technique 2724: 2511:requirements such as capability, 2304: 1309: 954: 844: 447:Standards and bodies of knowledge 7625:Software engineering terminology 7564:Graphical user interface testing 7276: 7275: 7265: 6715: 6705: 6696: 6695: 5439:Willison, John S. (April 2004). 5055:"The growth of software testing" 4607:Introduction to Software Testing 4041:Introduction to Software Testing 3864:Lee, D.; Yannakakis, M. (1996). 2971:Graphical user interface testing 2737: 2659:This section is an excerpt from 2283:test-driven software development 1622: 1392:This section is an excerpt from 1339:Graphical user interface testing 1054:This section is an excerpt from 793: 6706: 6109:Computational complexity theory 5650:Meyer, Bertrand (August 2008). 5591: 5553: 5517: 5498: 5476: 5455: 5432: 5391: 5372: 5327: 5300: 5220: 5194: 5138: 5112: 5087: 5039: 4994: 4968: 4943: 4812: 4787: 4764: 4597: 4523:Ransome, J.; Misra, A. (2013). 4450: 4422: 4405:Foundations of Software Testing 4374:. William Andrew. p. 313. 4341:Foundations of Software Testing 4294: 4263: 4139: 4038:Ammann, P.; Offutt, J. (2016). 3923: 3888: 3857: 3835: 3815: 3774: 3723:Foundations of Software Testing 3521: 3496: 3463: 3440: 3404: 3371: 3257:Testing JavaScript Applications 3209:. Addison-Wesley Professional. 3147:; Fiva, Arno (September 2007). 2698: 2318:software development life cycle 1876:Common Standards for compliance 1631: 1463:now being required to become a 906: 720: 594:is the act of checking whether 539:Outline of software development 6787:Empirical software engineering 5900:Network performance evaluation 5505:Paul Krill (August 22, 2014). 5402:. ieee.org. pp. 318–322. 5009:. Icfp '00. pp. 268–279. 3563:. 3.0. IEEE Computer Society. 3273: 3248: 3223: 3198: 3136: 2750:software testing controversies 2743: 2640: 2162: 2059: 1048: 810:versus what it is supposed to 13: 1: 6264:Multimedia information system 6249:Geographic information system 6239:Enterprise information system 5835:Computer systems organization 5687: 5381:"We're All Part of the Story" 5379:Strom, David (July 1, 2009). 4529:. CRC Press. pp. 140–3. 3593:"Chapter 4: Software Testing" 3037: 3007:Reverse semantic traceability 2980:Independent test organization 2653: 1570:User acceptance testing (UAT) 1018:/drivers or execution from a 7589:Software reliability testing 7528:Software performance testing 6812:Site reliability engineering 6623:Computational social science 6211:Theoretical computer science 6031:Software development process 5807:Electronic design automation 5792:Very Large Scale Integration 5120:"Software Testing Lifecycle" 4270:Laycock, Gilbert T. (1993). 3907:10.1007/978-3-642-24580-0_12 3085:Pan, Jiantao (Spring 1999). 2775:Manual vs. automated testing 2621: 2553: 2541: 2233: 1892:Web Accessibility Initiative 1773:Software performance testing 1767:Software performance testing 678: 7: 6817:Social software engineering 6446:Natural language processing 6234:Information storage systems 5572:. STAR East. Archived from 5284:10.1007/978-1-4471-2239-5_1 5206:Microsoft Developer Network 4581:The Art of Software Testing 3602:. IEEE. pp. 4–1–4–17. 3356:10.1109/IEEESTD.1990.101064 3320:The Art of Software Testing 3230:Molina, Alessandro (2021). 2928: 2716: 2494: 2406:verification and validation 2178: 2127:property testing algorithms 1720:non-functional requirements 1298:Component interface testing 768:non-functional requirements 10: 7641: 7431:Testing types, techniques, 6955:Software quality assurance 6362:Human–computer interaction 6332:Intrusion detection system 6244:Social information systems 6229:Database management system 5148:Effective Software Testing 4736:"ISTQB CTFL Syllabus 2018" 4612:Cambridge University Press 4432:Visual testing of software 4402:Mathur, Aditya P. (2007). 4093:Cornett, Steve (c. 1996). 3936:. IEEE. pp. 224–228. 3644:. APress. pp. 193–4. 2778:Some writers believe that 2728: 2702: 2687: 2658: 2625: 2581: 2557: 2477:software quality assurance 2471:Software quality assurance 2393: 2382: 2378: 2276:Agile software development 2245: 2151: 2124: 2096: 2078: 2063: 2037: 1770: 1755: 1729: 1703: 1674:particular feature work." 1635: 1553: 1521: 1494: 1428: 1391: 1347: 1336: 1223: 1098: 1053: 959: 935: 911: 865: 850: 696: 302:Software quality assurance 7556: 7430: 7399: 7329: 7261: 7220: 7185: 7124: 7038: 7031: 6990: 6850: 6769: 6691: 6628:Computational engineering 6603:Computational mathematics 6580: 6527: 6489: 6436: 6398: 6360: 6302: 6219: 6165: 6127: 6079: 6016: 5949: 5913: 5870: 5834: 5767: 5756: 5598:McConnell, Steve (2004). 5463:Software Test Automation. 5145:Dustin, Elfriede (2002). 5059:Communications of the ACM 4368:Clapp, Judith A. (1995). 4222: 4201: 4150: 4145:As a simple example, the 3120:Testing Computer Software 2847: 2825: 2684:Test fixture or test data 2108:Output comparison testing 1896:World Wide Web Consortium 1688:, behavior under certain 1588:quality management system 1467:, which must render in a 1109:White Box Testing Diagram 903:is the focus of a test. 894: 620:of software for specific 598:satisfies expectations. 7574:Orthogonal array testing 7523:Smoke testing (software) 7493:Dynamic program analysis 7111:Model-driven engineering 6910:Functional specification 6893:Software incompatibility 6802:Requirements engineering 6638:Computational healthcare 6633:Differentiable computing 6552:Graphics processing unit 5978:Domain-specific language 5847:Computational complexity 5700:templates for discussion 4221:will succeed, except if 4095:"Code Coverage Analysis" 3791:10.1109/icnp.1997.643699 3013:Software testing tactics 2992:Orthogonal array testing 2959:Dynamic program analysis 2786:Is the existence of the 2400:Software quality control 2183: 2125:Not to be confused with 1751:software fault injection 1743:Software fault injection 1497:Smoke testing (software) 1491:Smoke and sanity testing 1241:equivalence partitioning 1025:Static testing involves 853:Software testing tactics 712: 287:Configuration management 6905:Enterprise architecture 6613:Computational chemistry 6547:Photograph manipulation 6438:Artificial intelligence 6254:Decision support system 5348:10.1145/2393596.2393634 5244:Tran, Eushiuan (1999). 4281:University of Sheffield 3870:Proceedings of the IEEE 3323:. John Wiley and Sons. 2195:In the 1980s, the term 1990:of the target language. 1716:functional requirements 1644:user acceptance testing 1611:aspects of the system. 1512:build verification test 1253:state transition tables 1245:boundary value analysis 1008:static program analysis 511:Artificial intelligence 7116:Round-trip engineering 6873:Backward compatibility 6868:Software compatibility 6678:Educational technology 6509:Reinforcement learning 6259:Process control system 6157:Computational geometry 6147:Algorithmic efficiency 6142:Analysis of algorithms 5797:Systems on Chip (SoCs) 5488:commonsensetesting.org 5465:Addison Wesley, 1999, 2950:, testing of databases 2926: 2925: 2911: 2292:continuous integration 1678:Non-functional testing 1579:Alpha and beta testing 1534:unintended consequence 1473:backward compatibility 1235: 1110: 950:are tested as a group. 673:end to end (e2e) tests 588: 435:Infrastructure as code 281:Supporting disciplines 7453:Compatibility testing 6935:Software architecture 6888:Forward compatibility 6648:Electronic publishing 6618:Computational biology 6608:Computational physics 6504:Unsupervised learning 6418:Distributed computing 6294:Information retrieval 6201:Mathematical analysis 6191:Mathematical software 6081:Theory of computation 6046:Software construction 6036:Requirements analysis 5914:Software organization 5842:Computer architecture 5812:Hardware acceleration 5777:Printed circuit board 5015:10.1145/351240.351266 4583:(2 ed.). Wiley. 4338:Mathur, A.P. (2011). 4233:happens to be chosen. 3972:Limaye, M.G. (2009). 3457:10.1109/ICST.2012.142 3054:(November 17, 2006). 2942:Cross-browser testing 2916: 2912: 2823:Cost to fix a defect 2815:continuous deployment 2810: 2756:Agile vs. traditional 2729:Further information: 2527:, compatibility, and 2314:Requirements analysis 2258:waterfall development 2246:Further information: 2242:Waterfall development 2019:environment variables 1851:Accessibility testing 1756:Further information: 1447:(or operating system 1431:Compatibility testing 1425:Compatibility testing 1337:Further information: 1233: 1108: 873:In software testing, 683:A study conducted by 582: 292:Deployment management 7498:Installation testing 7488:Differential testing 7233:Computer engineering 6930:Software archaeology 6920:Programming paradigm 6832:Software maintenance 6777:Computer programming 6763:Software engineering 6408:Concurrent computing 6380:Ubiquitous computing 6352:Application security 6347:Information security 6176:Discrete mathematics 6152:Randomized algorithm 6104:Computability theory 6089:Model of computation 6061:Software maintenance 6056:Software engineering 6018:Software development 5968:Programming language 5963:Programming paradigm 5880:Network architecture 5541:on November 27, 2009 5451:on October 29, 2005. 4647:Lewis, W.E. (2016). 4493:Lewis, W.E. (2016). 4243:Patton, Ron (2005). 4009:Software Engineering 4006:Saleh, K.A. (2009). 3942:10.1109/HASE.2014.39 3665:Wiegers, K. (2013). 3428:on December 17, 2008 3234:. Packt Publishing. 3018:Test management tool 2668:software development 2591:software development 2481:software engineering 2281:One agile practice, 2224:automation developer 2190:software development 2087:concurrent computing 2050:static code analysis 1603:(OR&A) testing. 1596:software maintenance 1592:software development 1530:software regressions 1441:application software 1403:installation testing 1394:Installation testing 1387:Installation testing 1068:and test execution. 1039:runtime verification 609:of its failure to a 605:of software and the 112:Paradigms and models 41:Software development 7483:Development testing 7478:Destructive testing 7468:Conformance testing 7412:Integration testing 7357:Model-based testing 7347:Exploratory testing 7253:Systems engineering 7238:Information science 7018:Service orientation 6970:Structured analysis 6878:Compatibility layer 6822:Software deployment 6683:Document management 6673:Operations research 6598:Enterprise software 6514:Multi-task learning 6499:Supervised learning 6221:Information systems 6051:Software deployment 6008:Software repository 5862:Real-time computing 5667:10.1109/MC.2008.306 5494:on October 2, 2014. 5408:10.1109/ADC.2005.45 5387:on August 31, 2009. 5278:. Springer London. 5272:Cleland-Huang, Jane 5072:10.1145/62959.62965 3638:Dooley, J. (2011). 3392:on October 28, 2017 3205:Cohn, Mike (2009). 3057:Exploratory Testing 2965:Formal verification 2609:, detailed design, 2599:baselined documents 2595:traceability matrix 2584:Traceability matrix 2577:Traceability matrix 2285:(TDD), is a way of 2154:Metamorphic testing 2148:Metamorphic testing 2099:Conformance testing 2040:Development testing 2034:Development testing 2015:configuration files 2005:bi-directional text 1975:Software may use a 1965:in the source code. 1819:scalability testing 1732:Destructive testing 1726:Destructive testing 1361:integration testing 1357:reverse engineering 1331:exploratory testing 1273:exploratory testing 1265:model-based testing 1062:Exploratory testing 1056:Exploratory testing 1037:related to offline 944:Integration testing 938:Integration testing 931:Integration testing 884:continuous delivery 650:and its associated 35:Part of a series on 7538:Symbolic execution 7513:Regression testing 7473:Continuous testing 7463:Concurrent testing 7407:Acceptance testing 7330:The "box" approach 7243:Project management 7008:Object orientation 6975:Essential analysis 6883:Compatibility mode 6466:Search methodology 6413:Parallel computing 6370:Interaction design 6279:Computing platform 6206:Numerical analysis 6196:Information theory 5988:Software framework 5951:Software notations 5890:Network components 5787:Integrated circuit 5313:. New York: IEEE. 5208:. January 14, 2009 5182:. December 5, 2015 5096:More Agile Testing 4557:on October 1, 2018 4119:Black, R. (2011). 3849:2013-06-12 at the 3828:2013-06-12 at the 3478:. Wiley. pp. 3315:Myers, Glenford J. 3087:"Software Testing" 2761:process "maturity" 2748:Some of the major 2368:Regression testing 2228:test administrator 2081:Concurrent testing 2075:Concurrent testing 1988:character encoding 1936:pseudolocalization 1825:Real-time software 1758:Exception handling 1706:Continuous testing 1700:Continuous testing 1671:Functional testing 1605:Functional testing 1556:Acceptance testing 1550:Acceptance testing 1524:Regression testing 1518:Regression testing 1378:exception handling 1236: 1198:Statement coverage 1116:in-circuit testing 1111: 999:is referred to as 888:continuous testing 589: 430:Release automation 307:Project management 7607: 7606: 7548:Usability testing 7374:White-box testing 7342:All-pairs testing 7337:Black-box testing 7289: 7288: 7216: 7215: 7157:Information model 7061:Incremental model 6915:Modeling language 6729: 6728: 6658:Electronic voting 6588:Quantum Computing 6581:Applied computing 6567:Image compression 6337:Hardware security 6327:Security services 6284:Digital marketing 6071:Open-source model 5983:Modeling language 5895:Network scheduler 5617:978-0-7356-1967-8 5579:on March 26, 2010 5471:978-0-201-33140-0 5417:978-0-7695-2487-0 5320:978-0-7381-1443-9 5158:978-0-201-79429-8 5105:978-0-13-374956-4 5024:978-1-58113-202-1 4929:TechWell Insights 4848:TechWell Insights 4821:"What is Web 2.0" 4716:978-0-8155-1363-6 4689:978-3-642-14334-2 4660:978-1-4398-3436-7 4621:978-0-521-88038-1 4536:978-1-4665-6095-6 4506:978-1-4398-3436-7 4415:978-81-317-1660-1 4381:978-0-8155-1363-6 4351:978-81-317-5908-0 4256:978-0-672-32798-8 4132:978-1-118-07938-6 4076:978-0-470-14634-7 4051:978-1-316-77312-3 4019:978-1-932159-94-3 3985:978-0-07-013990-9 3951:978-1-4799-3466-9 3916:978-3-642-24579-4 3800:978-0-8186-8061-8 3767:978-1-139-49176-1 3733:978-1-84480-989-9 3703:978-0-470-04212-0 3678:978-0-13-348929-3 3651:978-1-4302-3801-0 3609:978-0-7695-5166-1 3570:978-0-7695-5166-1 3541:978-3-319-24647-5 3514:978-0-470-04212-0 3489:978-0-471-08112-8 3365:978-1-55937-067-7 3330:978-0-471-04328-7 3191:978-0-470-04212-0 3129:978-0-471-35846-6 2910: 2909: 2607:high-level design 2489:quality assurance 2271:Agile development 1977:keyboard shortcut 1840:Usability testing 1835:Usability testing 1829:real-time testing 1812:Stability testing 1796:endurance testing 1745:, in the form of 1445:operating systems 1304:black-box testing 1249:all-pairs testing 1234:Black box diagram 1226:Black-box testing 1220:Black-box testing 1204:Decision coverage 1192:Function coverage 1101:White-box testing 1095:White-box testing 861:Automated testing 749:computer hardware 702:Glenford J. Myers 669:integration tests 577: 576: 468:ISO/IEC standards 16:(Redirected from 7632: 7620:Software testing 7518:Security testing 7503:Negative testing 7458:Concolic testing 7384:Mutation testing 7369:Grey-box testing 7362:Scenario testing 7323:Software testing 7316: 7309: 7302: 7293: 7292: 7279: 7278: 7269: 7268: 7228:Computer science 7036: 7035: 6950:Software quality 6842:Systems analysis 6837:Software testing 6756: 6749: 6742: 6733: 6732: 6719: 6718: 6709: 6708: 6699: 6698: 6519:Cross-validation 6491:Machine learning 6375:Social computing 6342:Network security 6137:Algorithm design 6066:Programming team 6026:Control variable 6003:Software library 5941:Software quality 5936:Operating system 5885:Network protocol 5750:Computer science 5743: 5736: 5729: 5720: 5719: 5677: 5675: 5673: 5656: 5637: 5636: 5628: 5622: 5621: 5605: 5595: 5589: 5588: 5586: 5584: 5578: 5571: 5557: 5551: 5550: 5548: 5546: 5540: 5534:. Archived from 5533: 5521: 5515: 5514: 5502: 5496: 5495: 5490:. Archived from 5480: 5474: 5459: 5453: 5452: 5436: 5430: 5429: 5395: 5389: 5388: 5376: 5370: 5369: 5331: 5325: 5324: 5304: 5298: 5297: 5267: 5258: 5257: 5255: 5253: 5241: 5235: 5234: 5224: 5218: 5217: 5215: 5213: 5198: 5192: 5191: 5189: 5187: 5172: 5163: 5162: 5142: 5136: 5135: 5133: 5131: 5116: 5110: 5109: 5091: 5085: 5084: 5074: 5053:(June 1, 1988). 5043: 5037: 5036: 4998: 4992: 4991: 4989: 4987: 4982:on June 23, 2012 4972: 4966: 4965: 4963: 4961: 4950:"Section 4.38". 4947: 4941: 4940: 4938: 4936: 4920: 4914: 4913: 4911: 4909: 4903: 4892: 4886: 4885: 4883: 4881: 4866: 4860: 4859: 4857: 4855: 4839: 4833: 4832: 4830: 4828: 4816: 4810: 4809: 4807: 4805: 4799: 4791: 4785: 4784: 4782: 4780: 4768: 4762: 4761: 4759: 4757: 4751: 4740: 4732: 4721: 4720: 4700: 4694: 4693: 4671: 4665: 4664: 4644: 4633: 4632: 4630: 4628: 4601: 4595: 4594: 4576: 4567: 4566: 4564: 4562: 4547: 4541: 4540: 4520: 4511: 4510: 4490: 4479: 4478: 4476: 4474: 4469:on July 24, 2012 4465:. Archived from 4459:"Visual testing" 4454: 4448: 4447: 4445: 4443: 4437: 4426: 4420: 4419: 4399: 4393: 4392: 4390: 4388: 4365: 4356: 4355: 4335: 4329: 4328: 4326: 4324: 4310: 4298: 4292: 4291: 4289: 4287: 4278: 4267: 4261: 4260: 4246:Software Testing 4240: 4234: 4232: 4231: 4228: 4225: 4220: 4219: 4216: 4213: 4210: 4207: 4204: 4199: 4198: 4195: 4192: 4189: 4186: 4183: 4180: 4177: 4174: 4171: 4168: 4165: 4162: 4159: 4156: 4153: 4143: 4137: 4136: 4116: 4107: 4106: 4104: 4102: 4090: 4081: 4080: 4062: 4056: 4055: 4035: 4024: 4023: 4003: 3990: 3989: 3975:Software Testing 3969: 3956: 3955: 3927: 3921: 3920: 3892: 3886: 3885: 3882:10.1109/5.533956 3876:(8): 1090–1123. 3861: 3855: 3839: 3833: 3819: 3813: 3812: 3778: 3772: 3771: 3751: 3738: 3737: 3717: 3708: 3707: 3689: 3683: 3682: 3662: 3656: 3655: 3635: 3629: 3628: 3626: 3624: 3619:on June 19, 2018 3618: 3612:. Archived from 3597: 3588: 3582: 3581: 3579: 3577: 3552: 3546: 3545: 3525: 3519: 3518: 3500: 3494: 3493: 3477: 3467: 3461: 3460: 3444: 3438: 3437: 3435: 3433: 3427: 3416: 3408: 3402: 3401: 3399: 3397: 3391: 3375: 3369: 3368: 3344: 3335: 3334: 3311: 3300: 3299: 3297: 3295: 3285: 3277: 3271: 3270: 3252: 3246: 3245: 3227: 3221: 3220: 3202: 3196: 3195: 3175: 3166: 3165: 3163: 3161: 3155: 3140: 3134: 3133: 3112: 3099: 3098: 3096: 3094: 3082: 3073: 3072: 3070: 3068: 3062: 3048: 2997: 2976: 2948:Database testing 2848:Time introduced 2820: 2819: 2536:software metrics 2503:, completeness, 2385:Software quality 2121:Property testing 2023:formats for date 1912:system intrusion 1908:Security testing 1903:Security testing 1778:resource usage. 1762:Recovery testing 1350:Gray box testing 1344:Grey-box testing 1164:Mutation testing 592:Software testing 569: 562: 555: 516:Computer science 425:Build automation 32: 31: 21: 7640: 7639: 7635: 7634: 7633: 7631: 7630: 7629: 7610: 7609: 7608: 7603: 7552: 7543:Test automation 7432: 7426: 7395: 7325: 7320: 7290: 7285: 7257: 7248:Risk management 7212: 7181: 7120: 7101:Waterfall model 7071:Prototype model 7066:Iterative model 7027: 7003:Aspect-oriented 6986: 6965:Software system 6846: 6827:Software design 6765: 6760: 6730: 6725: 6716: 6687: 6668:Word processing 6576: 6562:Virtual reality 6523: 6485: 6456:Computer vision 6432: 6428:Multiprocessing 6394: 6356: 6322:Security hacker 6298: 6274:Digital library 6215: 6166:Mathematics of 6161: 6123: 6099:Automata theory 6094:Formal language 6075: 6041:Software design 6012: 5945: 5931:Virtual machine 5909: 5905:Network service 5866: 5857:Embedded system 5830: 5763: 5752: 5747: 5703: 5684: 5671: 5669: 5654: 5646: 5644:Further reading 5641: 5640: 5629: 5625: 5618: 5596: 5592: 5582: 5580: 5576: 5569: 5558: 5554: 5544: 5542: 5538: 5531: 5522: 5518: 5503: 5499: 5482: 5481: 5477: 5460: 5456: 5437: 5433: 5418: 5396: 5392: 5377: 5373: 5358: 5332: 5328: 5321: 5305: 5301: 5294: 5270:Gotel, Orlena; 5268: 5261: 5251: 5249: 5242: 5238: 5225: 5221: 5211: 5209: 5200: 5199: 5195: 5185: 5183: 5174: 5173: 5166: 5159: 5143: 5139: 5129: 5127: 5118: 5117: 5113: 5106: 5092: 5088: 5047:Gelperin, David 5044: 5040: 5025: 4999: 4995: 4985: 4983: 4974: 4973: 4969: 4959: 4957: 4949: 4948: 4944: 4934: 4932: 4931:. TechWell Corp 4921: 4917: 4907: 4905: 4901: 4893: 4889: 4879: 4877: 4867: 4863: 4853: 4851: 4850:. TechWell Corp 4840: 4836: 4826: 4824: 4817: 4813: 4803: 4801: 4797: 4793: 4792: 4788: 4778: 4776: 4769: 4765: 4755: 4753: 4749: 4738: 4734: 4733: 4724: 4717: 4701: 4697: 4690: 4672: 4668: 4661: 4645: 4636: 4626: 4624: 4622: 4614:. p. 215. 4602: 4598: 4591: 4577: 4570: 4560: 4558: 4549: 4548: 4544: 4537: 4521: 4514: 4507: 4491: 4482: 4472: 4470: 4457:Chima, Raspal. 4455: 4451: 4441: 4439: 4435: 4427: 4423: 4416: 4400: 4396: 4386: 4384: 4382: 4366: 4359: 4352: 4336: 4332: 4322: 4320: 4308: 4299: 4295: 4285: 4283: 4276: 4268: 4264: 4257: 4241: 4237: 4229: 4226: 4223: 4217: 4214: 4211: 4208: 4205: 4202: 4196: 4193: 4190: 4187: 4184: 4181: 4178: 4175: 4172: 4169: 4166: 4163: 4160: 4157: 4154: 4151: 4144: 4140: 4133: 4117: 4110: 4100: 4098: 4091: 4084: 4077: 4063: 4059: 4052: 4036: 4027: 4020: 4004: 3993: 3986: 3970: 3959: 3952: 3928: 3924: 3917: 3893: 3889: 3862: 3858: 3851:Wayback Machine 3840: 3836: 3830:Wayback Machine 3820: 3816: 3801: 3779: 3775: 3768: 3752: 3741: 3734: 3718: 3711: 3704: 3690: 3686: 3679: 3663: 3659: 3652: 3636: 3632: 3622: 3620: 3616: 3610: 3595: 3589: 3585: 3575: 3573: 3571: 3553: 3549: 3542: 3526: 3522: 3515: 3501: 3497: 3490: 3468: 3464: 3445: 3441: 3431: 3429: 3425: 3414: 3410: 3409: 3405: 3395: 3393: 3389: 3377: 3376: 3372: 3366: 3346: 3345: 3338: 3331: 3312: 3303: 3293: 3291: 3283: 3279: 3278: 3274: 3267: 3253: 3249: 3242: 3228: 3224: 3217: 3203: 3199: 3192: 3176: 3169: 3159: 3157: 3153: 3145:Meyer, Bertrand 3141: 3137: 3130: 3113: 3102: 3092: 3090: 3083: 3076: 3066: 3064: 3060: 3049: 3045: 3040: 3035: 2995: 2974: 2936:Data validation 2931: 2923:Boehm's claims. 2780:test automation 2770:Waterfall model 2746: 2733: 2727: 2719: 2707: 2701: 2692: 2686: 2681: 2680: 2664: 2656: 2643: 2630: 2624: 2619: 2618: 2587: 2579: 2562: 2556: 2544: 2525:maintainability 2497: 2473: 2402: 2394:Main articles: 2392: 2387: 2381: 2323:Test planning: 2307: 2273: 2254: 2252:Waterfall model 2244: 2236: 2197:software tester 2186: 2181: 2165: 2156: 2150: 2130: 2123: 2114:data comparison 2110: 2101: 2095: 2083: 2077: 2068: 2062: 2042: 2036: 1981:keyboard layout 1928: 1905: 1853: 1837: 1775: 1769: 1764: 1734: 1728: 1712:automated tests 1708: 1702: 1668: 1640: 1634: 1625: 1558: 1552: 1526: 1520: 1499: 1493: 1465:Web application 1433: 1427: 1422: 1421: 1397: 1389: 1352: 1346: 1341: 1312: 1228: 1222: 1183:software metric 1179:function points 1158:Fault injection 1103: 1097: 1088: 1086:Black/white box 1079: 1074: 1073: 1059: 1051: 1001:dynamic testing 981: 976: 975: 972:software system 965: 957: 952: 951: 948:software system 941: 933: 928: 927: 917: 909: 901:software system 897: 892: 891: 877:is the use of 875:test automation 871: 868:Test automation 863: 855: 847: 796: 780:maintainability 764: 723: 715: 699: 681: 573: 544: 543: 534: 526: 525: 506: 498: 497: 448: 440: 439: 390: 380: 379: 325: 317: 316: 312:User experience 282: 274: 273: 164: 153: 152: 113: 105: 104: 50: 49:Core activities 28: 23: 22: 15: 12: 11: 5: 7638: 7628: 7627: 7622: 7605: 7604: 7602: 7601: 7596: 7594:Stress testing 7591: 7586: 7581: 7576: 7571: 7569:Manual testing 7566: 7560: 7558: 7554: 7553: 7551: 7550: 7545: 7540: 7535: 7533:Stress testing 7530: 7525: 7520: 7515: 7510: 7508:Random testing 7505: 7500: 7495: 7490: 7485: 7480: 7475: 7470: 7465: 7460: 7455: 7450: 7445: 7439: 7437: 7428: 7427: 7425: 7424: 7419: 7417:System testing 7414: 7409: 7403: 7401: 7400:Testing levels 7397: 7396: 7394: 7393: 7392: 7391: 7389:Static testing 7386: 7381: 7371: 7366: 7365: 7364: 7359: 7354: 7349: 7344: 7333: 7331: 7327: 7326: 7319: 7318: 7311: 7304: 7296: 7287: 7286: 7284: 7283: 7273: 7262: 7259: 7258: 7256: 7255: 7250: 7245: 7240: 7235: 7230: 7224: 7222: 7221:Related fields 7218: 7217: 7214: 7213: 7211: 7210: 7205: 7200: 7195: 7189: 7187: 7183: 7182: 7180: 7179: 7174: 7169: 7164: 7159: 7154: 7152:Function model 7149: 7144: 7139: 7134: 7128: 7126: 7122: 7121: 7119: 7118: 7113: 7108: 7103: 7098: 7093: 7088: 7083: 7078: 7073: 7068: 7063: 7058: 7056:Executable UML 7053: 7048: 7042: 7040: 7033: 7029: 7028: 7026: 7025: 7020: 7015: 7010: 7005: 7000: 6994: 6992: 6988: 6987: 6985: 6984: 6979: 6978: 6977: 6967: 6962: 6957: 6952: 6947: 6942: 6937: 6932: 6927: 6922: 6917: 6912: 6907: 6902: 6897: 6896: 6895: 6890: 6885: 6880: 6875: 6865: 6860: 6854: 6852: 6848: 6847: 6845: 6844: 6839: 6834: 6829: 6824: 6819: 6814: 6809: 6804: 6799: 6797:Formal methods 6794: 6789: 6784: 6779: 6773: 6771: 6767: 6766: 6759: 6758: 6751: 6744: 6736: 6727: 6726: 6724: 6723: 6713: 6703: 6692: 6689: 6688: 6686: 6685: 6680: 6675: 6670: 6665: 6660: 6655: 6650: 6645: 6640: 6635: 6630: 6625: 6620: 6615: 6610: 6605: 6600: 6595: 6590: 6584: 6582: 6578: 6577: 6575: 6574: 6572:Solid modeling 6569: 6564: 6559: 6554: 6549: 6544: 6539: 6533: 6531: 6525: 6524: 6522: 6521: 6516: 6511: 6506: 6501: 6495: 6493: 6487: 6486: 6484: 6483: 6478: 6473: 6471:Control method 6468: 6463: 6458: 6453: 6448: 6442: 6440: 6434: 6433: 6431: 6430: 6425: 6423:Multithreading 6420: 6415: 6410: 6404: 6402: 6396: 6395: 6393: 6392: 6387: 6382: 6377: 6372: 6366: 6364: 6358: 6357: 6355: 6354: 6349: 6344: 6339: 6334: 6329: 6324: 6319: 6317:Formal methods 6314: 6308: 6306: 6300: 6299: 6297: 6296: 6291: 6289:World Wide Web 6286: 6281: 6276: 6271: 6266: 6261: 6256: 6251: 6246: 6241: 6236: 6231: 6225: 6223: 6217: 6216: 6214: 6213: 6208: 6203: 6198: 6193: 6188: 6183: 6178: 6172: 6170: 6163: 6162: 6160: 6159: 6154: 6149: 6144: 6139: 6133: 6131: 6125: 6124: 6122: 6121: 6116: 6111: 6106: 6101: 6096: 6091: 6085: 6083: 6077: 6076: 6074: 6073: 6068: 6063: 6058: 6053: 6048: 6043: 6038: 6033: 6028: 6022: 6020: 6014: 6013: 6011: 6010: 6005: 6000: 5995: 5990: 5985: 5980: 5975: 5970: 5965: 5959: 5957: 5947: 5946: 5944: 5943: 5938: 5933: 5928: 5923: 5917: 5915: 5911: 5910: 5908: 5907: 5902: 5897: 5892: 5887: 5882: 5876: 5874: 5868: 5867: 5865: 5864: 5859: 5854: 5849: 5844: 5838: 5836: 5832: 5831: 5829: 5828: 5819: 5814: 5809: 5804: 5799: 5794: 5789: 5784: 5779: 5773: 5771: 5765: 5764: 5757: 5754: 5753: 5746: 5745: 5738: 5731: 5723: 5717: 5716: 5711: 5683: 5682:External links 5680: 5679: 5678: 5645: 5642: 5639: 5638: 5623: 5616: 5590: 5552: 5516: 5497: 5475: 5454: 5431: 5416: 5390: 5371: 5356: 5326: 5319: 5299: 5292: 5259: 5236: 5219: 5193: 5180:Agile Alliance 5164: 5157: 5137: 5111: 5104: 5086: 5065:(6): 687–695. 5038: 5023: 4993: 4967: 4942: 4915: 4887: 4861: 4834: 4811: 4786: 4763: 4722: 4715: 4695: 4688: 4666: 4659: 4634: 4620: 4596: 4589: 4568: 4542: 4535: 4512: 4505: 4480: 4449: 4421: 4414: 4394: 4380: 4357: 4350: 4330: 4293: 4262: 4255: 4235: 4138: 4131: 4108: 4082: 4075: 4057: 4050: 4025: 4018: 3991: 3984: 3957: 3950: 3922: 3915: 3887: 3856: 3834: 3814: 3799: 3773: 3766: 3739: 3732: 3709: 3702: 3684: 3677: 3657: 3650: 3630: 3608: 3583: 3569: 3547: 3540: 3520: 3513: 3495: 3488: 3462: 3439: 3403: 3370: 3364: 3350:, IEEE, 1990, 3336: 3329: 3301: 3272: 3266:978-1617297915 3265: 3247: 3241:978-1838642655 3240: 3222: 3216:978-0321579362 3215: 3197: 3190: 3167: 3135: 3128: 3100: 3074: 3042: 3041: 3039: 3036: 3034: 3033: 3027: 3021: 3015: 3010: 3004: 2998: 2989: 2986:Manual testing 2983: 2977: 2968: 2962: 2956: 2954:Domain testing 2951: 2945: 2939: 2932: 2930: 2927: 2908: 2907: 2904: 2901: 2898: 2895: 2892: 2888: 2887: 2884: 2881: 2878: 2875: 2872: 2868: 2867: 2864: 2861: 2858: 2855: 2852: 2849: 2845: 2844: 2841: 2838: 2835: 2832: 2828: 2827: 2826:Time detected 2824: 2809: 2808: 2805: 2802: 2798: 2795: 2791: 2784: 2776: 2773: 2757: 2745: 2742: 2726: 2725:Certifications 2723: 2718: 2715: 2703:Main article: 2700: 2697: 2688:Main article: 2685: 2682: 2665: 2657: 2655: 2652: 2642: 2639: 2626:Main article: 2623: 2620: 2588: 2580: 2578: 2575: 2558:Main article: 2555: 2552: 2543: 2540: 2496: 2493: 2472: 2469: 2446: 2445: 2442: 2435: 2434: 2431: 2417: 2416: 2413: 2391: 2388: 2383:Main article: 2380: 2377: 2376: 2375: 2371: 2365: 2362: 2358: 2351: 2347: 2340:test scenarios 2336: 2321: 2306: 2305:Sample process 2303: 2272: 2269: 2243: 2240: 2235: 2232: 2185: 2182: 2180: 2177: 2164: 2161: 2152:Main article: 2149: 2146: 2122: 2119: 2109: 2106: 2097:Main article: 2094: 2091: 2079:Main article: 2076: 2073: 2064:Main article: 2061: 2058: 2038:Main article: 2035: 2032: 2031: 2030: 2021:and different 2011: 2008: 2001: 1998: 1995:CJK characters 1991: 1984: 1973: 1966: 1959: 1956: 1953: 1927: 1924: 1904: 1901: 1900: 1899: 1889: 1884: 1873: 1872: 1869: 1866: 1863: 1852: 1849: 1836: 1833: 1807:Stress testing 1801:Volume testing 1771:Main article: 1768: 1765: 1730:Main article: 1727: 1724: 1704:Main article: 1701: 1698: 1667: 1664: 1660:perpetual beta 1633: 1630: 1624: 1621: 1609:non-functional 1581: 1580: 1577: 1574: 1571: 1554:Main article: 1551: 1548: 1522:Main article: 1519: 1516: 1502:Sanity testing 1495:Main article: 1492: 1489: 1429:Main article: 1426: 1423: 1420: 1419: 1416: 1413: 1410: 1398: 1390: 1388: 1385: 1348:Main article: 1345: 1342: 1327:Ad hoc testing 1311: 1310:Visual testing 1308: 1289:non-functional 1257:decision table 1224:Main article: 1221: 1218: 1210: 1209: 1208: 1207: 1201: 1195: 1174: 1173: 1170:Static testing 1167: 1161: 1155: 1149: 1099:Main article: 1096: 1093: 1087: 1084: 1078: 1075: 1060: 1052: 1050: 1047: 980: 977: 968:System testing 966: 962:System testing 958: 956: 955:System testing 953: 942: 934: 932: 929: 918: 910: 908: 905: 896: 893: 872: 864: 862: 859: 851:Main article: 846: 845:Categorization 843: 804:non-functional 795: 792: 763: 760: 733:assistance to 722: 719: 714: 711: 709:verification. 698: 695: 680: 677: 667:, followed by 637:specifications 575: 574: 572: 571: 564: 557: 549: 546: 545: 542: 541: 535: 532: 531: 528: 527: 524: 523: 518: 513: 507: 504: 503: 500: 499: 496: 495: 490: 485: 480: 475: 470: 465: 460: 458:IEEE standards 455: 449: 446: 445: 442: 441: 438: 437: 432: 427: 422: 417: 412: 407: 402: 397: 391: 386: 385: 382: 381: 378: 377: 372: 367: 362: 357: 352: 347: 342: 337: 332: 326: 323: 322: 319: 318: 315: 314: 309: 304: 299: 294: 289: 283: 280: 279: 276: 275: 272: 271: 266: 261: 256: 251: 246: 241: 236: 231: 226: 221: 216: 211: 206: 201: 196: 191: 186: 181: 176: 171: 165: 163:and frameworks 159: 158: 155: 154: 151: 150: 145: 140: 135: 130: 125: 120: 114: 111: 110: 107: 106: 103: 102: 97: 92: 87: 82: 77: 72: 67: 62: 57: 51: 48: 47: 44: 43: 37: 36: 26: 9: 6: 4: 3: 2: 7637: 7626: 7623: 7621: 7618: 7617: 7615: 7600: 7597: 7595: 7592: 7590: 7587: 7585: 7582: 7580: 7577: 7575: 7572: 7570: 7567: 7565: 7562: 7561: 7559: 7555: 7549: 7546: 7544: 7541: 7539: 7536: 7534: 7531: 7529: 7526: 7524: 7521: 7519: 7516: 7514: 7511: 7509: 7506: 7504: 7501: 7499: 7496: 7494: 7491: 7489: 7486: 7484: 7481: 7479: 7476: 7474: 7471: 7469: 7466: 7464: 7461: 7459: 7456: 7454: 7451: 7449: 7446: 7444: 7441: 7440: 7438: 7436: 7429: 7423: 7420: 7418: 7415: 7413: 7410: 7408: 7405: 7404: 7402: 7398: 7390: 7387: 7385: 7382: 7380: 7377: 7376: 7375: 7372: 7370: 7367: 7363: 7360: 7358: 7355: 7353: 7350: 7348: 7345: 7343: 7340: 7339: 7338: 7335: 7334: 7332: 7328: 7324: 7317: 7312: 7310: 7305: 7303: 7298: 7297: 7294: 7282: 7274: 7272: 7264: 7263: 7260: 7254: 7251: 7249: 7246: 7244: 7241: 7239: 7236: 7234: 7231: 7229: 7226: 7225: 7223: 7219: 7209: 7206: 7204: 7201: 7199: 7196: 7194: 7191: 7190: 7188: 7184: 7178: 7175: 7173: 7172:Systems model 7170: 7168: 7165: 7163: 7160: 7158: 7155: 7153: 7150: 7148: 7145: 7143: 7140: 7138: 7135: 7133: 7130: 7129: 7127: 7123: 7117: 7114: 7112: 7109: 7107: 7104: 7102: 7099: 7097: 7094: 7092: 7089: 7087: 7084: 7082: 7079: 7077: 7074: 7072: 7069: 7067: 7064: 7062: 7059: 7057: 7054: 7052: 7049: 7047: 7044: 7043: 7041: 7039:Developmental 7037: 7034: 7030: 7024: 7021: 7019: 7016: 7014: 7011: 7009: 7006: 7004: 7001: 6999: 6996: 6995: 6993: 6989: 6983: 6980: 6976: 6973: 6972: 6971: 6968: 6966: 6963: 6961: 6958: 6956: 6953: 6951: 6948: 6946: 6943: 6941: 6938: 6936: 6933: 6931: 6928: 6926: 6923: 6921: 6918: 6916: 6913: 6911: 6908: 6906: 6903: 6901: 6900:Data modeling 6898: 6894: 6891: 6889: 6886: 6884: 6881: 6879: 6876: 6874: 6871: 6870: 6869: 6866: 6864: 6861: 6859: 6856: 6855: 6853: 6849: 6843: 6840: 6838: 6835: 6833: 6830: 6828: 6825: 6823: 6820: 6818: 6815: 6813: 6810: 6808: 6805: 6803: 6800: 6798: 6795: 6793: 6790: 6788: 6785: 6783: 6780: 6778: 6775: 6774: 6772: 6768: 6764: 6757: 6752: 6750: 6745: 6743: 6738: 6737: 6734: 6722: 6714: 6712: 6704: 6702: 6694: 6693: 6690: 6684: 6681: 6679: 6676: 6674: 6671: 6669: 6666: 6664: 6661: 6659: 6656: 6654: 6651: 6649: 6646: 6644: 6641: 6639: 6636: 6634: 6631: 6629: 6626: 6624: 6621: 6619: 6616: 6614: 6611: 6609: 6606: 6604: 6601: 6599: 6596: 6594: 6591: 6589: 6586: 6585: 6583: 6579: 6573: 6570: 6568: 6565: 6563: 6560: 6558: 6557:Mixed reality 6555: 6553: 6550: 6548: 6545: 6543: 6540: 6538: 6535: 6534: 6532: 6530: 6526: 6520: 6517: 6515: 6512: 6510: 6507: 6505: 6502: 6500: 6497: 6496: 6494: 6492: 6488: 6482: 6479: 6477: 6474: 6472: 6469: 6467: 6464: 6462: 6459: 6457: 6454: 6452: 6449: 6447: 6444: 6443: 6441: 6439: 6435: 6429: 6426: 6424: 6421: 6419: 6416: 6414: 6411: 6409: 6406: 6405: 6403: 6401: 6397: 6391: 6390:Accessibility 6388: 6386: 6385:Visualization 6383: 6381: 6378: 6376: 6373: 6371: 6368: 6367: 6365: 6363: 6359: 6353: 6350: 6348: 6345: 6343: 6340: 6338: 6335: 6333: 6330: 6328: 6325: 6323: 6320: 6318: 6315: 6313: 6310: 6309: 6307: 6305: 6301: 6295: 6292: 6290: 6287: 6285: 6282: 6280: 6277: 6275: 6272: 6270: 6267: 6265: 6262: 6260: 6257: 6255: 6252: 6250: 6247: 6245: 6242: 6240: 6237: 6235: 6232: 6230: 6227: 6226: 6224: 6222: 6218: 6212: 6209: 6207: 6204: 6202: 6199: 6197: 6194: 6192: 6189: 6187: 6184: 6182: 6179: 6177: 6174: 6173: 6171: 6169: 6164: 6158: 6155: 6153: 6150: 6148: 6145: 6143: 6140: 6138: 6135: 6134: 6132: 6130: 6126: 6120: 6117: 6115: 6112: 6110: 6107: 6105: 6102: 6100: 6097: 6095: 6092: 6090: 6087: 6086: 6084: 6082: 6078: 6072: 6069: 6067: 6064: 6062: 6059: 6057: 6054: 6052: 6049: 6047: 6044: 6042: 6039: 6037: 6034: 6032: 6029: 6027: 6024: 6023: 6021: 6019: 6015: 6009: 6006: 6004: 6001: 5999: 5996: 5994: 5991: 5989: 5986: 5984: 5981: 5979: 5976: 5974: 5971: 5969: 5966: 5964: 5961: 5960: 5958: 5956: 5952: 5948: 5942: 5939: 5937: 5934: 5932: 5929: 5927: 5924: 5922: 5919: 5918: 5916: 5912: 5906: 5903: 5901: 5898: 5896: 5893: 5891: 5888: 5886: 5883: 5881: 5878: 5877: 5875: 5873: 5869: 5863: 5860: 5858: 5855: 5853: 5852:Dependability 5850: 5848: 5845: 5843: 5840: 5839: 5837: 5833: 5827: 5823: 5820: 5818: 5815: 5813: 5810: 5808: 5805: 5803: 5800: 5798: 5795: 5793: 5790: 5788: 5785: 5783: 5780: 5778: 5775: 5774: 5772: 5770: 5766: 5761: 5755: 5751: 5744: 5739: 5737: 5732: 5730: 5725: 5724: 5721: 5715: 5712: 5710: 5706: 5701: 5697: 5696: 5691: 5686: 5685: 5668: 5664: 5660: 5653: 5648: 5647: 5634: 5627: 5619: 5613: 5609: 5604: 5603: 5602:Code Complete 5594: 5575: 5568: 5567: 5562: 5556: 5537: 5530: 5526: 5520: 5512: 5508: 5501: 5493: 5489: 5485: 5479: 5472: 5468: 5464: 5458: 5450: 5446: 5442: 5435: 5427: 5423: 5419: 5413: 5409: 5405: 5401: 5394: 5386: 5382: 5375: 5367: 5363: 5359: 5357:9781450316149 5353: 5349: 5345: 5341: 5337: 5330: 5322: 5316: 5312: 5311: 5307:IEEE (1998). 5303: 5295: 5293:9781447122388 5289: 5285: 5281: 5277: 5273: 5266: 5264: 5247: 5240: 5232: 5231: 5223: 5207: 5203: 5197: 5181: 5177: 5171: 5169: 5160: 5154: 5150: 5149: 5141: 5125: 5121: 5115: 5107: 5101: 5097: 5090: 5082: 5078: 5073: 5068: 5064: 5060: 5056: 5052: 5048: 5042: 5034: 5030: 5026: 5020: 5016: 5012: 5008: 5004: 4997: 4981: 4977: 4971: 4955: 4954: 4946: 4930: 4926: 4919: 4900: 4899: 4891: 4876: 4872: 4865: 4849: 4845: 4838: 4822: 4815: 4796: 4790: 4774: 4767: 4748: 4744: 4737: 4731: 4729: 4727: 4718: 4712: 4708: 4707: 4699: 4691: 4685: 4681: 4677: 4670: 4662: 4656: 4652: 4651: 4643: 4641: 4639: 4623: 4617: 4613: 4609: 4608: 4600: 4592: 4590:9780471469124 4586: 4582: 4575: 4573: 4556: 4552: 4546: 4538: 4532: 4528: 4527: 4519: 4517: 4508: 4502: 4498: 4497: 4489: 4487: 4485: 4468: 4464: 4463:TEST Magazine 4460: 4453: 4434: 4433: 4425: 4417: 4411: 4407: 4406: 4398: 4383: 4377: 4373: 4372: 4364: 4362: 4353: 4347: 4343: 4342: 4334: 4318: 4314: 4307: 4304:(June 1999). 4303: 4297: 4282: 4275: 4274: 4266: 4258: 4252: 4248: 4247: 4239: 4148: 4142: 4134: 4128: 4124: 4123: 4115: 4113: 4096: 4089: 4087: 4078: 4072: 4068: 4061: 4053: 4047: 4043: 4042: 4034: 4032: 4030: 4021: 4015: 4011: 4010: 4002: 4000: 3998: 3996: 3987: 3981: 3977: 3976: 3968: 3966: 3964: 3962: 3953: 3947: 3943: 3939: 3935: 3934: 3926: 3918: 3912: 3908: 3904: 3900: 3899: 3891: 3883: 3879: 3875: 3871: 3867: 3860: 3853: 3852: 3848: 3845: 3838: 3831: 3827: 3824: 3821:Cem Kaner, " 3818: 3810: 3806: 3802: 3796: 3792: 3788: 3784: 3777: 3769: 3763: 3759: 3758: 3750: 3748: 3746: 3744: 3735: 3729: 3725: 3724: 3716: 3714: 3705: 3699: 3695: 3688: 3680: 3674: 3670: 3669: 3661: 3653: 3647: 3643: 3642: 3634: 3615: 3611: 3605: 3601: 3594: 3587: 3572: 3566: 3562: 3558: 3551: 3543: 3537: 3533: 3532: 3524: 3516: 3510: 3506: 3499: 3491: 3485: 3481: 3476: 3475: 3466: 3458: 3454: 3450: 3443: 3424: 3420: 3413: 3407: 3388: 3384: 3380: 3374: 3367: 3361: 3357: 3353: 3349: 3343: 3341: 3332: 3326: 3322: 3321: 3316: 3310: 3308: 3306: 3289: 3282: 3276: 3268: 3262: 3258: 3251: 3243: 3237: 3233: 3226: 3218: 3212: 3208: 3201: 3193: 3187: 3183: 3182: 3174: 3172: 3152: 3151: 3146: 3139: 3131: 3125: 3121: 3117: 3111: 3109: 3107: 3105: 3088: 3081: 3079: 3059: 3058: 3053: 3047: 3043: 3031: 3028: 3025: 3022: 3019: 3016: 3014: 3011: 3008: 3005: 3002: 2999: 2993: 2990: 2987: 2984: 2981: 2978: 2972: 2969: 2966: 2963: 2960: 2957: 2955: 2952: 2949: 2946: 2943: 2940: 2937: 2934: 2933: 2924: 2920: 2915: 2905: 2902: 2899: 2896: 2893: 2891:Construction 2890: 2889: 2885: 2882: 2879: 2876: 2873: 2871:Architecture 2870: 2869: 2865: 2862: 2859: 2856: 2853: 2851:Requirements 2850: 2846: 2843:Post-release 2842: 2839: 2837:Construction 2836: 2834:Architecture 2833: 2831:Requirements 2830: 2829: 2821: 2818: 2816: 2806: 2803: 2799: 2796: 2792: 2789: 2785: 2781: 2777: 2774: 2771: 2766: 2765:agile testing 2762: 2758: 2755: 2754: 2753: 2751: 2741: 2739: 2732: 2722: 2714: 2712: 2706: 2696: 2691: 2677: 2673: 2669: 2662: 2651: 2648: 2638: 2635: 2629: 2616: 2612: 2608: 2604: 2600: 2596: 2592: 2585: 2574: 2572: 2571:test strategy 2567: 2561: 2551: 2549: 2539: 2537: 2532: 2530: 2526: 2522: 2518: 2514: 2510: 2506: 2502: 2492: 2490: 2485: 2482: 2478: 2468: 2464: 2460: 2457: 2453: 2449: 2443: 2440: 2439: 2438: 2432: 2429: 2428: 2427: 2425: 2423: 2422:IEEE Standard 2414: 2411: 2410: 2409: 2407: 2401: 2397: 2386: 2372: 2369: 2366: 2363: 2359: 2356: 2352: 2348: 2345: 2341: 2337: 2334: 2330: 2326: 2325:Test strategy 2322: 2319: 2315: 2312: 2311: 2310: 2302: 2300: 2295: 2293: 2288: 2284: 2279: 2277: 2268: 2265: 2263: 2259: 2253: 2249: 2239: 2231: 2229: 2225: 2221: 2217: 2216:test designer 2213: 2209: 2205: 2200: 2198: 2193: 2191: 2176: 2174: 2169: 2160: 2155: 2145: 2143: 2138: 2134: 2128: 2118: 2115: 2105: 2100: 2090: 2088: 2082: 2072: 2067: 2057: 2055: 2051: 2046: 2041: 2028: 2024: 2020: 2016: 2012: 2009: 2006: 2002: 1999: 1996: 1992: 1989: 1985: 1982: 1978: 1974: 1971: 1967: 1964: 1960: 1957: 1954: 1951: 1947: 1946: 1945: 1942: 1939: 1937: 1933: 1923: 1919: 1917: 1913: 1909: 1897: 1894:(WAI) of the 1893: 1890: 1888: 1885: 1883: 1880: 1879: 1878: 1877: 1870: 1867: 1864: 1861: 1860: 1859: 1857: 1856:Accessibility 1848: 1846: 1841: 1832: 1830: 1826: 1822: 1820: 1815: 1813: 1809: 1808: 1803: 1802: 1797: 1793: 1789: 1785: 1784: 1779: 1774: 1763: 1759: 1754: 1752: 1748: 1744: 1740: 1733: 1723: 1721: 1717: 1713: 1707: 1697: 1695: 1691: 1687: 1683: 1679: 1675: 1672: 1663: 1661: 1657: 1653: 1649: 1648:beta versions 1645: 1639: 1629: 1623:Alpha testing 1620: 1616: 1612: 1610: 1606: 1602: 1597: 1593: 1589: 1584: 1578: 1575: 1572: 1569: 1568: 1567: 1564: 1561: 1557: 1547: 1544: 1538: 1535: 1531: 1525: 1515: 1513: 1509: 1508:Smoke testing 1505: 1503: 1498: 1488: 1486: 1482: 1478: 1474: 1470: 1466: 1462: 1458: 1454: 1450: 1446: 1442: 1438: 1437:compatibility 1432: 1417: 1414: 1411: 1408: 1407: 1406: 1404: 1395: 1384: 1381: 1380:, and so on. 1379: 1374: 1370: 1364: 1362: 1358: 1351: 1340: 1335: 1332: 1328: 1324: 1320: 1316: 1307: 1305: 1300: 1299: 1295: 1292: 1290: 1286: 1281: 1276: 1274: 1270: 1266: 1262: 1258: 1254: 1250: 1246: 1242: 1232: 1227: 1217: 1215: 1205: 1202: 1199: 1196: 1193: 1190: 1189: 1188: 1187: 1186: 1184: 1180: 1171: 1168: 1165: 1162: 1159: 1156: 1153: 1152:Code coverage 1150: 1147: 1143: 1140: 1139: 1138: 1135: 1132: 1128: 1124: 1119: 1117: 1107: 1102: 1092: 1083: 1071: 1067: 1063: 1057: 1046: 1044: 1040: 1034: 1032: 1028: 1023: 1022:environment. 1021: 1017: 1013: 1009: 1004: 1002: 998: 994: 990: 986: 973: 969: 963: 949: 945: 939: 925: 921: 915: 904: 902: 889: 885: 880: 876: 869: 858: 854: 849: 842: 840: 839:combinatorics 835: 833: 829: 828:compatibility 825: 821: 817: 813: 809: 805: 801: 794:Code coverage 791: 789: 785: 781: 777: 773: 769: 759: 756: 754: 751:, changes in 750: 745: 743: 738: 736: 732: 728: 718: 710: 707: 703: 694: 692: 688: 686: 676: 674: 670: 666: 661: 658: 655: 653: 652:documentation 649: 644: 642: 638: 634: 629: 627: 623: 619: 614: 612: 608: 604: 599: 597: 593: 586: 581: 570: 565: 563: 558: 556: 551: 550: 548: 547: 540: 537: 536: 530: 529: 522: 519: 517: 514: 512: 509: 508: 502: 501: 494: 491: 489: 486: 484: 481: 479: 476: 474: 471: 469: 466: 464: 461: 459: 456: 454: 451: 450: 444: 443: 436: 433: 431: 428: 426: 423: 421: 418: 416: 413: 411: 408: 406: 403: 401: 398: 396: 393: 392: 389: 384: 383: 376: 373: 371: 368: 366: 363: 361: 358: 356: 353: 351: 348: 346: 343: 341: 338: 336: 333: 331: 328: 327: 321: 320: 313: 310: 308: 305: 303: 300: 298: 297:Documentation 295: 293: 290: 288: 285: 284: 278: 277: 270: 267: 265: 262: 260: 257: 255: 252: 250: 247: 245: 242: 240: 237: 235: 232: 230: 227: 225: 222: 220: 217: 215: 212: 210: 207: 205: 202: 200: 197: 195: 192: 190: 187: 185: 182: 180: 177: 175: 172: 170: 167: 166: 162: 161:Methodologies 157: 156: 149: 146: 144: 141: 139: 136: 134: 131: 129: 126: 124: 121: 119: 116: 115: 109: 108: 101: 98: 96: 93: 91: 88: 86: 83: 81: 78: 76: 73: 71: 68: 66: 63: 61: 58: 56: 55:Data modeling 53: 52: 46: 45: 42: 39: 38: 34: 33: 30: 19: 7584:Soak testing 7579:Pair testing 7422:Unit testing 7352:Fuzz testing 7322: 7167:Object model 7162:Metamodeling 7091:Spiral model 6991:Orientations 6836: 6653:Cyberwarfare 6312:Cryptography 5693: 5672:November 21, 5670:. Retrieved 5658: 5632: 5626: 5601: 5593: 5581:. Retrieved 5574:the original 5565: 5555: 5543:. Retrieved 5536:the original 5519: 5510: 5500: 5492:the original 5487: 5478: 5462: 5457: 5449:the original 5444: 5434: 5399: 5393: 5385:the original 5374: 5339: 5329: 5309: 5302: 5275: 5250:. Retrieved 5239: 5229: 5222: 5210:. Retrieved 5205: 5196: 5184:. Retrieved 5179: 5147: 5140: 5128:. Retrieved 5123: 5114: 5095: 5089: 5062: 5058: 5051:Hetzel, Bill 5041: 5006: 5003:"QuickCheck" 4996: 4984:. Retrieved 4980:the original 4970: 4958:. Retrieved 4952: 4945: 4933:. Retrieved 4928: 4918: 4906:. Retrieved 4897: 4890: 4878:. Retrieved 4874: 4864: 4852:. Retrieved 4847: 4837: 4825:. Retrieved 4814: 4802:. Retrieved 4789: 4777:. Retrieved 4766: 4754:. Retrieved 4742: 4705: 4698: 4679: 4669: 4649: 4627:November 29, 4625:. Retrieved 4606: 4599: 4580: 4561:December 10, 4559:. Retrieved 4555:the original 4545: 4525: 4495: 4471:. Retrieved 4467:the original 4462: 4452: 4440:. Retrieved 4431: 4424: 4404: 4397: 4385:. Retrieved 4370: 4340: 4333: 4321:. Retrieved 4319:(6): 113–114 4316: 4312: 4296: 4284:. Retrieved 4272: 4265: 4245: 4238: 4141: 4121: 4101:November 21, 4099:. Retrieved 4066: 4060: 4040: 4008: 3974: 3932: 3925: 3897: 3890: 3873: 3869: 3859: 3842: 3837: 3817: 3782: 3776: 3756: 3722: 3693: 3687: 3667: 3660: 3640: 3633: 3621:. Retrieved 3614:the original 3599: 3586: 3574:. Retrieved 3560: 3550: 3534:. Springer. 3530: 3523: 3504: 3498: 3473: 3465: 3448: 3442: 3432:December 15, 3430:. Retrieved 3423:the original 3406: 3396:December 15, 3394:. Retrieved 3387:the original 3373: 3347: 3319: 3294:December 19, 3292:. Retrieved 3275: 3256: 3250: 3231: 3225: 3206: 3200: 3180: 3158:. Retrieved 3149: 3138: 3119: 3093:November 21, 3091:. Retrieved 3067:November 22, 3065:. Retrieved 3056: 3046: 3001:Pair testing 2921: 2917: 2913: 2840:System test 2811: 2747: 2734: 2720: 2711:test harness 2708: 2705:Test harness 2699:Test harness 2693: 2690:Test fixture 2644: 2631: 2603:requirements 2563: 2545: 2533: 2509:ISO/IEC 9126 2498: 2486: 2474: 2465: 2461: 2458: 2454: 2450: 2447: 2436: 2420: 2418: 2403: 2308: 2299:unit testing 2296: 2287:unit testing 2280: 2274: 2266: 2255: 2237: 2227: 2223: 2219: 2215: 2212:test analyst 2211: 2207: 2204:test manager 2203: 2201: 2196: 2194: 2187: 2170: 2166: 2157: 2139: 2135: 2131: 2111: 2102: 2084: 2069: 2054:traceability 2047: 2043: 1943: 1940: 1930:Testing for 1929: 1920: 1906: 1875: 1874: 1854: 1845:UI designers 1838: 1823: 1816: 1811: 1805: 1799: 1795: 1783:Load testing 1781: 1780: 1776: 1735: 1709: 1676: 1669: 1641: 1632:Beta testing 1626: 1617: 1613: 1608: 1585: 1582: 1565: 1562: 1559: 1539: 1527: 1506: 1500: 1434: 1399: 1382: 1365: 1353: 1325: 1321: 1317: 1313: 1301: 1297: 1296: 1293: 1277: 1261:fuzz testing 1237: 1214:control flow 1211: 1203: 1197: 1191: 1175: 1136: 1120: 1112: 1089: 1080: 1043:log analysis 1035: 1027:verification 1024: 1005: 989:walkthroughs 982: 920:Unit testing 914:Unit testing 907:Unit testing 898: 856: 848: 836: 811: 807: 799: 797: 765: 757: 746: 739: 724: 721:Finding bugs 716: 700: 689: 682: 671:and finally 662: 659: 656: 645: 630: 615: 613:or sponsor. 600: 591: 590: 415:UML Modeling 410:GUI designer 84: 75:Construction 65:Requirements 29: 18:Beta-testing 7599:Web testing 7443:A/B testing 7379:API testing 6858:Abstraction 6663:Video games 6643:Digital art 6400:Concurrency 6269:Data mining 6181:Probability 5921:Interpreter 5688:‹ The 5583:January 18, 5545:October 13, 5484:"stop29119" 5130:January 13, 5124:etestinghub 4986:January 13, 4960:January 17, 4935:January 16, 4908:January 16, 4880:January 16, 4875:Stickyminds 4854:January 12, 4827:January 11, 4473:January 13, 4442:January 13, 4302:Bach, James 3841:Cem Kaner, 3557:"Chapter 5" 3259:. Manning. 3160:December 8, 3030:Web testing 3024:Trace table 2744:Controversy 2738:controversy 2647:test script 2641:Test script 2521:portability 2513:reliability 2501:correctness 2355:test effort 2163:VCR testing 2066:A/B testing 2060:A/B testing 1792:scalability 1690:constraints 1686:performance 1682:scalability 1477:abstracting 1469:Web browser 1439:with other 1142:API testing 1127:integration 1066:test design 1049:Exploratory 993:inspections 924:source code 832:reliability 824:performance 820:scalability 784:performance 776:scalability 772:testability 691:Outsourcing 618:correctness 133:Prototyping 128:Incremental 100:Maintenance 80:Engineering 7614:Categories 7177:View model 7142:Data model 6721:Glossaries 6593:E-commerce 6186:Statistics 6129:Algorithms 5926:Middleware 5782:Peripheral 5635:. leanpub. 5561:Kaner, Cem 5525:Kaner, Cem 5252:August 13, 4804:January 9, 4779:January 9, 4387:January 5, 4323:August 19, 4286:January 2, 3576:January 2, 3290:. May 2002 3116:Kaner, Cem 3052:Kaner, Cem 3038:References 2794:withdrawn. 2676:test cases 2672:test suite 2661:Test suite 2654:Test suite 2615:test cases 2517:efficiency 2467:document. 2350:knowledge. 2344:test cases 2142:QuickCheck 1963:hard coded 1739:robustness 1636:See also: 1285:functional 1280:test cases 1031:validation 997:test cases 731:programmer 665:unit tests 587:, May 2016 505:Glossaries 95:Deployment 7448:Benchmark 7186:Languages 6542:Rendering 6537:Animation 6168:computing 6119:Semantics 5817:Processor 5511:InfoWorld 5445:CrossTalk 5212:March 17, 5186:March 17, 4756:April 11, 4149:function 2788:ISO 29119 2752:include: 2740:section. 2634:test case 2628:Test case 2622:Test case 2611:test plan 2566:test plan 2560:Test plan 2554:Test plan 2548:artifacts 2542:Artifacts 2529:usability 2374:projects. 2329:test plan 2234:Processes 2208:test lead 1865:Font Size 1831:is used. 1684:or other 1271:testing, 1259:testing, 1070:Cem Kaner 1012:functions 816:usability 742:dead code 737:and fix. 706:debugging 679:Economics 641:contracts 622:scenarios 324:Practices 148:Waterfall 123:Cleanroom 90:Debugging 60:Processes 7557:See also 7281:Category 7147:ER model 7013:Ontology 6925:Software 6851:Concepts 6701:Category 6529:Graphics 6304:Security 5973:Compiler 5872:Networks 5769:Hardware 5690:template 5659:Computer 5563:(2003). 5527:(2001). 5426:30322339 5081:14731341 4747:Archived 4313:Computer 3854:, p. 36. 3847:Archived 3826:Archived 3809:42596126 3623:July 13, 3317:(1979). 2929:See also 2886:25–100× 2866:10–100× 2717:Test run 2505:security 2495:Measures 2179:Teamwork 2027:currency 1970:run time 1694:security 1656:feedback 1453:terminal 1449:versions 1369:database 1269:use case 1020:debugger 879:software 788:security 770:such as 596:software 585:Katowice 533:Outlines 463:ISO 9001 405:Profiler 400:Debugger 395:Compiler 370:Stand-up 7435:tactics 7271:Commons 7096:V-model 6711:Outline 5692:below ( 5366:9072512 5033:5668071 2906:10–25× 2379:Quality 2333:testbed 2262:project 1950:strings 1916:hackers 1747:fuzzing 1485:library 1461:desktop 1172:methods 1166:methods 1118:(ICT). 985:Reviews 697:History 603:quality 204:Lean SD 143:V model 85:Testing 7032:Models 6782:DevOps 6770:Fields 5709:Curlie 5695:Curlie 5614: 5469: 5424: 5414: 5364: 5354: 5317: 5290: 5155: 5102: 5079: 5031: 5021: 4713: 4686: 4657: 4618: 4587: 4533: 4503: 4412: 4378: 4348: 4253: 4170:return 4129: 4073: 4048: 4016: 3982: 3948: 3913: 3832:", p.2 3807: 3797: 3764: 3730: 3700: 3675: 3648: 3606: 3567: 3538: 3511: 3486: 3362: 3327: 3263: 3238: 3213: 3188: 3126: 2860:5–10× 2763:? The 2613:, and 2361:later. 2226:, and 2220:tester 1481:module 1131:system 1129:, and 895:Levels 830:, and 786:, and 633:oracle 478:SWEBOK 199:Kanban 174:DevOps 138:Spiral 70:Design 7208:SysML 7132:SPICE 7125:Other 7086:Scrum 7046:Agile 6998:Agile 6982:CI/CD 6114:Logic 5955:tools 5655:(PDF) 5577:(PDF) 5570:(PDF) 5539:(PDF) 5532:(PDF) 5422:S2CID 5362:S2CID 5077:S2CID 5029:S2CID 4902:(PDF) 4798:(PDF) 4750:(PDF) 4739:(PDF) 4436:(PDF) 4309:(PDF) 4277:(PDF) 4215:>= 3805:S2CID 3617:(PDF) 3596:(PDF) 3482:–43. 3426:(PDF) 3415:(PDF) 3390:(pdf) 3284:(PDF) 3154:(PDF) 3061:(PDF) 2184:Roles 1898:(W3C) 1788:users 1692:, or 1016:stubs 991:, or 735:debug 713:Goals 473:PMBOK 388:Tools 249:SEMAT 244:Scrum 118:Agile 7433:and 7193:IDEF 7137:CMMI 7023:SDLC 5953:and 5826:Form 5822:Size 5674:2017 5612:ISBN 5585:2018 5547:2006 5467:ISBN 5412:ISBN 5352:ISBN 5315:ISBN 5288:ISBN 5254:2008 5214:2018 5188:2018 5153:ISBN 5132:2012 5100:ISBN 5019:ISBN 4988:2012 4962:2018 4937:2018 4910:2018 4882:2018 4856:2018 4829:2018 4806:2018 4781:2018 4758:2022 4711:ISBN 4684:ISBN 4655:ISBN 4629:2017 4616:ISBN 4585:ISBN 4563:2012 4531:ISBN 4501:ISBN 4475:2012 4444:2012 4410:ISBN 4389:2018 4376:ISBN 4346:ISBN 4325:2008 4288:2018 4251:ISBN 4127:ISBN 4103:2017 4071:ISBN 4046:ISBN 4014:ISBN 3980:ISBN 3946:ISBN 3911:ISBN 3795:ISBN 3762:ISBN 3728:ISBN 3698:ISBN 3673:ISBN 3646:ISBN 3625:2018 3604:ISBN 3578:2018 3565:ISBN 3536:ISBN 3509:ISBN 3484:ISBN 3434:2017 3398:2017 3360:ISBN 3325:ISBN 3296:2017 3261:ISBN 3236:ISBN 3211:ISBN 3186:ISBN 3162:2017 3124:ISBN 3095:2017 3069:2014 2903:10× 2883:15× 2880:10× 2863:10× 2670:, a 2593:, a 2507:and 2398:and 2250:and 2025:and 2017:and 1760:and 1718:and 1652:bugs 1594:and 1543:risk 1329:and 1146:APIs 1123:unit 1041:and 886:and 814:) – 753:data 727:code 685:NIST 648:code 626:bugs 611:user 607:risk 488:IREB 483:ITIL 453:CMMI 330:ATDD 239:SAFe 209:LeSS 184:DSDM 7203:USL 7198:UML 7076:RAD 7051:EUP 5707:at 5663:doi 5404:doi 5344:doi 5280:doi 5067:doi 5011:doi 4161:int 4152:int 3938:doi 3903:doi 3878:doi 3787:doi 3453:doi 3352:doi 2900:1× 2877:1× 2857:3× 2854:1× 2666:In 2589:In 2256:In 2173:vcr 1914:by 1662:). 1483:or 1457:GUI 1455:or 1373:SQL 1287:or 800:all 493:OMG 420:IDE 375:TDD 365:SBE 355:DDD 340:CCO 335:BDD 259:TSP 254:TDD 234:RUP 229:RAD 224:PSP 219:MSF 214:MDD 194:IID 189:FDD 179:DAD 169:ASD 7616:: 7106:XP 7081:UP 5824:/ 5657:. 5610:. 5608:29 5509:. 5486:. 5443:. 5420:. 5410:. 5360:. 5350:. 5338:. 5286:. 5262:^ 5204:. 5178:. 5167:^ 5122:. 5075:. 5063:31 5061:. 5057:. 5049:; 5027:. 5017:. 5005:. 4927:. 4873:. 4846:. 4745:. 4741:. 4725:^ 4637:^ 4610:. 4571:^ 4515:^ 4483:^ 4461:. 4360:^ 4317:32 4315:. 4311:. 4197:;} 4182:-6 4167:){ 4111:^ 4085:^ 4028:^ 3994:^ 3960:^ 3944:. 3909:. 3874:84 3872:. 3868:. 3803:. 3793:. 3742:^ 3712:^ 3598:. 3559:. 3480:31 3417:. 3381:. 3358:, 3339:^ 3304:^ 3286:. 3170:^ 3103:^ 3077:^ 2897:– 2894:– 2874:– 2772:). 2713:. 2645:A 2632:A 2564:A 2531:. 2523:, 2519:, 2515:, 2426:: 2408:: 2342:, 2331:, 2327:, 2301:. 2230:. 2222:, 2218:, 2214:, 2210:, 2206:, 2175:. 2144:. 1918:. 1847:. 1798:. 1514:. 1487:. 1443:, 1267:, 1263:, 1255:, 1251:, 1247:, 1243:, 1125:, 1045:. 1033:. 1003:. 987:, 826:, 822:, 818:, 812:do 808:be 790:. 782:, 778:, 774:, 654:. 639:, 628:. 360:PP 350:CD 345:CI 269:XP 264:UP 7315:e 7308:t 7301:v 6755:e 6748:t 6741:v 5762:. 5742:e 5735:t 5728:v 5676:. 5665:: 5620:. 5587:. 5549:. 5513:. 5473:. 5428:. 5406:: 5368:. 5346:: 5323:. 5296:. 5282:: 5256:. 5233:. 5216:. 5190:. 5161:. 5134:. 5108:. 5083:. 5069:: 5035:. 5013:: 4990:. 4964:. 4939:. 4912:. 4884:. 4858:. 4831:. 4808:. 4783:. 4760:. 4719:. 4692:. 4663:. 4631:. 4593:. 4565:. 4539:. 4509:. 4477:. 4446:. 4418:. 4391:. 4354:. 4327:. 4290:. 4259:. 4230:3 4227:= 4224:x 4218:0 4212:) 4209:x 4206:( 4203:f 4194:8 4191:+ 4188:x 4185:* 4179:x 4176:* 4173:x 4164:x 4158:( 4155:f 4147:C 4135:. 4105:. 4079:. 4054:. 4022:. 3988:. 3954:. 3940:: 3919:. 3905:: 3884:. 3880:: 3811:. 3789:: 3770:. 3736:. 3706:. 3681:. 3654:. 3627:. 3580:. 3544:. 3517:. 3492:. 3459:. 3455:: 3436:. 3400:. 3354:: 3333:. 3298:. 3269:. 3244:. 3219:. 3194:. 3164:. 3132:. 3097:. 3071:. 2663:. 2617:. 2586:. 2129:. 2029:. 2007:. 1396:. 1058:. 974:. 964:. 940:. 916:. 890:. 870:. 568:e 561:t 554:v 20:)

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

Index