2640:
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:
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
7270:
6690:
1231:
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."
6700:
6710:
2455:
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).
7260:
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
2459:
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.
2922:
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.
2639:
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
2486:
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
2785:
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
2465:
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
2292:
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
2921:
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.
2815:
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
2458:
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
2170:
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
2073:
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
2681:
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
2161:
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
2925:
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
2571:
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
2803:
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
2048:
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
2697:
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
2454:
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
2135:
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.
2469:
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
2047:
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:
2466:
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
2373:: 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.
2136:
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.
2139:
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.
2796:
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,
2119:
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.
2652:
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
2572:(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.
2363:
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
2106:
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.
2738:
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
2171:
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.
2770:
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
2482:(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
2376:
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
2352:
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
5277:; 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
2724:
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
2422:
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.
2433:
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.
1886:
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
566:
3532:
3381:
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.
2263:, 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
2281:
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.
2003:
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)
2092:, 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.
4749:
3421:
3385:
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.
2447:
Validation is confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.
520:
2810:
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:
2436:
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.
2270:
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.
6746:
3290:
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
2312:
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
487:
1958:
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.
7306:
5726:
3159:. ESEC/FSE'07: European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering 2007. Dubrovnik, Croatia
559:
3534:
Systems, Software and Services Process Improvement: 22nd European Conference, EuroSPI 2015, Ankara, Turkey, September 30 -- October 2, 2015. Proceedings
2143:
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
7617:
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.
2490:
Software testing is an activity to investigate software under test in order to provide quality-related information to stakeholders. By contrast, QA (
5383:
4553:
1881:
1319:
in video format. Output videos are supplemented by real-time tester input via picture-in-a-picture webcam and audio commentary from microphones.
329:
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
6443:
6415:
5509:
4873:
2408:
2398:
579:
477:
7129:
7058:
6468:
5618:
5532:"NSF grant proposal to 'lay a foundation for significant improvements in the quality of academic and commercial courses in software testing'"
5473:
5443:
5418:
5321:
5159:
5106:
5025:
4717:
4690:
4661:
4622:
4537:
4507:
4416:
4382:
4352:
4257:
4133:
4077:
4052:
4020:
3986:
3952:
3917:
3801:
3768:
3734:
3704:
3679:
3652:
3610:
3571:
3542:
3515:
3490:
3366:
3331:
3192:
3130:
2250:
1931:
552:
452:
193:
3235:
Crafting Test-Driven Software with Python: Write test suites that scale with your applications' needs and complexity using Python and PyTest
2600:(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
2487:
Although there are close links with SQA, testing departments often exist independently, and there may be no SQA function in some companies.
6952:
6855:
6319:
472:
3389:
6473:
5745:
2601:
2444:
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
510:
6739:
5978:
3267:
3242:
3217:
1972:
1600:
1145:
419:
183:
2323:. During the design phase, testers work to determine what aspects of a design are testable and with what parameters those tests work.
6932:
6799:
6784:
6625:
6453:
5983:
5358:
5294:
4846:
4591:
2025:
286:
5531:
4775:
4738:
4461:
3595:
7556:
6713:
5807:
2973:
1338:
409:
404:
160:
5699:
4978:
2786:
in tools and expertise can be amortized over multiple projects with the right level of knowledge sharing within an organization.
6101:
3784:
Lee, D.; Netravali, A.N.; Sabnani, K.K.; Sugla, B.; John, A. (1997). "Passive testing and applications to network management".
3531:
O’Connor, Rory V.; Akkaya, Mariye Umay; Kemaneci, Kerem; Yilmaz, Murat; Poth, Alexander; Messnarz, Richard (October 15, 2015).
2550:
2451:
The contradiction is caused by the use of the concepts of requirements and specified requirements but with different meanings.
2320:
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?
538:
6354:
3898:
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.
7299:
7263:
7088:
7015:
7005:
6850:
6779:
6392:
6011:
5719:
2752:
2503:
1476:
617:
429:
142:
122:
7139:
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
2553:. The actual artifacts produced are a factor of the software development model used, stakeholder and organisational needs.
1996:
Fonts and font sizes that are appropriate in the source language may be inappropriate in the target language; for example,
1941:
Globalization testing verifies that the software is adapted for a new culture, such as different currencies or time zones.
1658:
field to a maximal number of future users and to deliver value earlier, for an extended or even indefinite period of time (
7273:
7068:
7010:
6732:
6534:
6511:
6241:
6231:
3009:
2982:
1738:
339:
228:
218:
168:
3414:
1619:
independent testers. Regulation acceptance testing sometimes involves the regulatory agencies auditing the test results.
7581:
7520:
7078:
6937:
6804:
6615:
6203:
6111:
6016:
5792:
5777:
5567:
3849:
3828:
2300:
Even in organizations that separate teams by programming and testing functions, many often have the programmers perform
2195:
team or they may be integrated into one team. Software testing can also be performed by non-dedicated software testers.
1891:
1772:
1528:
Regression testing focuses on finding defects after a major code change has occurred. Specifically, it seeks to uncover
515:
243:
208:
59:
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.
7000:
6995:
6809:
6703:
6438:
5936:
4927:
1719:
1637:
1011:
803:
767:
334:
306:
5486:
1944:
Actual translation to human languages must be tested, too. Possible localization and globalization failures include:
1363:
between two modules of code written by two different developers, where only the interfaces are exposed for the test.
3901:
In Testing Software and Systems: 23rd IFIP WG 6.1 International Conference, ICTSS 2011, Paris, France, November 7-10
7195:
7043:
7038:
6990:
6967:
6947:
6675:
6324:
4956:
ISO/IEC/IEEE 29119-1:2013 – Software and Systems Engineering – Software Testing – Part 1 – Concepts and Definitions
4614:
2479:
2424:
2278:
1915:
457:
301:
188:
178:
117:
3151:
2608:(these often consist of marketing requirements) and detailed requirements of the product to the matching parts of
2576:" 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:
7612:
7525:
7292:
7200:
7190:
6693:
6620:
6595:
6458:
6106:
5712:
5204:
2763:
2541:, or measures, which are used to assist in determining the state of the software or the adequacy of the testing.
2056:
1952:
1895:
1587:
831:
223:
203:
2712:
The software, tools, samples of data input and output, and configurations are all referred to collectively as a
2367:
Defect Retesting: Once a defect has been dealt with by the development team, it is retested by the testing team.
7566:
7515:
7485:
7427:
7103:
6902:
6885:
6794:
6544:
6377:
5963:
5832:
5690:
4149:
3015:
2994:
2961:
2402:
1961:
Literal word-for-word translations may sound inappropriate, artificial or too technical in the target language.
1689:
1507:
1496:
1240:
852:
364:
233:
213:
1753:
page; there are also numerous open-source and free software tools available that perform destructive testing.
660:
Information learned from software testing may be used to improve the process by which software is developed.
7053:
6897:
6605:
6539:
6430:
6246:
5906:
4797:
4283:
2515:
2507:
2285:
1715:
1643:
1511:
1244:
1007:
492:
374:
253:
127:
1794:. The related load testing activity of when performed as a non-functional activity is often referred to as
1563:
Acceptance testing may be performed as part of the hand-off process between any two phases of development.
7108:
6865:
6860:
6670:
6501:
6382:
6149:
6139:
6134:
2519:
2294:
2088:
Concurrent or concurrency testing assesses the behaviour and performance of software and systems that use
1844:
1677:
1533:
1472:
1436:
1288:
1252:
827:
434:
344:
296:
238:
2051:
Depending on the organization's expectations for software development, Development Testing might include
1680:
refers to aspects of the software that may not be related to a specific function or user action, such as
7445:
7440:
6927:
6880:
6640:
6610:
6600:
6496:
6410:
6286:
6226:
6193:
6183:
6066:
6031:
6021:
5958:
5827:
5802:
5797:
5762:
2944:
2817:
2494:) is the implementation of policies and procedures intended to prevent defects from reaching customers.
2316:
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
1430:
1026:
291:
258:
74:
64:
5387:
4823:
3454:. IEEE Fifth International Conference on Software Testing and Validation (ICST). Montreal, QC, Canada.
2762:
Should testers learn to work under conditions of uncertainty and constant change or should they aim at
5343:
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
7490:
7480:
7225:
7063:
6922:
6912:
6824:
6769:
6755:
6400:
6372:
6344:
6339:
6168:
6144:
6096:
6079:
6074:
6056:
6046:
6041:
6003:
5953:
5948:
5865:
5811:
5231:
3182:
3020:
2670:
2593:
2483:
2192:
2089:
2052:
2021:
1911:
1595:
1591:
1440:
1402:
1393:
1038:
988:
823:
783:
771:
621:
354:
198:
132:
99:
79:
40:
4557:
2820:
practices and cloud-based services, the cost of re-deployment and maintenance may lessen over time.
2356:
Test reporting: Once testing is completed, testers generate metrics and make final reports on their
7475:
7470:
7460:
7404:
7349:
7339:
7245:
7230:
7098:
6962:
6870:
6814:
6665:
6590:
6506:
6491:
6256:
6036:
5993:
5988:
5885:
5875:
5847:
4308:
3904:. Lecture Notes in Computer Science. Vol. 7019. Springer Berlin Heidelberg. pp. 162–178.
2967:
2597:
2586:
2156:
2101:
2042:
2007:
1955:
out of context, and the translator may choose the wrong translation for an ambiguous source string.
1824:
1818:
1731:
1529:
1484:
1480:
1448:
1360:
1330:
1272:
1264:
1126:
1061:
1055:
1030:
992:
943:
937:
883:
834:– can be subjective; something that constitutes sufficient value to one person may not to another.
668:
349:
268:
94:
5248:
7530:
7505:
7465:
7455:
7399:
7235:
6875:
6630:
6529:
6405:
6362:
6271:
6213:
6198:
6188:
5973:
5772:
5451:
5424:
5364:
5274:
5079:
5031:
3807:
2370:
2264:
2241:
Organizations that develop software, perform testing differently, but there are common patterns.
2083:
2055:, data flow analysis, metrics analysis, peer code reviews, unit testing, code coverage analysis,
2017:
1990:
1935:
1757:
1705:
1670:
1604:
1555:
1523:
1377:
1284:
887:
672:
640:
602:
467:
2917:
The data from which this table is extrapolated is scant. Laurent Bossavit says in his analysis:
5654:
3933:
Petrenko, A.; Yevtushenko, N. (2014). "Adaptive testing of nondeterministic systems with FSM".
3283:
2418:
Validation: Have we built the right software? (i.e., do the deliverables satisfy the customer).
1975:
and the resulting string may be ungrammatical, functionally incorrect, misleading or confusing.
1560:
Acceptance testing is system-level testing to ensure the software meets customer expectations.
1294:
Black box testing can be used to any level of testing although usually not at the unit level.
1206:, which reports on whether both the True and the False branch of a given test has been executed
7540:
7366:
7334:
7329:
7149:
6907:
6650:
6580:
6559:
6521:
6329:
6296:
6276:
5968:
5880:
5754:
5614:
5469:
5414:
5354:
5317:
5290:
5155:
5102:
5053:
5021:
4979:"Globalization Step-by-Step: The World-Ready Approach to Testing. Microsoft Developer Network"
4899:
4713:
4707:
4686:
4657:
4618:
4608:
4587:
4533:
4527:
4503:
4412:
4378:
4372:
4348:
4253:
4129:
4073:
4048:
4016:
4010:
3982:
3976:
3948:
3913:
3797:
3764:
3758:
3730:
3700:
3675:
3669:
3648:
3642:
3606:
3567:
3538:
3511:
3486:
3482:
3362:
3327:
3263:
3238:
3213:
3188:
3126:
2609:
2491:
1979:
1839:
1828:
1693:
1452:
1303:
1248:
1225:
1100:
787:
748:
701:
5636:
The Leprechauns of Software Engineering: How folklore turns into fact and what to do about it
4678:
4651:
4497:
4406:
4342:
4123:
4042:
3724:
1583:
Sometimes, UAT is performed by the customer, in their environment and on their own hardware.
7510:
7495:
7450:
7376:
7361:
7354:
7220:
7164:
6942:
6834:
6483:
6367:
6334:
6129:
6051:
5940:
5926:
5921:
5870:
5857:
5782:
5735:
5665:
5406:
5346:
5282:
5149:
5069:
5013:
3940:
3905:
3880:
3789:
3474:
3455:
3452:
Combinatorial Test Design in the TOSCA Testsuite: Lessons Learned and Practical Implications
3354:
2950:
2387:
2129:
1907:
1761:
1460:
1444:
1349:
1163:
1105:
610:
424:
387:
369:
359:
5610:
2415:
Verification: Have we built the software right? (i.e., does it implement the requirements).
2267:
buffer to compensate for project delays, thereby compromising the time devoted to testing.
7535:
7240:
7093:
7073:
6957:
6819:
6554:
6448:
6420:
6314:
6266:
6251:
6236:
6091:
6086:
6026:
5916:
5890:
5842:
5787:
3853:
3832:
2938:
2782:
2772:
2538:
2527:
2260:
2254:
2116:
1983:
1750:
1742:
1711:
1542:
1464:
1405:. These procedures may involve full or partial upgrades, and install/uninstall processes.
1182:
1178:
1157:
1115:
1000:
971:
947:
900:
874:
867:
779:
311:
263:
147:
69:
2462:
So, when these words are defined in common terms, the apparent contradiction disappears.
1862:
Ensuring that the color contrast between the font and the background color is appropriate
1064:
is an approach to software testing that is concisely described as simultaneous learning,
995:
are referred to as static testing, whereas executing programmed code with a given set of
663:
Software testing should follow a "pyramid" approach wherein most of your tests should be
5538:
3616:
2816:
than if it had already been found by the requirements review. With the advent of modern
7586:
7561:
7500:
7409:
7381:
7144:
7048:
6789:
6660:
6564:
6463:
6309:
6281:
5010:
Proceedings of the fifth ACM SIGPLAN international conference on Functional programming
4469:
3317:
3147:
3066:. Quality Assurance Institute Worldwide Annual Software Testing Conference. Orlando, FL
2988:
2956:
1997:
1806:
1800:
1659:
1501:
1451:, old or new), or target environments that differ greatly from the original (such as a
1356:
1326:
1256:
1169:
1130:
967:
961:
5634:
Bossavit, Laurent (November 20, 2013). "The cost of defects: an illustrated history".
5122:
4874:"The Relationship between Risk and Continuous Testing: An Interview with Wayne Ariola"
4247:
3089:
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
7606:
7124:
6892:
6549:
5837:
5338:
5049:
4982:
3475:
3321:
2790:
2767:
2733:
2573:
2342:
2338:
creation. Since many activities will be carried out during testing, a plan is needed.
2327:
1855:
1151:
838:
651:
636:
54:
5428:
5083:
4776:"Operational Acceptance – an application of the ISO 29119 Software Testing standard"
4274:
3811:
729:
that causes an undesirable result. Bugs generally slow testing progress and involve
7576:
7571:
7414:
7344:
7159:
7154:
7083:
6645:
6304:
5603:
5368:
5035:
5005:
4433:
3003:
2713:
2707:
2692:
2511:
2301:
2289:
1787:
1782:
1746:
1651:
1647:
1260:
1213:
1122:
1042:
919:
913:
625:
137:
2682:
also contain prerequisite states or steps and descriptions of the following tests.
4125:
Pragmatic Software Testing: Becoming an Effective and Efficient Test Professional
3909:
7591:
7435:
7371:
6635:
6261:
6173:
5286:
3358:
3032:
3026:
2800:
Some practitioners declare that the testing field is not ready for certification
2649:
2605:
2357:
2068:
1965:
1791:
1685:
1681:
1642:
Beta testing comes after alpha testing and can be considered a form of external
1468:
1230:
1141:
1065:
1015:
984:
923:
819:
775:
752:
726:
690:
647:
632:
3936:
In 2014 IEEE 15th International Symposium on High-Assurance Systems Engineering
3899:
2604:
using a many-to-many relationship comparison. It is often used with high-level
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,
7169:
7134:
6655:
6585:
6178:
5911:
5767:
5178:
4304:
4097:
3425:
2674:
2663:
2144:
730:
664:
5576:
3846:
3825:
3793:
1212:
100% statement coverage ensures that all code paths or branches (in terms of
725:
Software testing typically includes handling software bugs – a defect in the
6160:
6121:
5563:
5527:
5350:
5337:
Pinto, Leandro Sales; Sinha, Saurabh; Orso, Alessandro (November 11, 2012).
5205:"Test-Driven Development and Continuous Integration for Mobile Applications"
3118:
3054:
2970: – Proving or disproving the correctness of certain intended algorithms
2678:
2636:
2630:
2617:
2613:
2568:
2562:
2531:
2346:
2331:
1418:
Software systems may need connectivity to connect to other software systems.
1279:
1069:
996:
815:
741:
705:
89:
17:
4070:
Software Testing: Testing Across the Entire Software Development Life Cycle
2191:
In an organization, testers may be in a separate team from the rest of the
837:
Although testing for every possible input is not feasible, testing can use
5494:
5017:
4954:
3459:
3153:
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
6917:
6221:
5311:
3944:
3559:
2029:
1986:, but is used for typing characters in the layout of the target language.
1655:
1654:. Beta versions can be made available to the open public to increase the
1368:
1268:
1019:
899:
Software testing can be categorized into levels based on how much of the
878:
595:
584:
462:
414:
399:
394:
5669:
5410:
5074:
5057:
3450:
Ramler, Rudolf; Kopetzky, Theodorich; Platz, Wolfgang (April 17, 2012).
3284:"The Economic Impacts of Inadequate Infrastructure for Software Testing"
2941: – 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
6724:
4068:
Everatt, G.D.; McLeod Jr., R. (2007). "Chapter 7: Functional Testing".
3934:
2523:
2335:
5401:
Griffiths, M. (2005). "Teaching agile project management to the PMI".
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
6774:
5694:
3884:
3058:
2174:
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.
173:
1200:, which reports on the number of lines executed to complete the test
7284:
5704:
3868:
1412:
Dependent files and libraries must be allocated, loaded or located.
798:
A fundamental limitation of software testing is that testing under
6974:
4803:. Version 3.1. International Software Testing Qualifications Board
4681:. In Borba, P.; Cavalcanti, A.; Sampaio, A.; Woodcook, J. (eds.).
4577:
4575:
4203:
consists of only one statement. All tests against a specification
3869:"Principles and methods of testing finite state machines-a survey"
3697:
Automated Defect Prevention: Best Practices in Software Management
3508:
Automated Defect Prevention: Best Practices in Software Management
3184:
Automated Defect Prevention: Best Practices in Software Management
2698:
product or a project. There are techniques to generate Test data.
1229:
1134:
unimplemented parts of the specification or missing requirements.
1104:
734:
578:
248:
1810:
is a way to test reliability under unexpected or rare workloads.
7185:
3603:
SWEBOK v3.0: Guide to the Software Engineering Body of Knowledge
2985: – Organization that tests according to agreed requirements
2677:, less commonly known as a validation suite, is a collection of
684:
606:
482:
7288:
6728:
5708:
5386:. Software Test & Performance Collaborative. Archived from
5230:
Brown, Chris; Cobb, Gary; Culbertson, Robert (April 12, 2002).
4276:
The Theory and Practice of Specification Based Software Testing
4826:. O'Reilly Media. Section 4. End of the Software Release Cycle
3786:
Proceedings 1997 International Conference on Network Protocols
3477:
Lessons Learned in Software Testing: A Context-Driven Approach
2016:
Localized operating systems may have differently named system
1456:
1372:
4582:
Myers, G. (2004). Sandler, C; Badgett, T; Thomas, M. (eds.).
2964: – Analysis of software performed when running a program
2175:
2162:
whether the actual outputs agree with the expected outcomes.
2013:
Software may display images with text that was not localized.
4706:
Clapp, J.A.; Stanten, S.F.; Peng, W.W.; et al. (1995).
2360:
and whether or not the software tested is ready for release.
5339:"Understanding myths and realities of test-suite evolution"
4847:"Part of the Pipeline: Why Continuous Testing Is Essential"
4746:
ISTQB - International Software Testing Qualifications Board
2807:
Studies used to show the relative expense of fixing defects
5268:
5266:
3351:
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
4685:. Springer Science & Business Media. pp. 13–14.
3035: – Software testing that focuses on web applications
2349:, test datasets, test scripts to use in testing software.
758:
A single defect may result in multiple failure symptoms.
3424:. July 1, 2005. Principle 2, Section 1.3. Archived from
2319:: Testing should begin in the requirements phase of the
2006:
Software may lack proper support for reading or writing
631:
Based on the criteria for measuring correctness from an
5510:"Software testers balk at ISO 29119 standards proposal"
4282:(dissertation thesis). Department of Computer Science,
3210:
Succeeding with Agile: Software Development Using Scrum
1887:
Section 508 Amendment to the Rehabilitation Act of 1973
1479:
operating system functionality into a separate program
5345:. Association for Computing Machinery. pp. 1–11.
3718:
3716:
3023: – Stores test steps, test planning and reporting
1964:
Untranslated messages in the original language may be
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).
583:
TestingCup – Polish Championship in Software Testing,
4798:"Standard Glossary of Terms used in Software Testing"
4709:
Software Quality Control, Error Analysis, and Testing
4374:
Software Quality Control, Error Analysis, and Testing
2947: – Checking web applications in various browsers
2478:
In some organizations, software testing is part of a
2202:
started to be used to denote a separate profession.
1951:
Software is often localized by translating a list of
4645:
4643:
4641:
2999:
Pages displaying wikidata descriptions as a fallback
2978:
Pages displaying wikidata descriptions as a fallback
7549:
7423:
7392:
7322:
7213:
7178:
7117:
7031:
7024:
6983:
6843:
6762:
6573:
6520:
6482:
6429:
6391:
6353:
6295:
6212:
6158:
6120:
6065:
6002:
5935:
5899:
5856:
5820:
5753:
5700:"Software that makes Software better" Economist.com
5173:
5171:
4677:Machado, P.; Vincenzi, A.; Maldonado, J.C. (2010).
4653:
Software Testing and Continuous Quality Improvement
4499:
Software Testing and Continuous Quality Improvement
4225:
4204:
4153:
4117:
4115:
3970:
3968:
3966:
3964:
3760:
Verification and Validation in Scientific Computing
3752:
3750:
3748:
3746:
3564:
Guide to the Software Engineering Body of Knowledge
3558:Bourque, Pierre; Fairley, Richard E., eds. (2014).
3422:
International Software Testing Qualifications Board
3386:
International Software Testing Qualifications Board
2205:Notable software testing roles and titles include:
1741:of input validation and error-management routines.
5602:
4556:(white paper). Crosscheck Networks. Archived from
4491:
4489:
4487:
4004:
4002:
4000:
3998:
3723:Graham, D.; Van Veenendaal, E.; Evans, I. (2008).
3473:Kaner, Cem; Bach, James; Pettichord, Bret (2001).
4554:"SOA Testing Tools for Black, White and Gray Box"
3699:. Wiley-IEEE Computer Society Press. p. 75.
3510:. Wiley-IEEE Computer Society Press. p. 74.
4959:. International Organization for Standardization
4521:
4519:
4091:
4089:
4036:
4034:
4032:
3146:Leitner, Andreas; Ciupa, Ilinca; Oriol, Manuel;
5569:Measuring the Effectiveness of Software Testers
5444:"Agile Software Development for an Agile Force"
5101:. Addison-Wesley Professional. pp. 23–39.
4907:. Pacific Northwest Software Quality Conference
4901:DevOps: Are You Pushing Bugs to Clients Faster?
4898:Ariola, Wayne; Dunlop, Cynthia (October 2015).
4607:Ammann, Paul; Offutt, Jeff (January 28, 2008).
4441:(MSc thesis). Helsinki University of Technology
4252:(2nd ed.). Indianapolis: Sams Publishing.
3981:. Tata McGraw-Hill Education. pp. 108–11.
3388:. March 31, 2011. Section 1.1.2. Archived from
3345:
3343:
3125:(2nd ed.). New York: John Wiley and Sons.
2549:A software testing process can produce several
2115:Creating a display expected output, whether as
2000:may become unreadable if the font is too small.
1710:Continuous testing is the process of executing
983:There are many approaches to software testing.
4529:Core Software Security: Security at the Source
3763:. Cambridge University Press. pp. 154–5.
3644:Software Development and Professional Practice
3291:National Institute of Standards and Technology
2297:is to support development and reduce defects.
1982:that has no function on the source language's
1971: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
7300:
6740:
5744:Note: This template roughly follows the 2012
5720:
5664:. Vol. 41, no. 8. pp. 99–101.
5313:IEEE standard for software test documentation
4981:. Microsoft Developer Network. Archived from
4872:Philipp-Edmonds, Cameron (December 5, 2014).
3312:
3310:
3308:
2407: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:
8:
5464:An example is Mark Fewster, Dorothy Graham:
3415:"Certified Tester Foundation Level Syllabus"
3382:"Certified Tester Foundation Level Syllabus"
2427:Glossary of Software Engineering Terminology
1968:in the source code, and thus untranslatable.
1790:. This is generally referred to as software
755:, and interacting with different software.
4502:(3rd ed.). CRC Press. pp. 68–73.
4100:. Bullseye Testing Technology. Introduction
2991: – Testing software without automation
2804:competence, or professionalism as a tester.
1355:binary." Grey-box testing may also include
717:Software testing is typically goal driven.
7307:
7293:
7285:
7028:
6747:
6733:
6725:
5727:
5713:
5705:
5154:. Addison-Wesley Professional. p. 3.
4683:Testing Techniques in Software Engineering
4679:"Chapter 1: Software Testing: An Overview"
4656:(3rd ed.). CRC Press. pp. 92–6.
4072:. John Wiley & Sons. pp. 99–121.
4047:. Cambridge University Press. p. 26.
2293:part of regression testing. Goals of this
567:
553:
31:
5609:(2nd ed.). Microsoft Press. p.
5073:
3594:Bourque, P.; Fairley, R.D., eds. (2014).
2440:And, according to the ISO 9000 standard:
2074:better at achieving the desired outcome.
1471:). For example, in the case of a lack of
6938:Software development process/methodology
5251:(coursework). Carnegie Mellon University
5179:"What is Test Driven Development (TDD)?"
4366:
4364:
4128:. John Wiley & Sons. pp. 44–6.
3176:
3174:
3121:; Falk, Jack; Nguyen, Hung Quoc (1999).
3113:
3111:
3109:
3107:
3092:(coursework). Carnegie Mellon University
2822:
2734:Certification § In software testing
2502:Quality measures include such topics as
2059:, and other software testing practices.
1922:systems are not denied access to them."
1409:A user must select a variety of options.
1029:, whereas dynamic testing also involves
926:is tested to validate expected behavior.
5249:"Verification/Validation/Certification"
4411:. Pearson Education India. p. 18.
4347:. Pearson Education India. p. 63.
4015:. J. Ross Publishing. pp. 224–41.
3695:Kolawa, Adam; Huizinga, Dorota (2007).
3671:Creating a Software Engineering Culture
3506:Kolawa, Adam; Huizinga, Dorota (2007).
3181:Kolawa, Adam; Huizinga, Dorota (2007).
3046:
1882:Americans with Disabilities Act of 1990
1638:Software release life cycle § Beta
704:initially introduced the separation of
39:
6444:Knowledge representation and reasoning
5655:"Seven Principles of Software Testing"
5233:Introduction to Rapid Software Testing
5097:Gregory, Janet; Crispin, Lisa (2014).
4712:. Nova Data Corporation. p. 254.
3788:. IEEE Comput. Soc. pp. 113–122.
2537:There are a number of frequently used
2399:Verification and validation (software)
1868:Alternate Texts for multimedia content
1459:application intended to be run on the
857:Testing can be categorized many ways.
521:Electrical and electronics engineering
6469:Philosophy of artificial intelligence
5403:Agile Development Conference (ADC'05)
5004:Claessen, Koen; Hughes, John (2000).
4733:
4731:
4729:
4309:"Risk and Requirements-Based Testing"
3187:. Wiley-IEEE Computer Society Press.
3083:
3081:
2825:
2585:These paragraphs are an excerpt from
2251:Capability Maturity Model Integration
1932:internationalization and localization
1926:Internationalization and localization
1646:. Versions of the software, known as
1194:, which reports on functions executed
1185:can be reported as a percentage for:
1181:have been tested. Code coverage as a
7:
7259:
6953:Software verification and validation
6856:Component-based software engineering
5788:Energy consumption (Green computing)
4822:O'Reilly, Tim (September 30, 2005).
3729:. Cengage Learning. pp. 57–58.
2976: – term in software engineering
2793:software testing standard justified?
2393:Software verification and validation
1666:Functional vs non-functional testing
1573:Operational acceptance testing (OAT)
1148:(application programming interfaces)
979:Static, dynamic, and passive testing
27:Checking software against a standard
6474:Distributed artificial intelligence
5746:ACM Computing Classification System
5691:Software testing tools and products
5129:. Testing Phase in Software Testing
4755:from the original on March 24, 2022
3757:Oberkampf, W.L.; Roy, C.J. (2010).
2341:Test development: Test procedures,
2096:Conformance testing or type testing
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
5979:Integrated development environment
5450:(April 2004). STSC. Archived from
4928:"Shift Left and Put Quality First"
4926:Auerbach, Adam (October 2, 2014).
4774:Woods, Anthony J. (June 5, 2015).
3674:. Addison-Wesley. pp. 211–2.
3258:Fernandes da Costa, Lucas (2021).
3029: – Software testing technique
3006: – Software testing technique
2997: – software testing technique
1989:Software may lack support for the
1948:Some messages may be untranslated.
1601:Operations readiness and assurance
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:
6933:Software configuration management
6800:Search-based software engineering
6785:Experimental software engineering
6454:Automated planning and scheduling
5984:Software configuration management
5279:Software and Systems Traceability
4845:Auerbach, Adam (August 3, 2015).
4778:(Whitepaper). Capgemini Australia
4432:Lönnberg, Jan (October 7, 2003).
3847:A Tutorial in Exploratory Testing
3826:A Tutorial in Exploratory Testing
3012: – Quality control technique
2514:requirements such as capability,
447:Standards and bodies of knowledge
7618:Software engineering terminology
7557:Graphical user interface testing
7269:
7268:
7258:
6708:
6698:
6689:
6688:
5442:Willison, John S. (April 2004).
5058:"The growth of software testing"
4610:Introduction to Software Testing
4044:Introduction to Software Testing
3867:Lee, D.; Yannakakis, M. (1996).
2974:Graphical user interface testing
2740:
2662:This section is an excerpt from
2286:test-driven software development
1392:This section is an excerpt from
1339:Graphical user interface testing
1054:This section is an excerpt from
6699:
6102:Computational complexity theory
5653:Meyer, Bertrand (August 2008).
4526:Ransome, J.; Misra, A. (2013).
4408:Foundations of Software Testing
4377:. William Andrew. p. 313.
4344:Foundations of Software Testing
4041:Ammann, P.; Offutt, J. (2016).
3726:Foundations of Software Testing
3260:Testing JavaScript Applications
3212:. Addison-Wesley Professional.
3150:; Fiva, Arno (September 2007).
2321:software development life cycle
1876:Common Standards for compliance
1463:now being required to become a
594:is the act of checking whether
539:Outline of software development
6780:Empirical software engineering
5886:Network performance evaluation
5508:Paul Krill (August 22, 2014).
5405:. ieee.org. pp. 318–322.
5012:. Icfp '00. pp. 268–279.
3566:. 3.0. IEEE Computer Society.
2753:software testing controversies
810:versus what it is supposed to
1:
6257:Multimedia information system
6242:Geographic information system
6232:Enterprise information system
5821:Computer systems organization
5384:"We're All Part of the Story"
5382:Strom, David (July 1, 2009).
4532:. CRC Press. pp. 140–3.
3596:"Chapter 4: Software Testing"
3010:Reverse semantic traceability
2983:Independent test organization
1570:User acceptance testing (UAT)
1018:/drivers or execution from a
7582:Software reliability testing
7521:Software performance testing
6805:Site reliability engineering
6616:Computational social science
6204:Theoretical computer science
6017:Software development process
5793:Electronic design automation
5778:Very Large Scale Integration
5123:"Software Testing Lifecycle"
4273:Laycock, Gilbert T. (1993).
3910:10.1007/978-3-642-24580-0_12
3088:Pan, Jiantao (Spring 1999).
2778:Manual vs. automated testing
1892:Web Accessibility Initiative
1773:Software performance testing
1767:Software performance testing
6810:Social software engineering
6439:Natural language processing
6227:Information storage systems
5575:. STAR East. Archived from
5287:10.1007/978-1-4471-2239-5_1
5209:Microsoft Developer Network
4584:The Art of Software Testing
3605:. IEEE. pp. 4–1–4–17.
3359:10.1109/IEEESTD.1990.101064
3323:The Art of Software Testing
3233:Molina, Alessandro (2021).
2409:verification and validation
2130:property testing algorithms
1720:non-functional requirements
1298:Component interface testing
768:non-functional requirements
7634:
7424:Testing types, techniques,
6948:Software quality assurance
6355:Human–computer interaction
6325:Intrusion detection system
6237:Social information systems
6222:Database management system
5151:Effective Software Testing
4739:"ISTQB CTFL Syllabus 2018"
4615:Cambridge University Press
4435:Visual testing of software
4405:Mathur, Aditya P. (2007).
4096:Cornett, Steve (c. 1996).
3939:. IEEE. pp. 224–228.
3647:. APress. pp. 193–4.
2781:Some writers believe that
2731:
2705:
2690:
2661:
2628:
2584:
2560:
2480:software quality assurance
2474:Software quality assurance
2396:
2385:
2279:Agile software development
2248:
2154:
2127:
2099:
2081:
2066:
2040:
1770:
1755:
1729:
1703:
1674:particular feature work."
1635:
1553:
1521:
1494:
1428:
1391:
1347:
1336:
1223:
1098:
1053:
959:
935:
911:
865:
850:
302:Software quality assurance
7254:
6684:
6621:Computational engineering
6596:Computational mathematics
5742:
5601:McConnell, Steve (2004).
5466:Software Test Automation.
5148:Dustin, Elfriede (2002).
5062:Communications of the ACM
4371:Clapp, Judith A. (1995).
4148:As a simple example, the
3123:Testing Computer Software
2850:
2828:
2687:Test fixture or test data
2111: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.
620:of software for specific
598:satisfies expectations.
7567:Orthogonal array testing
7516:Smoke testing (software)
7486:Dynamic program analysis
7104:Model-driven engineering
6903:Functional specification
6886:Software incompatibility
6795:Requirements engineering
6631:Computational healthcare
6626:Differentiable computing
6545:Graphics processing unit
5964:Domain-specific language
5833:Computational complexity
4224:will succeed, except if
4098:"Code Coverage Analysis"
3794:10.1109/icnp.1997.643699
3016:Software testing tactics
2995:Orthogonal array testing
2962:Dynamic program analysis
2789:Is the existence of the
2403:Software quality control
2128: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
287:Configuration management
6898:Enterprise architecture
6606:Computational chemistry
6540:Photograph manipulation
6431:Artificial intelligence
6247:Decision support system
5351:10.1145/2393596.2393634
5247:Tran, Eushiuan (1999).
4284:University of Sheffield
3873:Proceedings of the IEEE
3326:. John Wiley and Sons.
2198:In the 1980s, the term
1993: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
7109:Round-trip engineering
6866:Backward compatibility
6861:Software compatibility
6671:Educational technology
6502:Reinforcement learning
6252:Process control system
6150:Computational geometry
6140:Algorithmic efficiency
6135:Analysis of algorithms
5783:Systems on Chip (SoCs)
5491:commonsensetesting.org
5468:Addison Wesley, 1999,
2953:, testing of databases
2929:
2928:
2914:
2295: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
7446:Compatibility testing
6928:Software architecture
6881:Forward compatibility
6641:Electronic publishing
6611:Computational biology
6601:Computational physics
6497:Unsupervised learning
6411:Distributed computing
6287:Information retrieval
6194:Mathematical analysis
6184:Mathematical software
6067:Theory of computation
6032:Software construction
6022:Requirements analysis
5900:Software organization
5828:Computer architecture
5798:Hardware acceleration
5763:Printed circuit board
5018:10.1145/351240.351266
4586:(2 ed.). Wiley.
4341:Mathur, A.P. (2011).
4236:happens to be chosen.
3975:Limaye, M.G. (2009).
3460:10.1109/ICST.2012.142
3057:(November 17, 2006).
2945:Cross-browser testing
2919:
2915:
2826:Cost to fix a defect
2818:continuous deployment
2813:
2759:Agile vs. traditional
2732:Further information:
2530:, compatibility, and
2317:Requirements analysis
2261:waterfall development
2249:Further information:
2245:Waterfall development
2022: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
7491:Installation testing
7481:Differential testing
7226:Computer engineering
6923:Software archaeology
6913:Programming paradigm
6825:Software maintenance
6770:Computer programming
6756:Software engineering
6401:Concurrent computing
6373:Ubiquitous computing
6345:Application security
6340:Information security
6169:Discrete mathematics
6145:Randomized algorithm
6097:Computability theory
6075:Model of computation
6047:Software maintenance
6042:Software engineering
6004:Software development
5954:Programming language
5949:Programming paradigm
5866:Network architecture
5544:on November 27, 2009
5454:on October 29, 2005.
4650:Lewis, W.E. (2016).
4496:Lewis, W.E. (2016).
4246:Patton, Ron (2005).
4012:Software Engineering
4009:Saleh, K.A. (2009).
3945:10.1109/HASE.2014.39
3668:Wiegers, K. (2013).
3431:on December 17, 2008
3237:. Packt Publishing.
3021:Test management tool
2671:software development
2594:software development
2484:software engineering
2284:One agile practice,
2227:automation developer
2193:software development
2090:concurrent computing
2053: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
7476:Development testing
7471:Destructive testing
7461:Conformance testing
7405:Integration testing
7350:Model-based testing
7340:Exploratory testing
7246:Systems engineering
7231:Information science
7011:Service orientation
6963:Structured analysis
6871:Compatibility layer
6815:Software deployment
6676:Document management
6666:Operations research
6591:Enterprise software
6507:Multi-task learning
6492:Supervised learning
6214:Information systems
6037:Software deployment
5994:Software repository
5848:Real-time computing
5670:10.1109/MC.2008.306
5497:on October 2, 2014.
5411:10.1109/ADC.2005.45
5390:on August 31, 2009.
5281:. Springer London.
5275:Cleland-Huang, Jane
5075:10.1145/62959.62965
3641:Dooley, J. (2011).
3395:on October 28, 2017
3208:Cohn, Mike (2009).
3060:Exploratory Testing
2968:Formal verification
2612:, detailed design,
2602:baselined documents
2598:traceability matrix
2587:Traceability matrix
2580:Traceability matrix
2288:(TDD), is a way of
2157:Metamorphic testing
2151:Metamorphic testing
2102:Conformance testing
2043:Development testing
2037:Development testing
2018:configuration files
2008:bi-directional text
1978:Software may use a
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
7531:Symbolic execution
7506:Regression testing
7466:Continuous testing
7456:Concurrent testing
7400:Acceptance testing
7323:The "box" approach
7236:Project management
7001:Object orientation
6968:Essential analysis
6876:Compatibility mode
6459:Search methodology
6406:Parallel computing
6363:Interaction design
6272:Computing platform
6199:Numerical analysis
6189:Information theory
5974:Software framework
5937:Software notations
5876:Network components
5773:Integrated circuit
5316:. New York: IEEE.
5211:. January 14, 2009
5185:. December 5, 2015
5099:More Agile Testing
4560:on October 1, 2018
4122:Black, R. (2011).
3852:2013-06-12 at the
3831:2013-06-12 at the
3481:. Wiley. pp.
3318:Myers, Glenford J.
3090:"Software Testing"
2764:process "maturity"
2751:Some of the major
2371:Regression testing
2231:test administrator
2084:Concurrent testing
2078:Concurrent testing
1991: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
7600:
7599:
7541:Usability testing
7367:White-box testing
7335:All-pairs testing
7330:Black-box testing
7282:
7281:
7209:
7208:
7150:Information model
7054:Incremental model
6908:Modeling language
6722:
6721:
6651:Electronic voting
6581:Quantum Computing
6574:Applied computing
6560:Image compression
6330:Hardware security
6320:Security services
6277:Digital marketing
6057:Open-source model
5969:Modeling language
5881:Network scheduler
5620:978-0-7356-1967-8
5582:on March 26, 2010
5474:978-0-201-33140-0
5420:978-0-7695-2487-0
5323:978-0-7381-1443-9
5161:978-0-201-79429-8
5108:978-0-13-374956-4
5027:978-1-58113-202-1
4932:TechWell Insights
4851:TechWell Insights
4824:"What is Web 2.0"
4719:978-0-8155-1363-6
4692:978-3-642-14334-2
4663:978-1-4398-3436-7
4624:978-0-521-88038-1
4539:978-1-4665-6095-6
4509:978-1-4398-3436-7
4418:978-81-317-1660-1
4384:978-0-8155-1363-6
4354:978-81-317-5908-0
4259:978-0-672-32798-8
4135:978-1-118-07938-6
4079:978-0-470-14634-7
4054:978-1-316-77312-3
4022:978-1-932159-94-3
3988:978-0-07-013990-9
3954:978-1-4799-3466-9
3919:978-3-642-24579-4
3803:978-0-8186-8061-8
3770:978-1-139-49176-1
3736:978-1-84480-989-9
3706:978-0-470-04212-0
3681:978-0-13-348929-3
3654:978-1-4302-3801-0
3612:978-0-7695-5166-1
3573:978-0-7695-5166-1
3544:978-3-319-24647-5
3517:978-0-470-04212-0
3492:978-0-471-08112-8
3368:978-1-55937-067-7
3333:978-0-471-04328-7
3194:978-0-470-04212-0
3132:978-0-471-35846-6
2913:
2912:
2610:high-level design
2492:quality assurance
2274:Agile development
1980: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
7625:
7613:Software testing
7511:Security testing
7496:Negative testing
7451:Concolic testing
7377:Mutation testing
7362:Grey-box testing
7355:Scenario testing
7316:Software testing
7309:
7302:
7295:
7286:
7272:
7271:
7262:
7261:
7221:Computer science
7029:
6943:Software quality
6835:Systems analysis
6830:Software testing
6749:
6742:
6735:
6726:
6712:
6711:
6702:
6701:
6692:
6691:
6512:Cross-validation
6484:Machine learning
6368:Social computing
6335:Network security
6130:Algorithm design
6052:Programming team
6012:Control variable
5989:Software library
5927:Software quality
5922:Operating system
5871:Network protocol
5736:Computer science
5729:
5722:
5715:
5706:
5680:
5678:
5676:
5659:
5640:
5639:
5631:
5625:
5624:
5608:
5598:
5592:
5591:
5589:
5587:
5581:
5574:
5560:
5554:
5553:
5551:
5549:
5543:
5537:. Archived from
5536:
5524:
5518:
5517:
5505:
5499:
5498:
5493:. Archived from
5483:
5477:
5462:
5456:
5455:
5439:
5433:
5432:
5398:
5392:
5391:
5379:
5373:
5372:
5334:
5328:
5327:
5307:
5301:
5300:
5270:
5261:
5260:
5258:
5256:
5244:
5238:
5237:
5227:
5221:
5220:
5218:
5216:
5201:
5195:
5194:
5192:
5190:
5175:
5166:
5165:
5145:
5139:
5138:
5136:
5134:
5119:
5113:
5112:
5094:
5088:
5087:
5077:
5056:(June 1, 1988).
5046:
5040:
5039:
5001:
4995:
4994:
4992:
4990:
4985:on June 23, 2012
4975:
4969:
4968:
4966:
4964:
4953:"Section 4.38".
4950:
4944:
4943:
4941:
4939:
4923:
4917:
4916:
4914:
4912:
4906:
4895:
4889:
4888:
4886:
4884:
4869:
4863:
4862:
4860:
4858:
4842:
4836:
4835:
4833:
4831:
4819:
4813:
4812:
4810:
4808:
4802:
4794:
4788:
4787:
4785:
4783:
4771:
4765:
4764:
4762:
4760:
4754:
4743:
4735:
4724:
4723:
4703:
4697:
4696:
4674:
4668:
4667:
4647:
4636:
4635:
4633:
4631:
4604:
4598:
4597:
4579:
4570:
4569:
4567:
4565:
4550:
4544:
4543:
4523:
4514:
4513:
4493:
4482:
4481:
4479:
4477:
4472:on July 24, 2012
4468:. Archived from
4462:"Visual testing"
4457:
4451:
4450:
4448:
4446:
4440:
4429:
4423:
4422:
4402:
4396:
4395:
4393:
4391:
4368:
4359:
4358:
4338:
4332:
4331:
4329:
4327:
4313:
4301:
4295:
4294:
4292:
4290:
4281:
4270:
4264:
4263:
4249:Software Testing
4243:
4237:
4235:
4234:
4231:
4228:
4223:
4222:
4219:
4216:
4213:
4210:
4207:
4202:
4201:
4198:
4195:
4192:
4189:
4186:
4183:
4180:
4177:
4174:
4171:
4168:
4165:
4162:
4159:
4156:
4146:
4140:
4139:
4119:
4110:
4109:
4107:
4105:
4093:
4084:
4083:
4065:
4059:
4058:
4038:
4027:
4026:
4006:
3993:
3992:
3978:Software Testing
3972:
3959:
3958:
3930:
3924:
3923:
3895:
3889:
3888:
3885:10.1109/5.533956
3879:(8): 1090–1123.
3864:
3858:
3842:
3836:
3822:
3816:
3815:
3781:
3775:
3774:
3754:
3741:
3740:
3720:
3711:
3710:
3692:
3686:
3685:
3665:
3659:
3658:
3638:
3632:
3631:
3629:
3627:
3622:on June 19, 2018
3621:
3615:. Archived from
3600:
3591:
3585:
3584:
3582:
3580:
3555:
3549:
3548:
3528:
3522:
3521:
3503:
3497:
3496:
3480:
3470:
3464:
3463:
3447:
3441:
3440:
3438:
3436:
3430:
3419:
3411:
3405:
3404:
3402:
3400:
3394:
3378:
3372:
3371:
3347:
3338:
3337:
3314:
3303:
3302:
3300:
3298:
3288:
3280:
3274:
3273:
3255:
3249:
3248:
3230:
3224:
3223:
3205:
3199:
3198:
3178:
3169:
3168:
3166:
3164:
3158:
3143:
3137:
3136:
3115:
3102:
3101:
3099:
3097:
3085:
3076:
3075:
3073:
3071:
3065:
3051:
3000:
2979:
2951:Database testing
2851:Time introduced
2823:
2539:software metrics
2506:, completeness,
2388:Software quality
2124:Property testing
2026: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:
21:
7633:
7632:
7628:
7627:
7626:
7624:
7623:
7622:
7603:
7602:
7601:
7596:
7545:
7536:Test automation
7425:
7419:
7388:
7318:
7313:
7283:
7278:
7250:
7241:Risk management
7205:
7174:
7113:
7094:Waterfall model
7064:Prototype model
7059:Iterative model
7020:
6996:Aspect-oriented
6979:
6958:Software system
6839:
6820:Software design
6758:
6753:
6723:
6718:
6709:
6680:
6661:Word processing
6569:
6555:Virtual reality
6516:
6478:
6449:Computer vision
6425:
6421:Multiprocessing
6387:
6349:
6315:Security hacker
6291:
6267:Digital library
6208:
6159:Mathematics of
6154:
6116:
6092:Automata theory
6087:Formal language
6061:
6027:Software design
5998:
5931:
5917:Virtual machine
5895:
5891:Network service
5852:
5843:Embedded system
5816:
5749:
5738:
5733:
5687:
5674:
5672:
5657:
5652:
5649:
5647:Further reading
5644:
5643:
5633:
5632:
5628:
5621:
5600:
5599:
5595:
5585:
5583:
5579:
5572:
5562:
5561:
5557:
5547:
5545:
5541:
5534:
5526:
5525:
5521:
5507:
5506:
5502:
5485:
5484:
5480:
5463:
5459:
5441:
5440:
5436:
5421:
5400:
5399:
5395:
5381:
5380:
5376:
5361:
5336:
5335:
5331:
5324:
5309:
5308:
5304:
5297:
5273:Gotel, Orlena;
5272:
5271:
5264:
5254:
5252:
5246:
5245:
5241:
5229:
5228:
5224:
5214:
5212:
5203:
5202:
5198:
5188:
5186:
5177:
5176:
5169:
5162:
5147:
5146:
5142:
5132:
5130:
5121:
5120:
5116:
5109:
5096:
5095:
5091:
5050:Gelperin, David
5048:
5047:
5043:
5028:
5003:
5002:
4998:
4988:
4986:
4977:
4976:
4972:
4962:
4960:
4952:
4951:
4947:
4937:
4935:
4934:. TechWell Corp
4925:
4924:
4920:
4910:
4908:
4904:
4897:
4896:
4892:
4882:
4880:
4871:
4870:
4866:
4856:
4854:
4853:. TechWell Corp
4844:
4843:
4839:
4829:
4827:
4821:
4820:
4816:
4806:
4804:
4800:
4796:
4795:
4791:
4781:
4779:
4773:
4772:
4768:
4758:
4756:
4752:
4741:
4737:
4736:
4727:
4720:
4705:
4704:
4700:
4693:
4676:
4675:
4671:
4664:
4649:
4648:
4639:
4629:
4627:
4625:
4617:. p. 215.
4606:
4605:
4601:
4594:
4581:
4580:
4573:
4563:
4561:
4552:
4551:
4547:
4540:
4525:
4524:
4517:
4510:
4495:
4494:
4485:
4475:
4473:
4460:Chima, Raspal.
4459:
4458:
4454:
4444:
4442:
4438:
4431:
4430:
4426:
4419:
4404:
4403:
4399:
4389:
4387:
4385:
4370:
4369:
4362:
4355:
4340:
4339:
4335:
4325:
4323:
4311:
4303:
4302:
4298:
4288:
4286:
4279:
4272:
4271:
4267:
4260:
4245:
4244:
4240:
4232:
4229:
4226:
4220:
4217:
4214:
4211:
4208:
4205:
4199:
4196:
4193:
4190:
4187:
4184:
4181:
4178:
4175:
4172:
4169:
4166:
4163:
4160:
4157:
4154:
4147:
4143:
4136:
4121:
4120:
4113:
4103:
4101:
4095:
4094:
4087:
4080:
4067:
4066:
4062:
4055:
4040:
4039:
4030:
4023:
4008:
4007:
3996:
3989:
3974:
3973:
3962:
3955:
3932:
3931:
3927:
3920:
3897:
3896:
3892:
3866:
3865:
3861:
3854:Wayback Machine
3843:
3839:
3833:Wayback Machine
3823:
3819:
3804:
3783:
3782:
3778:
3771:
3756:
3755:
3744:
3737:
3722:
3721:
3714:
3707:
3694:
3693:
3689:
3682:
3667:
3666:
3662:
3655:
3640:
3639:
3635:
3625:
3623:
3619:
3613:
3598:
3593:
3592:
3588:
3578:
3576:
3574:
3557:
3556:
3552:
3545:
3530:
3529:
3525:
3518:
3505:
3504:
3500:
3493:
3472:
3471:
3467:
3449:
3448:
3444:
3434:
3432:
3428:
3417:
3413:
3412:
3408:
3398:
3396:
3392:
3380:
3379:
3375:
3369:
3349:
3348:
3341:
3334:
3316:
3315:
3306:
3296:
3294:
3286:
3282:
3281:
3277:
3270:
3257:
3256:
3252:
3245:
3232:
3231:
3227:
3220:
3207:
3206:
3202:
3195:
3180:
3179:
3172:
3162:
3160:
3156:
3148:Meyer, Bertrand
3145:
3144:
3140:
3133:
3117:
3116:
3105:
3095:
3093:
3087:
3086:
3079:
3069:
3067:
3063:
3053:
3052:
3048:
3043:
3038:
2998:
2977:
2939:Data validation
2934:
2926:Boehm's claims.
2783:test automation
2773:Waterfall model
2749:
2736:
2730:
2722:
2710:
2704:
2695:
2689:
2684:
2683:
2667:
2659:
2646:
2633:
2627:
2622:
2621:
2590:
2582:
2565:
2559:
2547:
2528:maintainability
2500:
2476:
2405:
2397:Main articles:
2395:
2390:
2384:
2326:Test planning:
2310:
2276:
2257:
2255:Waterfall model
2247:
2239:
2200:software tester
2189:
2184:
2168:
2159:
2153:
2133:
2126:
2117:data comparison
2113:
2104:
2098:
2086:
2080:
2071:
2065:
2045:
2039:
1984: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:
7631:
7629:
7621:
7620:
7615:
7605:
7604:
7598:
7597:
7595:
7594:
7589:
7587:Stress testing
7584:
7579:
7574:
7569:
7564:
7562:Manual testing
7559:
7553:
7551:
7547:
7546:
7544:
7543:
7538:
7533:
7528:
7526:Stress testing
7523:
7518:
7513:
7508:
7503:
7501:Random testing
7498:
7493:
7488:
7483:
7478:
7473:
7468:
7463:
7458:
7453:
7448:
7443:
7438:
7432:
7430:
7421:
7420:
7418:
7417:
7412:
7410:System testing
7407:
7402:
7396:
7394:
7393:Testing levels
7390:
7389:
7387:
7386:
7385:
7384:
7382:Static testing
7379:
7374:
7364:
7359:
7358:
7357:
7352:
7347:
7342:
7337:
7326:
7324:
7320:
7319:
7314:
7312:
7311:
7304:
7297:
7289:
7280:
7279:
7277:
7276:
7266:
7255:
7252:
7251:
7249:
7248:
7243:
7238:
7233:
7228:
7223:
7217:
7215:
7214:Related fields
7211:
7210:
7207:
7206:
7204:
7203:
7198:
7193:
7188:
7182:
7180:
7176:
7175:
7173:
7172:
7167:
7162:
7157:
7152:
7147:
7145:Function model
7142:
7137:
7132:
7127:
7121:
7119:
7115:
7114:
7112:
7111:
7106:
7101:
7096:
7091:
7086:
7081:
7076:
7071:
7066:
7061:
7056:
7051:
7049:Executable UML
7046:
7041:
7035:
7033:
7026:
7022:
7021:
7019:
7018:
7013:
7008:
7003:
6998:
6993:
6987:
6985:
6981:
6980:
6978:
6977:
6972:
6971:
6970:
6960:
6955:
6950:
6945:
6940:
6935:
6930:
6925:
6920:
6915:
6910:
6905:
6900:
6895:
6890:
6889:
6888:
6883:
6878:
6873:
6868:
6858:
6853:
6847:
6845:
6841:
6840:
6838:
6837:
6832:
6827:
6822:
6817:
6812:
6807:
6802:
6797:
6792:
6790:Formal methods
6787:
6782:
6777:
6772:
6766:
6764:
6760:
6759:
6754:
6752:
6751:
6744:
6737:
6729:
6720:
6719:
6717:
6716:
6706:
6696:
6685:
6682:
6681:
6679:
6678:
6673:
6668:
6663:
6658:
6653:
6648:
6643:
6638:
6633:
6628:
6623:
6618:
6613:
6608:
6603:
6598:
6593:
6588:
6583:
6577:
6575:
6571:
6570:
6568:
6567:
6565:Solid modeling
6562:
6557:
6552:
6547:
6542:
6537:
6532:
6526:
6524:
6518:
6517:
6515:
6514:
6509:
6504:
6499:
6494:
6488:
6486:
6480:
6479:
6477:
6476:
6471:
6466:
6464:Control method
6461:
6456:
6451:
6446:
6441:
6435:
6433:
6427:
6426:
6424:
6423:
6418:
6416:Multithreading
6413:
6408:
6403:
6397:
6395:
6389:
6388:
6386:
6385:
6380:
6375:
6370:
6365:
6359:
6357:
6351:
6350:
6348:
6347:
6342:
6337:
6332:
6327:
6322:
6317:
6312:
6310:Formal methods
6307:
6301:
6299:
6293:
6292:
6290:
6289:
6284:
6282:World Wide Web
6279:
6274:
6269:
6264:
6259:
6254:
6249:
6244:
6239:
6234:
6229:
6224:
6218:
6216:
6210:
6209:
6207:
6206:
6201:
6196:
6191:
6186:
6181:
6176:
6171:
6165:
6163:
6156:
6155:
6153:
6152:
6147:
6142:
6137:
6132:
6126:
6124:
6118:
6117:
6115:
6114:
6109:
6104:
6099:
6094:
6089:
6084:
6083:
6082:
6071:
6069:
6063:
6062:
6060:
6059:
6054:
6049:
6044:
6039:
6034:
6029:
6024:
6019:
6014:
6008:
6006:
6000:
5999:
5997:
5996:
5991:
5986:
5981:
5976:
5971:
5966:
5961:
5956:
5951:
5945:
5943:
5933:
5932:
5930:
5929:
5924:
5919:
5914:
5909:
5903:
5901:
5897:
5896:
5894:
5893:
5888:
5883:
5878:
5873:
5868:
5862:
5860:
5854:
5853:
5851:
5850:
5845:
5840:
5835:
5830:
5824:
5822:
5818:
5817:
5815:
5814:
5805:
5800:
5795:
5790:
5785:
5780:
5775:
5770:
5765:
5759:
5757:
5751:
5750:
5743:
5740:
5739:
5734:
5732:
5731:
5724:
5717:
5709:
5703:
5702:
5697:
5686:
5685:External links
5683:
5682:
5681:
5648:
5645:
5642:
5641:
5626:
5619:
5593:
5555:
5519:
5500:
5478:
5457:
5434:
5419:
5393:
5374:
5359:
5329:
5322:
5302:
5295:
5262:
5239:
5222:
5196:
5183:Agile Alliance
5167:
5160:
5140:
5114:
5107:
5089:
5068:(6): 687–695.
5041:
5026:
4996:
4970:
4945:
4918:
4890:
4864:
4837:
4814:
4789:
4766:
4725:
4718:
4698:
4691:
4669:
4662:
4637:
4623:
4599:
4592:
4571:
4545:
4538:
4515:
4508:
4483:
4452:
4424:
4417:
4397:
4383:
4360:
4353:
4333:
4296:
4265:
4258:
4238:
4141:
4134:
4111:
4085:
4078:
4060:
4053:
4028:
4021:
3994:
3987:
3960:
3953:
3925:
3918:
3890:
3859:
3837:
3817:
3802:
3776:
3769:
3742:
3735:
3712:
3705:
3687:
3680:
3660:
3653:
3633:
3611:
3586:
3572:
3550:
3543:
3523:
3516:
3498:
3491:
3465:
3442:
3406:
3373:
3367:
3353:, IEEE, 1990,
3339:
3332:
3304:
3275:
3269:978-1617297915
3268:
3250:
3244:978-1838642655
3243:
3225:
3219:978-0321579362
3218:
3200:
3193:
3170:
3138:
3131:
3103:
3077:
3045:
3044:
3042:
3039:
3037:
3036:
3030:
3024:
3018:
3013:
3007:
3001:
2992:
2989:Manual testing
2986:
2980:
2971:
2965:
2959:
2957:Domain testing
2954:
2948:
2942:
2935:
2933:
2930:
2911:
2910:
2907:
2904:
2901:
2898:
2895:
2891:
2890:
2887:
2884:
2881:
2878:
2875:
2871:
2870:
2867:
2864:
2861:
2858:
2855:
2852:
2848:
2847:
2844:
2841:
2838:
2835:
2831:
2830:
2829:Time detected
2827:
2812:
2811:
2808:
2805:
2801:
2798:
2794:
2787:
2779:
2776:
2760:
2748:
2745:
2729:
2728:Certifications
2726:
2721:
2718:
2706:Main article:
2703:
2700:
2691:Main article:
2688:
2685:
2668:
2660:
2658:
2655:
2645:
2642:
2629:Main article:
2626:
2623:
2591:
2583:
2581:
2578:
2561:Main article:
2558:
2555:
2546:
2543:
2499:
2496:
2475:
2472:
2449:
2448:
2445:
2438:
2437:
2434:
2420:
2419:
2416:
2394:
2391:
2386:Main article:
2383:
2380:
2379:
2378:
2374:
2368:
2365:
2361:
2354:
2350:
2343:test scenarios
2339:
2324:
2309:
2308:Sample process
2306:
2275:
2272:
2246:
2243:
2238:
2235:
2188:
2185:
2183:
2180:
2167:
2164:
2155:Main article:
2152:
2149:
2125:
2122:
2112:
2109:
2100:Main article:
2097:
2094:
2082:Main article:
2079:
2076:
2067:Main article:
2064:
2061:
2041:Main article:
2038:
2035:
2034:
2033:
2024:and different
2014:
2011:
2004:
2001:
1998:CJK characters
1994:
1987:
1976:
1969:
1962:
1959:
1956:
1949:
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:
24:
14:
13:
10:
9:
6:
4:
3:
2:
7630:
7619:
7616:
7614:
7611:
7610:
7608:
7593:
7590:
7588:
7585:
7583:
7580:
7578:
7575:
7573:
7570:
7568:
7565:
7563:
7560:
7558:
7555:
7554:
7552:
7548:
7542:
7539:
7537:
7534:
7532:
7529:
7527:
7524:
7522:
7519:
7517:
7514:
7512:
7509:
7507:
7504:
7502:
7499:
7497:
7494:
7492:
7489:
7487:
7484:
7482:
7479:
7477:
7474:
7472:
7469:
7467:
7464:
7462:
7459:
7457:
7454:
7452:
7449:
7447:
7444:
7442:
7439:
7437:
7434:
7433:
7431:
7429:
7422:
7416:
7413:
7411:
7408:
7406:
7403:
7401:
7398:
7397:
7395:
7391:
7383:
7380:
7378:
7375:
7373:
7370:
7369:
7368:
7365:
7363:
7360:
7356:
7353:
7351:
7348:
7346:
7343:
7341:
7338:
7336:
7333:
7332:
7331:
7328:
7327:
7325:
7321:
7317:
7310:
7305:
7303:
7298:
7296:
7291:
7290:
7287:
7275:
7267:
7265:
7257:
7256:
7253:
7247:
7244:
7242:
7239:
7237:
7234:
7232:
7229:
7227:
7224:
7222:
7219:
7218:
7216:
7212:
7202:
7199:
7197:
7194:
7192:
7189:
7187:
7184:
7183:
7181:
7177:
7171:
7168:
7166:
7165:Systems model
7163:
7161:
7158:
7156:
7153:
7151:
7148:
7146:
7143:
7141:
7138:
7136:
7133:
7131:
7128:
7126:
7123:
7122:
7120:
7116:
7110:
7107:
7105:
7102:
7100:
7097:
7095:
7092:
7090:
7087:
7085:
7082:
7080:
7077:
7075:
7072:
7070:
7067:
7065:
7062:
7060:
7057:
7055:
7052:
7050:
7047:
7045:
7042:
7040:
7037:
7036:
7034:
7032:Developmental
7030:
7027:
7023:
7017:
7014:
7012:
7009:
7007:
7004:
7002:
6999:
6997:
6994:
6992:
6989:
6988:
6986:
6982:
6976:
6973:
6969:
6966:
6965:
6964:
6961:
6959:
6956:
6954:
6951:
6949:
6946:
6944:
6941:
6939:
6936:
6934:
6931:
6929:
6926:
6924:
6921:
6919:
6916:
6914:
6911:
6909:
6906:
6904:
6901:
6899:
6896:
6894:
6893:Data modeling
6891:
6887:
6884:
6882:
6879:
6877:
6874:
6872:
6869:
6867:
6864:
6863:
6862:
6859:
6857:
6854:
6852:
6849:
6848:
6846:
6842:
6836:
6833:
6831:
6828:
6826:
6823:
6821:
6818:
6816:
6813:
6811:
6808:
6806:
6803:
6801:
6798:
6796:
6793:
6791:
6788:
6786:
6783:
6781:
6778:
6776:
6773:
6771:
6768:
6767:
6765:
6761:
6757:
6750:
6745:
6743:
6738:
6736:
6731:
6730:
6727:
6715:
6707:
6705:
6697:
6695:
6687:
6686:
6683:
6677:
6674:
6672:
6669:
6667:
6664:
6662:
6659:
6657:
6654:
6652:
6649:
6647:
6644:
6642:
6639:
6637:
6634:
6632:
6629:
6627:
6624:
6622:
6619:
6617:
6614:
6612:
6609:
6607:
6604:
6602:
6599:
6597:
6594:
6592:
6589:
6587:
6584:
6582:
6579:
6578:
6576:
6572:
6566:
6563:
6561:
6558:
6556:
6553:
6551:
6550:Mixed reality
6548:
6546:
6543:
6541:
6538:
6536:
6533:
6531:
6528:
6527:
6525:
6523:
6519:
6513:
6510:
6508:
6505:
6503:
6500:
6498:
6495:
6493:
6490:
6489:
6487:
6485:
6481:
6475:
6472:
6470:
6467:
6465:
6462:
6460:
6457:
6455:
6452:
6450:
6447:
6445:
6442:
6440:
6437:
6436:
6434:
6432:
6428:
6422:
6419:
6417:
6414:
6412:
6409:
6407:
6404:
6402:
6399:
6398:
6396:
6394:
6390:
6384:
6383:Accessibility
6381:
6379:
6378:Visualization
6376:
6374:
6371:
6369:
6366:
6364:
6361:
6360:
6358:
6356:
6352:
6346:
6343:
6341:
6338:
6336:
6333:
6331:
6328:
6326:
6323:
6321:
6318:
6316:
6313:
6311:
6308:
6306:
6303:
6302:
6300:
6298:
6294:
6288:
6285:
6283:
6280:
6278:
6275:
6273:
6270:
6268:
6265:
6263:
6260:
6258:
6255:
6253:
6250:
6248:
6245:
6243:
6240:
6238:
6235:
6233:
6230:
6228:
6225:
6223:
6220:
6219:
6217:
6215:
6211:
6205:
6202:
6200:
6197:
6195:
6192:
6190:
6187:
6185:
6182:
6180:
6177:
6175:
6172:
6170:
6167:
6166:
6164:
6162:
6157:
6151:
6148:
6146:
6143:
6141:
6138:
6136:
6133:
6131:
6128:
6127:
6125:
6123:
6119:
6113:
6110:
6108:
6105:
6103:
6100:
6098:
6095:
6093:
6090:
6088:
6085:
6081:
6078:
6077:
6076:
6073:
6072:
6070:
6068:
6064:
6058:
6055:
6053:
6050:
6048:
6045:
6043:
6040:
6038:
6035:
6033:
6030:
6028:
6025:
6023:
6020:
6018:
6015:
6013:
6010:
6009:
6007:
6005:
6001:
5995:
5992:
5990:
5987:
5985:
5982:
5980:
5977:
5975:
5972:
5970:
5967:
5965:
5962:
5960:
5957:
5955:
5952:
5950:
5947:
5946:
5944:
5942:
5938:
5934:
5928:
5925:
5923:
5920:
5918:
5915:
5913:
5910:
5908:
5905:
5904:
5902:
5898:
5892:
5889:
5887:
5884:
5882:
5879:
5877:
5874:
5872:
5869:
5867:
5864:
5863:
5861:
5859:
5855:
5849:
5846:
5844:
5841:
5839:
5838:Dependability
5836:
5834:
5831:
5829:
5826:
5825:
5823:
5819:
5813:
5809:
5806:
5804:
5801:
5799:
5796:
5794:
5791:
5789:
5786:
5784:
5781:
5779:
5776:
5774:
5771:
5769:
5766:
5764:
5761:
5760:
5758:
5756:
5752:
5747:
5741:
5737:
5730:
5725:
5723:
5718:
5716:
5711:
5710:
5707:
5701:
5698:
5696:
5692:
5689:
5688:
5684:
5671:
5667:
5663:
5656:
5651:
5650:
5646:
5637:
5630:
5627:
5622:
5616:
5612:
5607:
5606:
5605:Code Complete
5597:
5594:
5578:
5571:
5570:
5565:
5559:
5556:
5540:
5533:
5529:
5523:
5520:
5515:
5511:
5504:
5501:
5496:
5492:
5488:
5482:
5479:
5475:
5471:
5467:
5461:
5458:
5453:
5449:
5445:
5438:
5435:
5430:
5426:
5422:
5416:
5412:
5408:
5404:
5397:
5394:
5389:
5385:
5378:
5375:
5370:
5366:
5362:
5360:9781450316149
5356:
5352:
5348:
5344:
5340:
5333:
5330:
5325:
5319:
5315:
5314:
5310:IEEE (1998).
5306:
5303:
5298:
5296:9781447122388
5292:
5288:
5284:
5280:
5276:
5269:
5267:
5263:
5250:
5243:
5240:
5235:
5234:
5226:
5223:
5210:
5206:
5200:
5197:
5184:
5180:
5174:
5172:
5168:
5163:
5157:
5153:
5152:
5144:
5141:
5128:
5124:
5118:
5115:
5110:
5104:
5100:
5093:
5090:
5085:
5081:
5076:
5071:
5067:
5063:
5059:
5055:
5051:
5045:
5042:
5037:
5033:
5029:
5023:
5019:
5015:
5011:
5007:
5000:
4997:
4984:
4980:
4974:
4971:
4958:
4957:
4949:
4946:
4933:
4929:
4922:
4919:
4903:
4902:
4894:
4891:
4879:
4875:
4868:
4865:
4852:
4848:
4841:
4838:
4825:
4818:
4815:
4799:
4793:
4790:
4777:
4770:
4767:
4751:
4747:
4740:
4734:
4732:
4730:
4726:
4721:
4715:
4711:
4710:
4702:
4699:
4694:
4688:
4684:
4680:
4673:
4670:
4665:
4659:
4655:
4654:
4646:
4644:
4642:
4638:
4626:
4620:
4616:
4612:
4611:
4603:
4600:
4595:
4593:9780471469124
4589:
4585:
4578:
4576:
4572:
4559:
4555:
4549:
4546:
4541:
4535:
4531:
4530:
4522:
4520:
4516:
4511:
4505:
4501:
4500:
4492:
4490:
4488:
4484:
4471:
4467:
4466:TEST Magazine
4463:
4456:
4453:
4437:
4436:
4428:
4425:
4420:
4414:
4410:
4409:
4401:
4398:
4386:
4380:
4376:
4375:
4367:
4365:
4361:
4356:
4350:
4346:
4345:
4337:
4334:
4321:
4317:
4310:
4307:(June 1999).
4306:
4300:
4297:
4285:
4278:
4277:
4269:
4266:
4261:
4255:
4251:
4250:
4242:
4239:
4151:
4145:
4142:
4137:
4131:
4127:
4126:
4118:
4116:
4112:
4099:
4092:
4090:
4086:
4081:
4075:
4071:
4064:
4061:
4056:
4050:
4046:
4045:
4037:
4035:
4033:
4029:
4024:
4018:
4014:
4013:
4005:
4003:
4001:
3999:
3995:
3990:
3984:
3980:
3979:
3971:
3969:
3967:
3965:
3961:
3956:
3950:
3946:
3942:
3938:
3937:
3929:
3926:
3921:
3915:
3911:
3907:
3903:
3902:
3894:
3891:
3886:
3882:
3878:
3874:
3870:
3863:
3860:
3856:
3855:
3851:
3848:
3841:
3838:
3834:
3830:
3827:
3824:Cem Kaner, "
3821:
3818:
3813:
3809:
3805:
3799:
3795:
3791:
3787:
3780:
3777:
3772:
3766:
3762:
3761:
3753:
3751:
3749:
3747:
3743:
3738:
3732:
3728:
3727:
3719:
3717:
3713:
3708:
3702:
3698:
3691:
3688:
3683:
3677:
3673:
3672:
3664:
3661:
3656:
3650:
3646:
3645:
3637:
3634:
3618:
3614:
3608:
3604:
3597:
3590:
3587:
3575:
3569:
3565:
3561:
3554:
3551:
3546:
3540:
3536:
3535:
3527:
3524:
3519:
3513:
3509:
3502:
3499:
3494:
3488:
3484:
3479:
3478:
3469:
3466:
3461:
3457:
3453:
3446:
3443:
3427:
3423:
3416:
3410:
3407:
3391:
3387:
3383:
3377:
3374:
3370:
3364:
3360:
3356:
3352:
3346:
3344:
3340:
3335:
3329:
3325:
3324:
3319:
3313:
3311:
3309:
3305:
3292:
3285:
3279:
3276:
3271:
3265:
3261:
3254:
3251:
3246:
3240:
3236:
3229:
3226:
3221:
3215:
3211:
3204:
3201:
3196:
3190:
3186:
3185:
3177:
3175:
3171:
3155:
3154:
3149:
3142:
3139:
3134:
3128:
3124:
3120:
3114:
3112:
3110:
3108:
3104:
3091:
3084:
3082:
3078:
3062:
3061:
3056:
3050:
3047:
3040:
3034:
3031:
3028:
3025:
3022:
3019:
3017:
3014:
3011:
3008:
3005:
3002:
2996:
2993:
2990:
2987:
2984:
2981:
2975:
2972:
2969:
2966:
2963:
2960:
2958:
2955:
2952:
2949:
2946:
2943:
2940:
2937:
2936:
2931:
2927:
2923:
2918:
2908:
2905:
2902:
2899:
2896:
2894:Construction
2893:
2892:
2888:
2885:
2882:
2879:
2876:
2874:Architecture
2873:
2872:
2868:
2865:
2862:
2859:
2856:
2854:Requirements
2853:
2849:
2846:Post-release
2845:
2842:
2840:Construction
2839:
2837:Architecture
2836:
2834:Requirements
2833:
2832:
2824:
2821:
2819:
2809:
2806:
2802:
2799:
2795:
2792:
2788:
2784:
2780:
2777:
2774:
2769:
2768:agile testing
2765:
2761:
2758:
2757:
2756:
2754:
2746:
2744:
2742:
2735:
2727:
2725:
2719:
2717:
2715:
2709:
2701:
2699:
2694:
2686:
2680:
2676:
2672:
2665:
2656:
2654:
2651:
2643:
2641:
2638:
2632:
2624:
2619:
2615:
2611:
2607:
2603:
2599:
2595:
2588:
2579:
2577:
2575:
2574:test strategy
2570:
2564:
2556:
2554:
2552:
2544:
2542:
2540:
2535:
2533:
2529:
2525:
2521:
2517:
2513:
2509:
2505:
2497:
2495:
2493:
2488:
2485:
2481:
2473:
2471:
2467:
2463:
2460:
2456:
2452:
2446:
2443:
2442:
2441:
2435:
2432:
2431:
2430:
2428:
2426:
2425:IEEE Standard
2417:
2414:
2413:
2412:
2410:
2404:
2400:
2392:
2389:
2381:
2375:
2372:
2369:
2366:
2362:
2359:
2355:
2351:
2348:
2344:
2340:
2337:
2333:
2329:
2328:Test strategy
2325:
2322:
2318:
2315:
2314:
2313:
2307:
2305:
2303:
2298:
2296:
2291:
2287:
2282:
2280:
2273:
2271:
2268:
2266:
2262:
2256:
2252:
2244:
2242:
2236:
2234:
2232:
2228:
2224:
2220:
2219:test designer
2216:
2212:
2208:
2203:
2201:
2196:
2194:
2186:
2181:
2179:
2177:
2172:
2165:
2163:
2158:
2150:
2148:
2146:
2141:
2137:
2131:
2123:
2121:
2118:
2110:
2108:
2103:
2095:
2093:
2091:
2085:
2077:
2075:
2070:
2062:
2060:
2058:
2054:
2049:
2044:
2036:
2031:
2027:
2023:
2019:
2015:
2012:
2009:
2005:
2002:
1999:
1995:
1992:
1988:
1985:
1981:
1977:
1974:
1970:
1967:
1963:
1960:
1957:
1954:
1950:
1947:
1946:
1945:
1942:
1939:
1937:
1933:
1925:
1923:
1919:
1917:
1913:
1909:
1902:
1897:
1894:(WAI) of the
1893:
1890:
1888:
1885:
1883:
1880:
1879:
1878:
1877:
1870:
1867:
1864:
1861:
1860:
1859:
1857:
1856:Accessibility
1850:
1848:
1846:
1841:
1834:
1832:
1830:
1826:
1822:
1820:
1815:
1813:
1809:
1808:
1803:
1802:
1797:
1793:
1789:
1785:
1784:
1779:
1774:
1766:
1763:
1759:
1754:
1752:
1748:
1744:
1740:
1733:
1725:
1723:
1721:
1717:
1713:
1707:
1699:
1697:
1695:
1691:
1687:
1683:
1679:
1675:
1672:
1665:
1663:
1661:
1657:
1653:
1649:
1648:beta versions
1645:
1639:
1631:
1629:
1623:Alpha testing
1622:
1620:
1616:
1612:
1610:
1606:
1602:
1597:
1593:
1589:
1584:
1578:
1575:
1572:
1569:
1568:
1567:
1564:
1561:
1557:
1549:
1547:
1544:
1538:
1535:
1531:
1525:
1517:
1515:
1513:
1509:
1508:Smoke testing
1505:
1503:
1498:
1490:
1488:
1486:
1482:
1478:
1474:
1470:
1466:
1462:
1458:
1454:
1450:
1446:
1442:
1438:
1437:compatibility
1432:
1424:
1417:
1414:
1411:
1408:
1407:
1406:
1404:
1395:
1386:
1384:
1381:
1380:, and so on.
1379:
1374:
1370:
1364:
1362:
1358:
1351:
1343:
1340:
1335:
1332:
1328:
1324:
1320:
1316:
1309:
1307:
1305:
1300:
1299:
1295:
1292:
1290:
1286:
1281:
1276:
1274:
1270:
1266:
1262:
1258:
1254:
1250:
1246:
1242:
1232:
1227:
1219:
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:
1094:
1092:
1085:
1083:
1076:
1071:
1067:
1063:
1057:
1048:
1046:
1044:
1040:
1034:
1032:
1028:
1023:
1022:environment.
1021:
1017:
1013:
1009:
1004:
1002:
998:
994:
990:
986:
978:
973:
969:
963:
954:
949:
945:
939:
930:
925:
921:
915:
906:
904:
902:
894:
889:
885:
880:
876:
869:
860:
858:
854:
849:
844:
842:
840:
839:combinatorics
835:
833:
829:
828:compatibility
825:
821:
817:
813:
809:
805:
801:
794:Code coverage
793:
791:
789:
785:
781:
777:
773:
769:
761:
759:
756:
754:
751:, changes in
750:
745:
743:
738:
736:
732:
728:
720:
718:
712:
710:
707:
703:
696:
694:
692:
688:
686:
678:
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:
38:
34:
33:
30:
19:
7577:Soak testing
7572:Pair testing
7415:Unit testing
7345:Fuzz testing
7315:
7160:Object model
7155:Metamodeling
7084:Spiral model
6984:Orientations
6829:
6646:Cyberwarfare
6305:Cryptography
5675:November 21,
5673:. Retrieved
5661:
5635:
5629:
5604:
5596:
5584:. Retrieved
5577:the original
5568:
5558:
5546:. Retrieved
5539:the original
5522:
5513:
5503:
5495:the original
5490:
5481:
5465:
5460:
5452:the original
5447:
5437:
5402:
5396:
5388:the original
5377:
5342:
5332:
5312:
5305:
5278:
5253:. Retrieved
5242:
5232:
5225:
5213:. Retrieved
5208:
5199:
5187:. Retrieved
5182:
5150:
5143:
5131:. Retrieved
5126:
5117:
5098:
5092:
5065:
5061:
5054:Hetzel, Bill
5044:
5009:
5006:"QuickCheck"
4999:
4987:. Retrieved
4983:the original
4973:
4961:. Retrieved
4955:
4948:
4936:. Retrieved
4931:
4921:
4909:. Retrieved
4900:
4893:
4881:. Retrieved
4877:
4867:
4855:. Retrieved
4850:
4840:
4828:. Retrieved
4817:
4805:. Retrieved
4792:
4780:. Retrieved
4769:
4757:. Retrieved
4745:
4708:
4701:
4682:
4672:
4652:
4630:November 29,
4628:. Retrieved
4609:
4602:
4583:
4564:December 10,
4562:. Retrieved
4558:the original
4548:
4528:
4498:
4474:. Retrieved
4470:the original
4465:
4455:
4443:. Retrieved
4434:
4427:
4407:
4400:
4388:. Retrieved
4373:
4343:
4336:
4324:. Retrieved
4322:(6): 113–114
4319:
4315:
4299:
4287:. Retrieved
4275:
4268:
4248:
4241:
4144:
4124:
4104:November 21,
4102:. Retrieved
4069:
4063:
4043:
4011:
3977:
3935:
3928:
3900:
3893:
3876:
3872:
3862:
3845:
3840:
3820:
3785:
3779:
3759:
3725:
3696:
3690:
3670:
3663:
3643:
3636:
3624:. Retrieved
3617:the original
3602:
3589:
3577:. Retrieved
3563:
3553:
3537:. Springer.
3533:
3526:
3507:
3501:
3476:
3468:
3451:
3445:
3435:December 15,
3433:. Retrieved
3426:the original
3409:
3399:December 15,
3397:. Retrieved
3390:the original
3376:
3350:
3322:
3297:December 19,
3295:. Retrieved
3278:
3259:
3253:
3234:
3228:
3209:
3203:
3183:
3161:. Retrieved
3152:
3141:
3122:
3096:November 21,
3094:. Retrieved
3070:November 22,
3068:. Retrieved
3059:
3049:
3004:Pair testing
2924:
2920:
2916:
2843:System test
2814:
2750:
2737:
2723:
2714:test harness
2711:
2708:Test harness
2702:Test harness
2696:
2693:Test fixture
2647:
2634:
2606:requirements
2566:
2548:
2536:
2512:ISO/IEC 9126
2501:
2489:
2477:
2468:
2464:
2461:
2457:
2453:
2450:
2439:
2423:
2421:
2406:
2311:
2302:unit testing
2299:
2290:unit testing
2283:
2277:
2269:
2258:
2240:
2230:
2226:
2222:
2218:
2215:test analyst
2214:
2210:
2207:test manager
2206:
2204:
2199:
2197:
2190:
2173:
2169:
2160:
2142:
2138:
2134:
2114:
2105:
2087:
2072:
2057:traceability
2050:
2046:
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:Private beta
7592:Web testing
7436:A/B testing
7372:API testing
6851:Abstraction
6656:Video games
6636:Digital art
6393:Concurrency
6262:Data mining
6174:Probability
5907:Interpreter
5586:January 18,
5548:October 13,
5487:"stop29119"
5133:January 13,
5127:etestinghub
4989:January 13,
4963:January 17,
4938:January 16,
4911:January 16,
4883:January 16,
4878:Stickyminds
4857:January 12,
4830:January 11,
4476:January 13,
4445:January 13,
4305:Bach, James
3844:Cem Kaner,
3560:"Chapter 5"
3262:. Manning.
3163:December 8,
3033:Web testing
3027:Trace table
2747:Controversy
2741:controversy
2650:test script
2644:Test script
2524:portability
2516:reliability
2504:correctness
2358:test effort
2166:VCR testing
2069:A/B testing
2063: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
7607:Categories
7170:View model
7135:Data model
6714:Glossaries
6586:E-commerce
6179:Statistics
6122:Algorithms
6080:Stochastic
5912:Middleware
5768:Peripheral
5638:. leanpub.
5564:Kaner, Cem
5528:Kaner, Cem
5255:August 13,
4807:January 9,
4782:January 9,
4390:January 5,
4326:August 19,
4289:January 2,
3579:January 2,
3293:. May 2002
3119:Kaner, Cem
3055:Kaner, Cem
3041:References
2797:withdrawn.
2679:test cases
2675:test suite
2664:Test suite
2657:Test suite
2618:test cases
2520:efficiency
2470:document.
2353:knowledge.
2347:test cases
2145:QuickCheck
1966: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
7441:Benchmark
7179:Languages
6535:Rendering
6530:Animation
6161:computing
6112:Semantics
5803:Processor
5514:InfoWorld
5448:CrossTalk
5215:March 17,
5189:March 17,
4759:April 11,
4152:function
2791:ISO 29119
2755:include:
2743:section.
2637:test case
2631:Test case
2625:Test case
2614:test plan
2569:test plan
2563:Test plan
2557:Test plan
2551:artifacts
2545:Artifacts
2532:usability
2377:projects.
2332:test plan
2237:Processes
2211: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
7550:See also
7274:Category
7140:ER model
7006:Ontology
6918:Software
6844:Concepts
6694:Category
6522:Graphics
6297:Security
5959:Compiler
5858:Networks
5755:Hardware
5662:Computer
5566:(2003).
5530:(2001).
5429:30322339
5084:14731341
4750:Archived
4316:Computer
3857:, p. 36.
3850:Archived
3829:Archived
3812:42596126
3626:July 13,
3320:(1979).
2932:See also
2889:25–100×
2869:10–100×
2720:Test run
2508:security
2498:Measures
2182:Teamwork
2030:currency
1973: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
7428:tactics
7264:Commons
7089:V-model
6704:Outline
5369:9072512
5036:5668071
2909:10–25×
2382:Quality
2336:testbed
2265:project
1953: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
7025:Models
6775:DevOps
6763:Fields
5695:Curlie
5617:
5472:
5427:
5417:
5367:
5357:
5320:
5293:
5158:
5105:
5082:
5034:
5024:
4716:
4689:
4660:
4621:
4590:
4536:
4506:
4415:
4381:
4351:
4256:
4173:return
4132:
4076:
4051:
4019:
3985:
3951:
3916:
3835:", p.2
3810:
3800:
3767:
3733:
3703:
3678:
3651:
3609:
3570:
3541:
3514:
3489:
3365:
3330:
3266:
3241:
3216:
3191:
3129:
2863:5–10×
2766:? The
2616:, and
2364:later.
2229:, and
2223: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
7201:SysML
7125:SPICE
7118:Other
7079:Scrum
7039:Agile
6991:Agile
6975:CI/CD
6107:Logic
5941:tools
5658:(PDF)
5580:(PDF)
5573:(PDF)
5542:(PDF)
5535:(PDF)
5425:S2CID
5365:S2CID
5080:S2CID
5032:S2CID
4905:(PDF)
4801:(PDF)
4753:(PDF)
4742:(PDF)
4439:(PDF)
4312:(PDF)
4280:(PDF)
4218:>=
3808:S2CID
3620:(PDF)
3599:(PDF)
3485:–43.
3429:(PDF)
3418:(PDF)
3393:(pdf)
3287:(PDF)
3157:(PDF)
3064:(PDF)
2187: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
7426:and
7186:IDEF
7130:CMMI
7016:SDLC
5939:and
5812:Form
5808:Size
5677:2017
5615:ISBN
5588:2018
5550:2006
5470:ISBN
5415:ISBN
5355:ISBN
5318:ISBN
5291:ISBN
5257:2008
5217:2018
5191:2018
5156:ISBN
5135:2012
5103:ISBN
5022:ISBN
4991:2012
4965:2018
4940:2018
4913:2018
4885:2018
4859:2018
4832:2018
4809:2018
4784:2018
4761:2022
4714:ISBN
4687:ISBN
4658:ISBN
4632:2017
4619:ISBN
4588:ISBN
4566:2012
4534:ISBN
4504:ISBN
4478:2012
4447:2012
4413:ISBN
4392:2018
4379:ISBN
4349:ISBN
4328:2008
4291:2018
4254:ISBN
4130:ISBN
4106:2017
4074:ISBN
4049:ISBN
4017:ISBN
3983:ISBN
3949:ISBN
3914:ISBN
3798:ISBN
3765:ISBN
3731:ISBN
3701:ISBN
3676:ISBN
3649:ISBN
3628:2018
3607:ISBN
3581:2018
3568:ISBN
3539:ISBN
3512:ISBN
3487:ISBN
3437:2017
3401:2017
3363:ISBN
3328:ISBN
3299:2017
3264:ISBN
3239:ISBN
3214:ISBN
3189:ISBN
3165:2017
3127:ISBN
3098:2017
3072:2014
2906:10Ă—
2886:15Ă—
2883:10Ă—
2866:10Ă—
2673:, a
2596:, a
2510:and
2401:and
2253:and
2028:and
2020: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
7196:USL
7191:UML
7069:RAD
7044:EUP
5693:at
5666:doi
5407:doi
5347:doi
5283:doi
5070:doi
5014:doi
4164:int
4155:int
3941:doi
3906:doi
3881:doi
3790:doi
3456:doi
3355:doi
2903:1Ă—
2880:1Ă—
2860:3Ă—
2857:1Ă—
2669:In
2592:In
2259:In
2176: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
7609::
7099:XP
7074:UP
5810:/
5660:.
5613:.
5611:29
5512:.
5489:.
5446:.
5423:.
5413:.
5363:.
5353:.
5341:.
5289:.
5265:^
5207:.
5181:.
5170:^
5125:.
5078:.
5066:31
5064:.
5060:.
5052:;
5030:.
5020:.
5008:.
4930:.
4876:.
4849:.
4748:.
4744:.
4728:^
4640:^
4613:.
4574:^
4518:^
4486:^
4464:.
4363:^
4320:32
4318:.
4314:.
4200:;}
4185:-6
4170:){
4114:^
4088:^
4031:^
3997:^
3963:^
3947:.
3912:.
3877:84
3875:.
3871:.
3806:.
3796:.
3745:^
3715:^
3601:.
3562:.
3483:31
3420:.
3384:.
3361:,
3342:^
3307:^
3289:.
3173:^
3106:^
3080:^
2900:–
2897:–
2877:–
2775:).
2716:.
2648:A
2635:A
2567:A
2534:.
2526:,
2522:,
2518:,
2429::
2411::
2345:,
2334:,
2330:,
2304:.
2233:.
2225:,
2221:,
2217:,
2213:,
2209:,
2178:.
2147:.
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
7308:e
7301:t
7294:v
6748:e
6741:t
6734:v
5748:.
5728:e
5721:t
5714:v
5679:.
5668::
5623:.
5590:.
5552:.
5516:.
5476:.
5431:.
5409::
5371:.
5349::
5326:.
5299:.
5285::
5259:.
5236:.
5219:.
5193:.
5164:.
5137:.
5111:.
5086:.
5072::
5038:.
5016::
4993:.
4967:.
4942:.
4915:.
4887:.
4861:.
4834:.
4811:.
4786:.
4763:.
4722:.
4695:.
4666:.
4634:.
4596:.
4568:.
4542:.
4512:.
4480:.
4449:.
4421:.
4394:.
4357:.
4330:.
4293:.
4262:.
4233:3
4230:=
4227:x
4221:0
4215:)
4212:x
4209:(
4206:f
4197:8
4194:+
4191:x
4188:*
4182:x
4179:*
4176:x
4167:x
4161:(
4158:f
4150:C
4138:.
4108:.
4082:.
4057:.
4025:.
3991:.
3957:.
3943::
3922:.
3908::
3887:.
3883::
3814:.
3792::
3773:.
3739:.
3709:.
3684:.
3657:.
3630:.
3583:.
3547:.
3520:.
3495:.
3462:.
3458::
3439:.
3403:.
3357::
3336:.
3301:.
3272:.
3247:.
3222:.
3197:.
3167:.
3135:.
3100:.
3074:.
2666:.
2620:.
2589:.
2132:.
2032:.
2010:.
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.