Software testing

From Wikipedia, the free encyclopedia Jump to: navigation, search

Software development process
Activities and steps Requirements ·Specification Architecture ·Design Implementation ·Testing Deployment ·Maintenance Methodologies Agile ·Cleanroom ·Iterative RAD ·RUP ·Spiral Waterfall ·XP ·Lean Scrum ·V-Model ·TDD Supporting disciplines Configuration management Documentation Quality assurance (SQA) Project management User experience design Tools Compiler ·Debugger ·Profiler GUI designer ·IDE v·d·e

Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test.[1] Software testing also provides an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs. Software testing can also be stated as the process of validating and verifying that a software program/application/product: 1. meets the business and technical requirements that guided its design and development; 2. works as expected; and 3. can be implemented with the same characteristics. Software testing, depending on the testing method employed, can be implemented at any time in the development process. However, most of the test effort occurs after the requirements have

been defined and the coding process has been completed. As such, the methodology of the test is governed by the software development methodology adopted. Different software development models will focus the test effort at different points in the development process. Newer development models, such as Agile, often employ test driven development and place an increased portion of the testing in the hands of the developer, before it reaches a formal team of testers. In a more traditional model, most of the test execution occurs after the requirements have been defined and the coding process has been completed.

• • •

1 Overview 2 History 3 Software testing topics
○ ○ ○ ○ ○ ○ ○ ○ ○ ○

3.1 Scope 3.2 Functional vs non-functional testing 3.3 Defects and failures 3.4 Finding faults early 3.5 Compatibility 3.6 Input combinations and preconditions 3.7 Static vs. dynamic testing 3.8 Software verification and validation 3.9 The software testing team 3.10 Software quality assurance (SQA) 4.1 The box approach
  

4 Testing methods

4.1.1 White box testing 4.1.2 Black box testing 4.1.3 Grey box testing

5 Testing levels

5.1 Test target
   

5.1.1 Unit testing 5.1.2 Integration testing 5.1.3 System testing 5.1.4 System integration testing 5.2.1 Regression testing

5.2 Objectives of testing

   • ○ ○ ○ ○ ○ ○ • ○ ○ ○ • ○ ○ • • • • • •

5.2.2 Acceptance testing 5.2.3 Alpha testing 5.2.4 Beta testing

6 Non-functional testing 6.1 Software performance testing and load testing 6.2 Stability testing 6.3 Usability testing 6.4 Security testing 6.5 Internationalization and localization 6.6 Destructive testing 7.1 Traditional CMMI or waterfall development model 7.2 Agile or Extreme development model 7.3 A sample testing cycle 8.1 Testing tools 8.2 Measurement in software testing

7 The testing process

8 Automated testing

9 Testing artifacts 10 Certifications 11 Controversy 12 See also 13 References 14 External links

[edit] Overview
Testing can never completely identify all the defects within software. Instead, it furnishes a criticism or comparison that compares the state and behavior of the product against oracles— principles or mechanisms by which someone might recognize a problem. These oracles may include (but are not limited to) specifications, contracts,[2] comparable products, past versions of the same product, inferences about intended or expected purpose, user or customer expectations, relevant standards, applicable laws, or other criteria. Every software product has a target audience. For example, the audience for video game software is completely different from banking software. Therefore, when an organization develops or otherwise invests in a software product, it can assess whether the software product will be acceptable to its end users, its target audience, its purchasers, and other stakeholders. Software testing is the process of attempting to make this assessment.

a testing organization may be separate from the development team. bug) in the software source code. Software faults occur through the following processes. Dave Gelperin and William C. causing a failure.A study conducted by NIST in 2002 reports that software bugs cost the U.Demonstration oriented[8] 1979–1982 . More than a third of this cost could be avoided if better software testing was performed.Evaluation oriented[10] 1988–2000 . Myers in 1979. e. that result in errors of omission by the program designer. although some development methodologies work from use cases or user stories. performance. such as debugging. [edit] Defects and failures Not all software defects are caused by coding errors.g.. unrecognized requirements. Functional tests tend to answer the question of "can the user do this" or "does this particular feature work".5 billion annually. scalability.[12] The scope of software testing often includes examination of code as well as execution of that code in various environments and conditions as well as examining the aspects of code: does it do what it is supposed to do and do what it needs to do. A programmer makes an error (mistake). from that of verification. usability.[13] [edit] Functional vs non-functional testing Functional testing refers to activities that verify a specific action or function of the code.[14] A common source of requirements gaps is non-functional requirements such as testability. maintainability. These are usually found in the code requirements documentation. and security.S. which results in a defect (fault. such as scalability or security.[15] Not all defects will . Non-functional testing tends to answer such questions as "how many people can log in at once".Destruction oriented[9] 1983–1987 . There are various roles for testing team members. economy $59. In the current culture of software development. Information derived from software testing may be used to correct the process by which software is developed. Testing cannot establish that a product functions properly under all conditions but can only establish that it does not function properly under specific conditions.Debugging oriented[7] 1957–1978 . Non-functional testing refers to aspects of the software that may not be related to a specific function or user action. Hetzel classified in 1988 the phases and goals in software testing in the following stages:[6] • • • • • Until 1956 . If this defect is executed. This is a non-trivial pursuit.[3] [edit] History The separation of debugging from testing was initially introduced by Glenford J.Prevention oriented[11] [edit] Software testing topics [edit] Scope A primary purpose of testing is to detect software failures so that defects may be discovered and corrected. [4] Although his attention was on breakage testing ("a successful test is one that finds a bug"[4][5]) it illustrated the desire of the software engineering community to separate fundamental development activities. One common source of expensive defects is caused by requirement gaps. in certain situations the system will produce wrong results.

if a problem in the requirements is found only post-release. something that constitutes sufficient value to one person may be intolerable to another. then it would cost 10–100 times more to fix than if it had already been found by the requirements review. Static testing can be (and unfortunately in practice often is) omitted. in the case of a lack of backward compatibility. this can occur because the programmers develop and test software only on the latest version of the target environment. or inspections are considered as static testing. operating systems (or operating system versions. defects in dead code will never result in failures. Reviews. or target environments that differ greatly from the original (such as a terminal or GUI application intended to be run on the desktop now being required to become a web application. Sometimes such issues can be fixed by proactively abstracting operating system functionality into a separate program module or library.[16] The following table shows the cost of fixing the defect depending on the stage it was found. Dynamic testing may begin before the program is 100% complete in order to test particular sections of code (modules or discrete functions). [edit] Input combinations and preconditions A very fundamental problem with software testing is that testing under all combinations of inputs and preconditions (initial state) is not feasible. [edit] Static vs. even with a simple product. compatibility. Dynamic testing takes place when the program itself is used for the first time (which is generally considered the beginning of the testing stage). whereas actually executing programmed code with a given set of test cases is referred to as dynamic testing. scalability.[12][18] This means that the number of defects in a software product can be very large and defects that occur infrequently are difficult to find in testing. non-functional dimensions of quality (how it is supposed to be versus what it is supposed to do)—usability.[17][not in citation given] For example. [edit] Finding faults early It is commonly believed that the earlier a defect is found the cheaper it is to fix it. reliability—can be highly subjective. or on older hardware that earlier versions of the target environment was capable of using. dynamic testing There are many approaches to software testing. Typical techniques for this are either using stubs/drivers or execution from a . More significantly. which must render in a web browser). Time detected Cost to fix a defect Time introduced Requirements Architecture Construction Requirements Architecture Construction 1× 3× 1× 5–10× 10× 1× System test 10× 15× 10× Postrelease 10–100× 25–100× 10–25× [edit] Compatibility A common cause of software failure (real or perceived) is a lack of compatibility with other application software. For example. which not all users may be running. For example. This results in the unintended consequence that the latest work may not function on earlier versions of the target environment. performance. old or new). walkthroughs. Examples of these changes in environment include the software being run on a new hardware platform.[15] A single defect may result in a wide range of failure symptoms. alterations in source data or interacting with different software. A defect can turn into a failure when the environment is changed.necessarily result in failures.

Although there are close links with SQA. software process specialists and auditors are concerned for the software development process rather than just the artefacts such as documentation. spreadsheet programs are. QA (quality assurance) is the implementation of policies and procedures intended to prevent defects from occurring in the first place. A flight simulator video game would have much higher defect tolerance than software for an actual airplane. [edit] The software testing team Software testing can be done by software testers. [edit] Software quality assurance (SQA) Though controversial. it is also common to see these two terms incorrectly defined. [edit] Testing methods [edit] The box approach Software testing methods are traditionally divided into white. Software testing is a task intended to detect defects in software by contrasting a computer program's expected results with its actual results for a given set of inputs. By contrast.debugger environment. tested to a large extent interactively ("on the fly"). The terms verification and validation are commonly used interchangeably in the industry.. According to the IEEE Standard Glossary of Software Engineering Terminology: 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.e. and there may be no SQA function in some companies. They examine and change the software engineering process itself to reduce the amount of faults that end up in the delivered software: the so-called defect rate. Regarding the periods and the different goals in software testing. [edit] Software verification and validation Software testing is used in association with verification and validation:[19] • • Verification: Have we built the software right? (i.[20] different roles have been established: manager.. testing departments often exist independently. is this what the customer wants). Until the 1980s the term "software tester" was used generally. but later it was also seen as a separate profession.e. test lead. tester. [12] In SQA. Validation: Have we built the right software? (i. software testing is a part of the software quality assurance (SQA) process. [edit] White box testing . 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. test designer. What constitutes an "acceptable defect rate" depends on the nature of the software. does it match the specification). code and systems. For example. with results displayed immediately after each calculation or text manipulation. and test administrator. These two approaches are used to describe the point of view that a test engineer takes when designing test cases. by their very nature.and black-box testing. automation developer.

Specification-based testing: Specification-based testing aims to test the functionality of software according to the applicable requirements. the test object. measured as a percentage. Specification-based testing is necessary. and only sees the output from. Using the principle. the tester inputs data into. model-based testing. Black box testing methods include: equivalence partitioning. boundary value analysis." black box testers find bugs where programmers do not. the test designer can create tests to cause all statements in the program to be executed at least once) Fault injection methods . and a tester's perception is very simple: a code must have bugs.testing of the application using public and private APIs Code coverage . [edit] Black box testing Main article: Black box testing Black box testing treats the software as a "black box"—without any knowledge of internal implementation. "Ask and you shall receive. either "is" or "is not" the same as the expected value specified in the test case. which reports on the number of lines executed to complete the test They both return a code coveragemetric." because the tester doesn't know how the software being tested was actually . This level of testing usually requires thorough test cases to be provided to the tester. fuzz testing.[21] Two common forms of code coverage are: • • Function coverage. who then can simply verify that for a given input. black box testing has been said to be "like a walk in a dark labyrinth without a flashlight. but it is insufficient to guard against certain risks.improving the coverage of a test by introducing faults to test code paths Mutation testing methods Static testing . the output value (or behavior).White box testing includes all static testing • • • Test coverage White box testing methods can also be used to evaluate the completeness of a test suite that was created with black box testing methods. Types of white box testing The following types of white box testing exist: • • API testing (application programming interface) . all-pairs testing. On the other hand.g.[22] Thus.Main article: White box testing White box testing is when the tester has access to the internal data structures and algorithms including the code that implement these.[23] Advantages and disadvantages: The black box tester has no "bonds" with the code. which reports on functions executed Statement coverage. This allows the software team to examine parts of a system that are rarely tested and ensures that the most important function points have been tested.. exploratory testing and specificationbased testing.creating tests to satisfy some criteria of code coverage (e.

Software components may be integrated in an iterative way or all together ("big bang"). but rather is used to assure that the building blocks the software uses work independently of each other. on the one hand. usually at the function level. or by the level of specificity of the test. Unit testing is also called component testing. for instance. boundary values or error messages.[27] These type of tests are usually written by developers as they work on code (white-box style). or black-box level. This distinction is particularly important when conducting integration testing between two modules of code written by two different developers. In an object-oriented environment. Therefore. where only the interfaces are exposed for test. modifying a data repository does qualify as grey box. on the other. One function might have multiple tests. Integration testing works to expose defects in the interfaces and interaction between integrated components (modules). and the minimal unit tests include the constructors and destructors. and system testing that are distinguished by the test target without impliying a specific process model. there are situations when (1) a tester writes many test cases to check something that could have been tested by only one test case. The main levels during the development process as defined by the SWEBOK guide are unit-. because the input and output are clearly outside of the "black-box" that we are calling the system under test. [24] [edit] Grey box testing Grey box testing (American spelling: gray box testing) involves having knowledge of internal data structures and algorithms for purposes of designing the test cases. However. this is usually at the class level.[26] [edit] Test target [edit] Unit testing Main article: Unit testing Unit testing refers to tests that verify the functionality of a specific section of code. Manipulating input data and formatting output do not qualify as grey box. black box testing has the advantage of "an unaffiliated opinion". Grey box testing may also include reverse engineering to determine. to ensure that the specific function is working as expected. [edit] Testing levels Tests are frequently grouped by where they are added in the software development process. [edit] Integration testing Main article: Integration testing Integration testing is any type of software testing that seeks to verify the interfaces between components against a software design. but testing at the user. Normally the former is considered a better practice since it allows interface issues to be localised more quickly and fixed. Unit testing alone cannot verify the functionality of a piece of software. integration-.[25] Other test levels are classified by the testing objective. As a result. Progressively larger groups of tested software components . as the user would not normally be able to change the data outside of the system under test.constructed. and/or (2) some parts of the back-end are not tested at all. and the disadvantage of "blind exploring". to catch corner cases or other branches in the code.

Typically.[citation needed] [edit] Objectives of testing [edit] Regression testing Main article: Regression testing Regression testing focuses on finding defects after a major code change has occurred. Acceptance testing is performed by the customer. They can either be complete. Specifically. known as beta versions. [edit] Acceptance testing Main article: Acceptance testing Acceptance testing can mean one of two things: 1. to very shallow. or old bugs that have come back. i. it seeks to uncover software regressions. consisting of positive tests on each feature. Common methods of regression testing include re-running previously run tests and checking whether previously fixed faults have re-emerged. before integration or regression. Sometimes. Acceptance testing may be performed as part of the hand-off process between any two phases of development. when the newly developed part of the software collides with the previously existing code. often in their lab environment on their own hardware. regressions occur as an unintended consequence of program changes.[30] [edit] Beta testing Beta testing comes after alpha testing and can be considered a form of external user acceptance testing. before the software goes to beta testing. are released to a limited audience outside of the programming team. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing.corresponding to elements of the architectural design are integrated and tested until the software works as a system. is known as user acceptance testing (UAT). if the changes are early in the release or deemed to be of low risk.[29] [edit] System integration testing Main article: System integration testing System integration testing verifies that a system is integrated to any external or third-party systems defined in the system requirements. Versions of the software. 2.[citation needed] [edit] Alpha testing Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers' site. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Such regressions occur whenever software functionality that was previously working correctly stops working as intended. for changes added late in the release or deemed to be risky. beta versions are made . The depth of testing depends on the phase in the release process and the risk of the added features. A smoke test is used as an acceptance test prior to introducing a new build to the main testing process.[28] [edit] System testing Main article: System testing System testing tests a completely integrated system to verify that it meets its requirements.e.

performance testing. [edit] Internationalization and localization The general ability of software to be internationalized and localized can be automatically tested without actual translation. reliability and resource usage. Load testing is a way to test performance. there are also numerous open-source and free software tools available that perform non-functional testing. [edit] Usability testing Usability testing is needed to check if the user interface is easy to use and understand. The terms load testing. are often used interchangeably. [edit] Security testing Security testing is essential for software that processes confidential data to prevent system intrusion by hackers. It will verify that the application still works. [citation needed] [edit] Non-functional testing Special methods exist to test non-functional aspects of software. Load testing is primarily concerned with testing that can continue to operate under a specific load. Stress testing is a way to test reliability. is designed to establish whether the device under test can tolerate invalid or unexpected inputs.available to the open public to increase the feedback field to a maximal number of future users. which establishes the correct operation of the software (correct in that it matches the expected behavior defined in the design requirements). This is generally referred to as software scalability. in the form of fuzzing. This activity of non-functional software testing is often referred to as load (or endurance) testing. reliability testing. especially for software. by using pseudolocalization. Various commercial non-functional testing tools are linked from the software fault injection page. even after it has been translated into a new language or adapted for a new culture (such as different currencies or time zones). [edit] Stability testing Stability testing checks to see if the software can continuously function well in or above an acceptable period. The related load testing activity of when performed as a non-functional activity is often referred to as endurance testing. There is little agreement on what the specific goals of load testing are. [edit] Software performance testing and load testing Performance testing is executed to determine how fast a system or sub-system performs under a particular workload. too. It can also serve to validate and verify other quality attributes of the system. Non-functional testing. Possible localization failures include: . In contrast to functional testing. is an example of non-functional testing. thereby establishing the robustness of input validation routines as well as error-handling routines. non-functional testing verifies that the software functions properly even when it receives invalid or unexpected inputs. Volume testing is a way to test functionality. and volume testing. Software fault injection.[31] Actual translation to human languages must be tested. whether that be large quantities of data or a large number of users. such as scalability.It approach towards the use of the application.

• • • • To avoid these and other localization problems. Software may lack support for the character encoding of the target language. [edit] The testing process [edit] Traditional CMMI or waterfall development model A common practice of software testing is that testing is performed by an independent group of testers after the functionality is developed.[32] This practice often results in the testing phase being used as a project buffer to compensate for project delays. thereby compromising the time devoted to testing. This may make the string partly invisible to the user or cause the software to fail.[33] Another practice is to start software testing at the same moment the project starts and it is a continuous process until the project finishes. Some messages may be created automatically in run time and the resulting string may be ungrammatical. Fonts and font sizes which are appropriate in the source language. Literal word-for-word translations may sound inappropriate. Untranslated messages in the original language may be left hard coded in the source code. before it is shipped to the customer. but is used for typing characters in the layout of the target language. for example. functionally incorrect. If several people translate strings. A string in the target language may be longer than the software can handle. artificial or too technical in the target language. Software may display images with text that wasn't localized. Localized operating systems may have differently-named system configuration files and environment variables and different formats for date and currency.[34] Further information: Capability Maturity Model Integration and Waterfall model [edit] Agile or Extreme development model . Software may use a keyboard shortcut which has no function on the source language's keyboard layout. translated correctly in context and don't cause failures. and the translator may choose the wrong translation for an ambiguous source string. CJK characters may become unreadable if the font is too small. may be inappropriate in the target language. [edit] Destructive testing Main article: Destructive testing Destructive testing attempts to cause the software or a sub-system to fail. a tester who knows the target language must run the program with all the possible use cases for translation to see if the messages are readable. technical terminology may become inconsistent. misleading or confusing.• • • • • • • • Software is often localized by translating a list of strings out of context. in order to test its robustness. Software may lack proper support for reading or writing bi-directional text.

Test development: Test procedures.[37] The sample below is common among organizations employing the Waterfall development model. Of course these tests fail initially. found software working properly) or deferred to be dealt with later.In counterpoint. is done by the development team usually along with the client.e. and that the software product as a whole is still working correctly. testers generate metrics and make final reports on their test effort and whether or not the software tested is ready for release. [35][36] [edit] A sample testing cycle Although variations exist between organizations. testbed creation. There are many frameworks to write tests in. test scenarios. there is a typical cycle for testing. Test Closure: Once the test meets the exit criteria. as they are expected to. adhere to a "test-driven software development" model. results. lessons learned. logs. Then as code is written it passes incrementally larger portions of the test suites. testers work with developers in determining what aspects of a design are testable and with what parameters those tests work. and continuous . for each integration of new. AKA Resolution testing. by the software engineers (often with pair programming in the extreme programming methodology). unit tests are written first. rejected (i. test datasets. Test execution: Testers execute the software based on the plans and test documents then report any errors found to the development team. documents related to the project are archived and used as a reference for future projects. a plan is needed. Test planning: Test strategy. test scripts to use in testing software. Test reporting: Once testing is completed. In this process. Test result analysis: Or Defect Analysis. Unit tests are maintained along with the rest of the software source code and generally integrated into the build process (with inherently interactive tests being relegated to a partially manual build acceptance process). some emerging software disciplines such as extreme programming and the agile software development movement. especially groups that use test-driven development. • Requirements analysis: Testing should begin in the requirements phase of the software development life cycle. and they are integrated with any regression tests that are developed. or fixed software. Regression testing: It is common to have a small test program built of a subset of tests. modified. in order to decide what defects should be treated. During the design phase. it is retested by the testing team. the activities such as capturing the key outputs. test plan. The test suites are continuously updated as new failure conditions and corner cases are discovered. in order to ensure that the latest delivery has not ruined anything. The ultimate goal of this test process is to achieve continuous deployment where software updates can be published to the public frequently. fixed. test cases. Since many activities will be carried out during testing. • • • • • • • • [edit] Automated testing Main article: Test automation Many programming groups are relying more and more on automated testing. Defect Retesting: Once a defect has been dealt with by the development team.

While automation cannot reproduce everything that a human can do (and all the ways they think of doing it). completeness. portability. tools allowing inspection of program variables on error or at chosen points Automated functional GUI testing tools are used to repeat system-level tests through the GUI Benchmarks. However. which are used to assist in determining the state of the software or the adequacy of the testing. such as capability. [edit] Testing artifacts Software testing process can produce several artifacts. permitting full or partial monitoring of program code including: ○ ○ ○ • Instruction set simulator. reliability. often called metrics. Differences detected indicate unexpected functionality changes or "regression". which cover existing functionality that result in persistent tabular data. [edit] Testing tools Program testing and fault detection can be aided significantly by testing tools and debuggers. allowing run-time performance comparisons to be made Performance analysis (or profiling tools) that can help to highlight hot spots and resource usage A regression testing technique is to have a standard set of tests. permitting complete instruction level monitoring and trace facilities Program animation. where there should not be differences. it does require a welldeveloped test suite of testing scripts in order to be truly useful. maintainability. and to compare pre-change data to postchange data.[citation needed] but can also include more technical requirements as described under the ISO standard ISO/IEC 9126. compatibility. Testing/debug tools include features such as: • Program monitors. permitting step-by-step execution and conditional breakpoint at source level or in machine code Code coverage reports Formatted dump or symbolic debugging. • • • Some of these features may be incorporated into an Integrated Development Environment (IDE).integration software will run tests automatically every time code is checked into a version control system. it can be very useful for regression testing. • [edit] Measurement in software testing Usually. security. efficiency. The idea is to make them more cautious when developing their code or . and usability. There are a number of frequently-used software measures. Test plan A test specification is called a test plan. using a tool like diffkit. The developers are well aware what test plans will be executed and this information is made available to management and the developers. quality is constrained to such topics as correctness.

or other common repository. Test case A test case normally consists of a unique identifier. Test harness The software. No certification is based on a widely accepted body of knowledge. whereas other test cases described in more detail the input scenario and what results might be expected. requirement references from a design specification. samples of data input and output. and descriptions of the following tests. who generated the results. In a database system. and actual result. Clinically defined a test case is an input and an expected result.making additional changes. This has led some to declare that the testing field is not ready for certification. a series of steps (also known as actions) to follow. preconditions. It is used to change tests when the source documents are changed. Today. Test data In most cases. The test suite often also contains more detailed instructions or goals for each collection of test cases. database. Test suite The most common term for a collection of test cases is a test suite. test procedure. tools. It definitely contains a section where the tester identifies the system configuration used during testing. author. or a combination of both. All the test values and changeable environmental components are collected in separate files and stored as test data. spreadsheet. automated. and descriptions. test scripts can be manual. test step. A test case should also contain a place for the actual result. These steps can be stored in a word processor document. and what system configuration was used to generate those results. you may also be able to see past test results. Some companies have a higher-level document called a test strategy. output. or order of execution number. depth. Traceability matrix A traceability matrix is a table that correlates requirements or design documents to test documents. and configurations are all referred to collectively as a test harness. The optional fields are a test case ID.[38] This can be as pragmatic as 'for condition x your derived result is y'. Test script The test script is the combination of a test case. multiple sets of values or data are used to test the same functionality of a particular feature. 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. Larger test cases may also contain prerequisite states or steps. A group of test cases may also contain prerequisite states or steps. and check boxes for whether the test is automatable and has been automated. Initially the term was derived from the product of work created by automated regression test tools. test category. related requirement(s). and test data. These past results would usually be stored in a separate table. [edit] Certifications Several certification programs exist to support the professional aspirations of software testers and quality assurance specialists. No certification currently offered actually requires the applicant to demonstrate the ability to test software.[39] . input. as a matter of economy) but with one expected result or expected outcome. expected result. or to verify that the test results are correct. It is also useful to provide this data to the client and with the product or a project. events.

[40] Software testing certification types • • Exam-based: Formalized exams. Ross & Associates[44] ISEB offered by the Information Systems Examinations Board ISTQB Certified Tester. traditional . and cannot guarantee their competence. J. but rather that testing is a set of skills that allow the tester to select or invent testing practices to suit each unique situation..Certification itself cannot measure an individual's productivity..[50] Agile vs. Certified Associate in Software Testing (CAST) offered by the Quality Assurance Institute (QAI)[42] CATe offered by the International Institute for Software Testing[43] Certified Manager in Software Testing (CMST) offered by the Quality Assurance Institute (QAI)[42] Certified Software Tester (CSTE) offered by the Quality Assurance Institute (QAI)[42] Certified Software Test Professional (CSTP) offered by the International Institute for Software Testing[43] CSTP (TM) (Australian Version) offered by K. their skill. where each course has to be passed [e. or practical knowledge. Advanced Level (CTAL) offered by the International Software Testing Qualification Board[45][46] TMPF TMap Next Foundation offered by the Examination Institute for Information Science[47] TMPA TMap Next Advanced offered by the Examination Institute for Information Science[47] CMSQ offered by the Quality Assurance Institute (QAI).g. or professionalism as a tester. Foundation Level (CTFL) offered by the International Software Testing Qualification Board[45][46] ISTQB Certified Tester.g. for ISTQB or QAI][41] Education-based: Instructor-led sessions. International Institute for Software Testing (IIST)]. can also be learned by self-study [e. which need to be passed.[42] CSQA offered by the Quality Assurance Institute (QAI)[42] CSQE offered by the American Society for Quality (ASQ)[48] CQIA offered by the American Society for Quality (ASQ)[48] Testing certifications • • • • • • • • • • • Quality assurance certifications • • • • [edit] Controversy Some of the major software testing controversies include: What constitutes responsible software testing? Members of the "context-driven" school of testing[49] believe that there are no "best practices" of testing.

Should testers learn to work under conditions of uncertainty and constant change or should they aim at process "maturity"? The agile testing movement has received growing popularity since 2006 mainly in commercial circles. ^Exploratory Testing. Cem Kaner. automated Some writers believe that test automation is so expensive relative to its value that it should be used sparingly. Orlando. in the Waterfall model). The tests then can be considered as a way to capture and implement the requirements. Quality Assurance Institute Worldwide Annual Software Testing Conference. Software design vs.[55] More in particular.[citation needed] Exploratory test vs. Florida Institute of Technology.g.[51][52] whereas government and military[53] software providers use this methodology but also the traditional test-last models (e. test-driven development states that developers should write unit-tests of the XUnit type before coding the functionality. software implementation[56] Should testing be carried out only at the end or throughout the whole process? Who watches the watchmen? The idea is that any form of observation is also an interaction—the act of testing can also affect that which is being tested. scripted[54] Should tests be designed at the same time as they are executed or should they be designed beforehand? Manual testing vs. FL.[57] [edit] See also Software Testing portal Book: Software testing Wikipedia Books are collections of articles that can be downloaded or ordered in print. • • • • • • • • • • • • • Acceptance testing All-pairs testing Automated testing Dynamic program analysis Formal verification GUI software testing Manual testing Orthogonal array testing Pair Testing Reverse semantic traceability Software testability Static code analysis Web testing [edit] References 1. November 2006 .

Automated Defect Prevention: Best Practices in Software Management.wiley. ^Software errors cost U.1. Hetzel (1988). John Wiley and Sons. Adam. D. "The Growth of Software Testing". People's Computer (1987). http://books. economy $59. 7. ^From 1988 on it was seen as prevention oriented period where tests were to demonstrate that software satisfies its specification.html.2. Cem. "The Growth of Software Testing".. Croatia). ISSN 0001-0782. 11. B. M. Adam. A. Testing Computer this period it was shown. NIST report 4... where the goal was to find errors. 13.. Wiley-IEEE Computer Society Press. 5. ISBN 0-471-358460. ISSN 0001-0782. D. Gelperin. ^ abcKaner. ^1983–1987 is classified as the evaluation oriented period: intention here is that during the software lifecycle a product evaluation is provided and measuring quality. Glenford J. 86.. D. ^From 1957–1978 there was the demonstration oriented period where debugging and testing was distinguished now . (1979). http://www. Dobb's journal of software tools for the professional programmer". Dr. D. ^ Company. Dorota (2007). CACM31 (6). September 2007 3. CACM31 (6). Certified Tester Foundation Level Syllabus. B. 12.. B. CACM31 (6).. Ciupa. "Dr. ^until 1956 it was the debugging oriented period. 6.wiley. ISSN 0001-0782. Dorota (2007). Jack and Nguyen. 9. ISBN 0470042125. D. Gelperin. pp. ^ ab Myers. A. 8. 41– B. CACM31 (6).. 14... B. http://www. to detect faults and to prevent faults. Gelperin. Huizinga. et al: John Wiley and Sons. Oriol. "Contract Driven Development = Test Driven Development . B. when testing was often associated to debugging: there was no clear difference between testing and debugging.. D. 15. "The Growth of Software Testing". "The Growth of Software Testing". Dobb's journal of software tools for the professional programmer (M&T Pub) 12 (1-6): 116.Writing Test Cases". Hetzel (1988). I. 10. ^ Gelperin. International Software Testing Qualifications Board . ^ Fiva. Hetzel (1988).2. CACM31 (6). p. pp.5 billion annually. Gelperin. Hetzel (1988). "The Growth of Software Testing". CACM31 (6). Falk. Hetzel (1988). 2nd Ed. Hetzel (1988). ISSN 0001-0782. (Dubrovnik. ^ Kolawa. Automated Defect Prevention: Best Practices in Software Management. ISSN 0001-0782.. Huizinga.. The Art of Software Testing. Proceedings of ESEC/FSE'07: European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering 2007. ISBN 0470042125. ^The time between 1979–1982 is announced as the destruction oriented period. ISBN 0-471-04328-1. ISSN 00010782. New York. Wiley-IEEE Computer Society Press. ^ ab Section 1.html. "The Growth of Software Testing". ^ Leitner. that software satisfies the Hung Quoc (1999). Meyer. 480 pages. B. Inc.

Topics in Dependable Embedded Systems. Retrieved 17 June 2010. ISBN 0- 20179-429-2.2 27. Cem. 960. ^ http://www. 159. James Bach. p. ISBN 978-0-615-23372-7. ^http://www. Roman (2008). . 21. Code Complete (2nd ed. "Standard glossary of terms used in Software Testing". Eushiuan (1999).ps. International Software Testing Qualifications Board 19. 29. Retrieved 2009-11-16.ece. http://www.).computer.). http://agilesoftwaredevelopment. Addison-Wesley Professional.html. (1993) (PostScript). ISBN 0- 7356-1967-0. ^ Beizer. Wiley. (1979). ISBN 1559370793. ^ McConnell.le. 145– 146. ISBN 0-471-08112-4. ^ ^ Tran.astqb. Lessons Learned in Software Testing: A Context-Driven Steve Cornett 22. 35. p. The Art of Software Testing. ISBN Retrieved 2008-02-13. Testing Object-Oriented Systems: Objects. http://www. 18. p. G. Robert V. 2007). 25. Steve (2004). http://www. UK.C. ISBN 0-201-80938-9. Certified Tester Foundation Level Syllabus. and Boris (1990). ^ Marchenko. New York: Van Nostrand Reinhold. James (June 1999). p. Artem (November 16. Code Coverage Bret Pettichord (2001).. ^Globalization Step-by-Step: The World-Ready Approach to Testing. P. How to Become a Software Tester. The Theory and Practice of Specification Based Software Testing. 45. Computer32 (6): 113–114.php#A.430. Microsoft Developer Network 32. ^ Laycock. "XP Practice: Continuous Integration".gz. ^http://www.1 26. ^ Binder. 3. Erik. ^e)Testing Phase in Software Testing:33. Effective Software Testing. 4. ^Bach. Retrieved 2008-08-19. Gelperin and W. 34. Addison Wesley. Section 1. Glenford J. 28. ^ IEEE (1990). ^ Myers. ISBN 0-471-04328-1. ^ see D. Hetzel 21. pp. John Wiley and Sons. ^Kaner. T. ^ van Veenendaal. Elfriede (2002).3. ^ Savenkov. 31. Sheffield University. Dept of Computer Science. "Risk and Requirements-Based Testing" (PDF). (1999). Microsoft Press. 17. USA: Carnegie Mellon University.cmu. pp. 23. IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries. In 30. Patterns. New York: IEEE.mcs. ^ Principle 2. Retrieved 2008-0113. Roman Savenkov Consulting.satisfice. "Verification/Validation/Certification". Software Testing Techniques (Second ed. pp.

^IEEE article on Exploratory vs. ^ Black. Cem (2003). ^Article referring to other links questioning the necessity of unit testing 57. ^ Pan. (April 2004). ^context-driven-testing. 2009 ^ ab"ISTQB".".istqb.Vol. Addison Wesley.archive.pdf. http://www. ^Microsoft Development Network Discussion on exactly this topic [edit] External links .org/a/mest. Rex (December 2008). Archived from the original on unknown. Advanced Software Testing. 51. 56. Ross & Associates 45. John S. See also Agile adoption study from 2007 53. http://www. ^ abAmerican Society for Quality 49. 1999. ^ An example is Mark Fewster.testingeducation.testingeducation. http://www. Cem (2001). http://www. Levent (February 19. Electrical and Computer Engineering Department. 38. http://www. young students of the Project Management Institute. "Agile Software Development for an Agile Force". "Agile 101: What is Continuous Integration?".astqb. ^ ab"ISTQB in the U. IEEE standard for software test 54. 2: Guide to the ISTQB Advanced Certification as an Advanced Test Manager. ^ IEEE (1998). 47. 2007). "Software Testing (18-849b Dependable Embedded Systems)". ^K. ^IEEE article about differences in adoption of agile trends between experienced managers vs. http://web. "NSF grant proposal to "lay a foundation for significant improvements in the quality of academic and commercial courses in software testing"" (pdf).hill. http://www. July 1. 46. J. Non Exploratory testing 55. ^ Kaner. Santa Barbara: Rocky Nook Publisher. Retrieved 2009-11-16. ^ Willison. CrossTalk (STSC) (April 2004). Topics in Dependable Embedded Systems. ISBN 0-7381-1443-X.stsc. Carnegie Mellon University.36. ^Article on taking agile traits without the agile method. 40. ^ Gurses.S. ^ abInternational Institute for Software Testing 44. Dorothy Graham: Software Test Automation. Jiantao (Spring 1999).pdf. ^ abcdeQuality Assurance Institute 43. ISBN 0-201-33140-3. 41. 4/0404willison.ece. ISBN New York: IEEE. "Measuring the Effectiveness of Software Testers" (pdf).jacoozi. ^ abEXIN: Examination Institute for Information Science 48. ^“We’re all part of the story” by David Strom. ^ Kaner.

com Automated software testing metrics including manual testing metrics [show]v·d·eMajor fields of computer science M a t h e m a t i c a lMathematical logic ·Set theory ·Number theory ·Graph theory ·Type theory ·Category theory ·Numerical analysis ·Information theory f o u n d a t i o n s T Automata theory ·Computability theory ·Computational complexity theory ·Quantum computing h theory e o r y o f c o m .At Wikiversity you can learn more and teach others about Software testing at: The Department of Software testing • • • Software testing tools and products at the Open Directory Project "Software that makes Software better" Economist.

p u t a t i o n A l g o r i t h m s a n d Analysis of algorithms ·Algorithm design ·Computational geometry d a t a s t r u c t u r e s P Parsers ·Interpreters ·Procedural programming ·Object-oriented programming ·Functional r programming ·Logic programming ·Programming paradigms o g r a m m .

i n g l a n g u a g e s a n d C o m p i l e r s C Multiprocessing ·Grid computing ·Concurrency control o n c u r r e n t . P a r a l l e l .

. a n d D i s t r i b u t e d s y s t e m s S o f t w a r e e Requirements analysis ·Software design ·Computer programming ·Formal methods ·Software n testing ·Software development process g i n e e r i n g .

S y s t e m a r c Computer architecture ·Computer organization ·Operating systems h i t e c t u r e T e l e c o m m u n i c a t iComputer audio ·Routing ·Network topology ·Cryptography o n & N e t w o r k i n g .

D a t a Database management systems ·Relational databases ·SQL ·Transactions ·Database b indexes ·Data mining a s e s A r t i f i c i a l Automated reasoning ·Computational linguistics ·Computer vision ·Evolutionary i computation ·Expert systems ·Machine learning ·Natural language processing ·Robotics n t e l l i g e n c e C Visualization ·Computer animation ·Image processing o m p u t e r g r a p .

h i c s H u m a n – c o m p u t e Computer accessibility ·User interfaces ·Wearable computing ·Ubiquitous computing ·Virtual r reality i n t e r a c t i o n S Artificial life ·Bioinformatics ·Cognitive science ·Computational chemistry ·Computational c ineuroscience ·Computational physics ·Numerical algorithms ·Symbolic mathematics e n t i f i c c o m p u .

[show]v·d·eSoftware engineering F i e Requirements analysis • Systems analysis • Software design • Computer programming • Formal lmethods • Software testing • Software deployment • Software maintenance d s C o n Data modeling • Enterprise architecture • Functional specification • Modeling language • c Programming paradigm • Software • Software architecture • Software development methodology e Software development process • Software quality • Software quality assurance • Software • p archaeology • Structured analysis t s O r i e n t Agile • Aspect-oriented • Object orientation • Ontology • Service orientation • SDLC a t i o n s Development Agile • Iterative model • RUP • Scrum • Spiral model • Waterfall model • XP • Vmodels Model • Incremental model • Prototype model M o d Other Automotive SPICE • CMMI • Data model • Function model • Information model • e models Metamodeling • Object model • Systems model • View model l s Modeling IDEF • UML languages .t i n g Note: Computer science can also be split up into different topics or fields according to the ACM Computing Classification System." Categories: Software development process | Software testing Hidden categories: All articles with unsourced statements | Articles with unsourced statements from February 2011 | Articles with unsourced statements from January 2008 | Articles with unsourced statements from March 2008 Personal tools • • • Views Log in / create account Article Discussion Namespaces Variants .S o f t w a r e Kent Beck • Grady Booch • Fred Brooks • Barry Boehm • Ward Cunningham • Ole-Johan Dahl • Tom DeMarco • Martin Fowler • C. Royce n Colette Rolland • James Rumbaugh • Niklaus Wirth • Edward Yourdon • Victor Basili • g i n e e r s R e l a t e d Computer science • Computer engineering • Enterprise engineering • History • Management • Project management • Quality management • Software ergonomics • Systems engineering f i e l d s Retrieved from "http://en. Jackson • Ivar e Jacobson • Craig Larman • James Martin • Bertrand Meyer • David Parnas • Winston W.wikipedia. Hoare • Watts Humphrey • Michael A. A.

• • • Actions Search Read Edit View history Top of Form Special:Search Bottom of Form Navigation • • • • • • • • • • • Toolbox Main page Contents Featured content Current events Random article Donate to Wikipedia Help About Wikipedia Community portal Recent changes Contact Wikipedia What links here Related changes Upload file Special pages Permanent link Cite this page Create a book Download as PDF Printable version ‫العربية‬ Беларуская (тарашкевіца) Interaction • • • • • • • • • • • Print/export Languages .

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Català Česky Deutsch Eesti Español ‫فارسی‬ Français 한국어 िहनदी Bahasa Indonesia Italiano ‫עברית‬ ಕನಡ ನ Magyar Bahasa Melayu Nederlands 日本語 Norsk (bokmål) Polski Português Română Русский Slovenčina Suomi Svenska தமிழ் ไทย Українська Tiếng Việt 中文 This page was last modified on 8 March 2011 at 13:08. Inc. Contact us • • • .. See Terms of Use for details. Text is available under the Creative Commons Attribution-ShareAlike License. additional terms may apply. a non-profit organization. Wikipedia® is a registered trademark of the Wikimedia Foundation.

• • • Privacy policy About Wikipedia Disclaimers • • .