Software testing 29090 225796087 2008-07-15T13:09:18Z Tedickey 1942604 rm redundant comments {{portal|Software Testing}} {{Software development process}} '''Software testing''' is the process of checking software, to verify that it satisfies its requirements and to detect errors. Software testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test<ref>[http://www.kaner.com/pdfs/ETatQAI.pdf Exploratory Testing], Cem Kaner, Florida Institute of Technology, ''Quality Assurance Institute Worldwide Annual Software Testing Conference'', Orlando, FL, November 2006</ref> , with respect to the context in which it is intended to operate. This includes, but is not limited to, the process of executing a program or application with the intent of finding [[software bugs]]. Quality is not an absolute; it is value to some person. With that in mind, testing can never completely establish the correctness of arbitrary computer software; testing furnishes a ''criticism'' or ''comparison'' that compares the state and behaviour of the product against a specification. An important point is that ''software testing'' should be distinguished from the separate discipline of ''[[Software Quality Assurance]]'' (S.Q.A.), which encompasses all business process areas, not just testing.{{Fact|date=January 2008}} Over its existence, computer software has continued to grow in complexity and size. 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 presumably must 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 study conducted by [[NIST]] in 2002 reports 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.<ref>[http://www.nist.gov/public_affairs/releases/n02-10.htm Software errors cost U.S. economy $59.5 billion annually], NIST report</ref> == Scope == A primary purpose for testing is to detect software failures so that defects may be uncovered and corrected. This is a non-trivial pursuit. Testing cannot establish that a product functions properly under all conditions but can only establish that it does not function properly under specific conditions.<ref name=Kaner1>{{cite book | last = Kaner | first = Cem | authorlink = Cem Kaner | coauthors = Falk, Jack and Nguyen, Hung Quoc | title = Testing Computer Software, 2nd Ed. | publisher = John Wiley and Sons, Inc. | date = 1999 | location = New York, et al | pages = 480 pages | url = | doi = | id = | isbn = 0-471-35846-0 }}</ref> 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 quality aspects of code: does it do what it is supposed to do and do what it needs to do. In the current culture of software development, a testing organization may be separate from the development team. There are various roles for testing team members. Information derived from software testing may be used to correct the process by which software is developed. ===Defects and failures=== The software faults occur through the following process. A programmer makes an [[human error|error]] (mistake), which results in a [[Fault (technology)|defect]] (fault, bug) in the software [[source code]]. If this defect is executed, in certain situations the system will produce wrong results, causing a [[failure]].<ref name="ctfl">Section 1.1.2, [http://www.istqb.org/downloads/syllabi/SyllabusFoundation.pdf Certified Tester Foundation Level Syllabus], [[International Software Testing Qualifications Board]]</ref> Not all defects will necessarily result in failures. For example, defects in [[dead code]] will never result in failures. A defect can turn into a failure when the environment is changed. Examples of these changes in environment include the software being run on a new [[hardware]] platform, alterations in [[source data]] or interacting with different software.<ref name="ctfl" /> A single defect may result in a wide range of failure symptoms. ===Input combinations and preconditions=== A problem with software testing is that testing under all combinations of inputs and preconditions (initial state) is not feasible, even with a simple product.<ref name=Kaner1>pp 17-18</ref><ref>Principle 2, Section 1.3, [http://www.bcs.org/upload/pdf/istqbsyll.pdf Certified Tester Foundation Level Syllabus], [[International Software Testing Qualifications Board]]</ref> This means that the number of [[Software bug|defect]]s in a software product can be very large and defects that occur infrequently are difficult to find in testing. More significantly, parafunctional dimensions of quality (how it is supposed to ''be'' versus what it is supposed to ''do'') -- for example, usability, scalability, performance, compatibility, reliability -- can be highly subjective; something that constitutes sufficient value to one person may be intolerable to another. ===Static vs. dynamic testing=== There are many approaches to software testing. [[Code review|Reviews]], [[walkthrough]]s or [[Software inspection|inspections]] are considered as [[static testing]], whereas actually executing programmed code with a given set of [[test case]]s is referred to as [[dynamic testing]]. ===Software verification and validation=== Software testing is used in association with [[Verification and Validation (software)|verification and validation]]:<ref name="tran">{{cite book |last=Tran | first=Eushiuan | editor=Koopman, P. | title=Topics in Dependable Embedded Systems | location=USA | publisher=Carnegie Mellon University | year=1999 | chapter=Verification/Validation/Certification |chapterurl=http://www.ece.cmu.edu/~koopman/des_s99/verification/index.html | accessdate=2008-01-13}}</ref> *'''[[Verification]]''': Have we built the software right (i.e., does it match the specification)? *'''[[Validation]]''': Have we built the right software (i.e., is this what the customer wants)? ===The software testing team=== Software testing can be done by ''[[software tester]]s''. Until the 1950s the term "software tester" was used generally, but later it was also seen as a separate profession. Regarding the periods and the different goals in software testing<ref>see D. Gelperin and W.C. Hetzel</ref> there have been established different roles: test lead/manager, test designer, tester, test automater/automation developer, and test administrator. === Software Quality Assurance (SQA) === Thought controversial<ref name=Kaner1>p 347</ref>, software testing may be viewed as an important part of the [[software quality assurance]] (SQA) process.{{Fact|date=December 2007}} In SQA, software process specialists and auditors take a broader view on software and its development. They examine and change the software engineering process itself to reduce the amount of faults that end up in defect rate. What constitutes an acceptable defect rate depends on the nature of the software. An arcade video game designed to simulate flying an airplane would presumably have a much higher tolerance for defects than [[mission critical]] software such as that used to control the functions of an airliner. Although there are close links with SQA, testing departments often exist independently, and there may be no SQA function in some companies. == History == The separation of debugging from testing was initially introduced by Glenford J. Myers in 1979.<ref>{{cite book|first=Glenford J.|last=Myers|title=The Art of Software Testing|publisher=John Wiley and Sons|year=1979|id=ISBN 0-471-04328-1}}</ref> Although his attention was on breakage testing, it illustrated the desire of the software engineering community to separate fundamental development activities, such as debugging, from that of verification. Dr. [[Dave Gelperin]] and Dr. [[William C. Hetzel]] classified in 1988 the phases and goals in software testing in the following stages:<ref>{{cite journal|first=D.|last=Gelperin|coauthors=B. Hetzel|title=The Growth of Software Testing|journal=CACM|volume=31|issue=6|year=1988|id=ISSN 0001-0782}}</ref> * Until 1956 - Debugging oriented<ref>''until 1956 it was the debugging oriented period, when testing was often associated to debugging: there was no clear difference between testing and debugging.'' {{cite journal|first=D.|last=Gelperin|coauthors=B. Hetzel|title=The Growth of Software Testing|journal=CACM|volume=31|issue=6|year=1988|id=ISSN 0001-0782}}</ref> * 1957-1978 - Demonstration oriented<ref>''From 1957-1978 there was the demonstration oriented period where debugging and testing was distinguished now - in this period it was shown, that software satisfies the requirements.'' {{cite journal|first=D.|last=Gelperin|coauthors=B. Hetzel|title=The Growth of Software Testing|journal=CACM|volume=31|issue=6|year=1988|id=ISSN 0001-0782}}</ref> * 1979-1982 - Destruction oriented<ref>''The time between 1979-1982 is announced as the destruction oriented period, where the goal was to find errors.'' {{cite journal|first=D.|last=Gelperin|coauthors=B. Hetzel|title=The Growth of Software Testing|journal=CACM|volume=31|issue=6|year=1988|id=ISSN 0001-0782}}</ref> * 1983-1987 - Evaluation oriented<ref>''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.'' {{cite journal|first=D.|last=Gelperin|coauthors=B. Hetzel|title=The Growth of Software Testing|journal=CACM|volume=31|issue=6|year=1988|id=ISSN 0001-0782}}</ref> * 1988-2000 - Prevention oriented<ref>''From 1988 on it was seen as prevention oriented period where tests were to demonstrate that software satisfies its specification, to detect faults and to prevent faults.'' {{cite journal|first=D.|last=Gelperin|coauthors=B. Hetzel|title=The Growth of Software Testing|journal=CACM|volume=31|issue=6|year=1988|id=ISSN 0001-0782}}</ref> == Testing methods == Software testing methods are traditionally divided into [[black box testing]] and [[white box testing]]. These two approaches are used to describe the point of view that a test engineer takes when designing test cases. ===Black box testing=== '''[[Black box testing]]''' treats the software as a black-box without any understanding of internal behavior. It aims to test the functionality according to the requirements.<ref>{{cite paper | last = Laycock | first = G. T. | title = The Theory and Practice of Specification Based Software Testing | publisher = Dept of Computer Science, Sheffield University, UK | date = 1993 | url =http://www.mcs.le.ac.uk/people/gtl1/thesis.ps.gz | format = [[PostScript]]| accessdate = 2008-02-13 }}</ref> Thus, the tester inputs data and only sees the output from the test object. This level of testing usually requires thorough test cases to be provided to the tester who then can simply verify that for a given input, the output value (or behavior), is the same as the expected value specified in the test case. Black box testing methods include: [[equivalence partitioning]], [[boundary value analysis]], [[all-pairs testing]], [[fuzz testing]], [[model-based testing]], [[traceability matrix]] etc. ===White box testing=== '''[[White box testing]]''', however, is when the tester has access to the internal data structures, code, and algorithms. ====Types of white box testing==== The following types of white box testing exist: * '''[[code coverage]]''' - 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. * '''[[mutation testing]]''' methods. * [[fault injection]] methods. * [[static testing]] - White box testing includes all static testing. ====Code completeness evaluation==== White box testing methods can also be used to evaluate the completeness of a test suite that was created with black box testing methods. 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.<ref>[http://www.bullseye.com/coverage.html#intro Introduction], Code Coverage Analysis, Steve Cornett</ref> Two common forms of code coverage are: * ''function coverage'', which reports on functions executed * and ''statement coverage'', which reports on the number of lines executed to complete the test. They both return a coverage metric, measured as a percentage. ===Grey Box Testing=== In recent years the term '''grey box''' testing has come into common usage. This involves having access to internal data structures and algorithms for purposes of designing the test cases, but testing at the user, or black-box level. Manipulating input data and formatting output do not qualify as grey-box because the input and output are clearly outside of the black-box we are calling the software under test. This is particularly important when conducting [[integration testing]] between two modules of code written by two different developers, where only the interfaces are exposed for test. Grey box testing may also include [[Reverse engineering#Reverse engineering of software|reverse engineering]] to determine, for instance, boundary values. ===Non Functional Software Testing=== Special methods exist to test non-functional aspects of software. * '''[[Software performance testing|Performance testing]]''' checks to see if the software can handle large quantities of data or [[Load testing|users]]. * '''[[Usability testing]]''' is needed to check if the user interface is easy to use and understand. * '''[[Security testing]]''' is essential for software which processes confidential data and to prevent [[Backdoor (computing)|system intrusion]] by [[Hacker (computer security)|hackers]]. * '''[[internationalization and localization]]''' is needed to test these aspects of software, for which a [[pseudolocalization]] method can be used. == Testing process == A common practice of software testing is performed by an independent group of testers after the functionality is developed before it is shipped to the customer.<ref>[http://www.etestinghub.com/testing_lifecycles.php#2 e)Testing Phase in Software Testing:-]</ref> This practice often results in the testing phase being used as [[project management|project]] buffer to compensate for project delays, thereby compromising the time devoted to testing.<ref>{{cite book|first=Glenford J.|last=Myers|title=The Art of Software Testing|publisher=John Wiley and Sons|year=1979|id=ISBN 0-471-04328-1|page=145-146}}</ref> Another practice is to start software testing at the same moment the project starts and it is a continuous process until the project finishes.<ref>{{cite book | last = Dustin | first = Elfriede | title=Effective Software Testing|publisher=Addison Wesley|year=2002|isbn = 0-20179-429-2|page=3}}</ref> In counterpoint, some emerging software disciplines such as [[extreme programming]] and the [[agile software development]] movement, adhere to a "[[Test-driven development|test-driven software development]]" model. In this process [[unit tests]] are written first, by the [[software engineering|software engineers]] (often with [[pair programming]] in the extreme programming methodology). Of course these tests fail initially; as they are expected to. Then as code is written it passes incrementally larger portions of the test suites. The test suites are continuously updated as new failure conditions and corner cases are discovered, and they are integrated with any regression tests that are developed. 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). Testing can be done on the following levels: * [[Unit testing]] tests the minimal software component, or module. Each unit (basic component) of the software is tested to verify that the detailed design for the unit has been correctly implemented. In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors.<ref>{{cite book|last=Binder | first = Robert V.|title=Testing Object-Oriented Systems: Objects, Patterns, and Tools|publisher=Addison-Wesley Professional|date=1999|isbn= 0-201-80938-9|page=45}}</ref> * [[Integration testing]] exposes defects in the interfaces and interaction between integrated components (modules). Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system. <ref>{{cite book|first=Boris|last=Beizer|title=Software Testing Techniques|date=1990|edition=Second Edition|isbn=0-442-20672-0|pages=pp.21,430}}</ref> * [[System testing]] tests a completely integrated system to verify that it meets its requirements.<ref name="ieee">{{cite book|author=IEEE|title=IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries|publisher=IEEE|location=New York|date=1990|isbn= 1559370793|}}</ref> * [[System integration testing]] verifies that a system is integrated to any external or third party systems defined in the system requirements.{{Fact|date=January 2008}} Before shipping the final version of software, ''alpha'' and ''beta'' testing are often done additionally: * '''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.{{Fact|date=March 2008}} * '''Beta testing''' comes after alpha testing. Versions of the software, known as [[beta version]]s, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or [[computer bug|bug]]s. Sometimes, beta versions are made available to the open public to increase the [[Feedback#In organizations|feedback]] field to a maximal number of future users.{{Fact|date=March 2008}} Finally, [[acceptance testing]] can be conducted by the end-user, customer, or client to validate whether or not to accept the product. Acceptance testing may be performed as part of the hand-off process between any two phases of development. {{Fact|date=January 2008}} ===Regression testing=== {{main|Regression testing}} After modifying software, either for a change in functionality or to fix defects, a [[Regression testing|regression test]] re-runs previously passing tests on the modified software to ensure that the modifications haven't unintentionally caused a ''[[Software regression|regression]]'' of previous functionality. Regression testing can be performed at any or all of the above test levels. These regression tests are often [[Test automation|automated]]. More specific forms of regression testing are known as [[sanity test]]ing, when quickly checking for bizarre behaviour, and [[smoke testing]] when testing for basic functionality. === Finding faults early === It is commonly believed that the earlier a defect is found the cheaper it is to fix it.<ref>{{cite book | last = Kaner | first = Cem | authorlink = Cem_Kaner | coauthors = James Bach, Bret Pettichord | title=Lessons Learned in Software Testing: A Context-Driven Approach | publisher=[[John Wiley & Sons| Wiley]] |year=2001 | isbn = 0-471-08112-4 | page=4 }}</ref> The following table shows the cost of fixing the defect depending on the stage it was found.<ref>{{cite book | last = McConnell | first = Steve | title = Code Complete | edition = 2nd edition | publisher = Microsoft Press |date=2004 | pages = 960 | isbn = 0-7356-1967-0 }}</ref> For example, if a problem in requirements is found only post-release, then it would cost 10-100 times more to fix it comparing to the cost if the same fault was already found by the requirements review. {| class="wikitable" |+ |- !rowspan="2" | Time Introduced !colspan="5" | Time Detected |- !Requirements !Architecture !Construction !System Test !Post-Release |- ! Requirements |align="center"| 1 |align="center"| 3 |align="center"| 5-10 |align="center"| 10 |align="center"| 10-100 |- !Architecture |align="center"| - |align="center"| 1 |align="center"| 10 |align="center"| 15 |align="center"| 25-100 |- !Construction |align="center"| - |align="center"| - |align="center"| 1 |align="center"| 10 |align="center"| 10-25 |} === Measuring software testing === Usually, quality is constrained to such topics as [[correctness]], completeness, [[computer security audit|security]],{{Fact|date=January 2008}} but can also include more technical requirements as described under the [[International Organization for Standardization|ISO]] standard [[ISO 9126]], such as capability, [[reliability]], [[algorithmic efficiency|efficiency]], [[Porting|portability]], [[maintainability]], compatibility, and [[usability]]. There are a number of common software measures, often called "metrics", which are used to measure the state of the software or the adequacy of the testing. ===Testing artifacts=== {{Refimprovesect|date=January 2008}} Software testing process can produce several [[Artifact (software development)|artifacts]]. ====Test case==== A [[test case]] is a software testing document, which consists of event, action, input, output, expected result, and actual result. Clinically defined a test case is an input and an expected result.<ref>{{cite book|author=IEEE|title=[[IEEE 829|IEEE standard for software test documentation]]|publisher=IEEE|location=New York|date=1998|isbn= 0-7381-1443-X}}</ref> This can be as pragmatic as 'for condition x your derived result is y', whereas other test cases described 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 repository. In a database system, you may also be able to see past test results and who generated the results and the system configuration used to generate those results. These past results would usually be stored in a separate table. ====Test script==== The [[test script]] is the combination of a test case, test procedure, and test data. Initially the term was derived from the product of work created by automated regression test tools. Today, [[test script]]s can be manual, automated, or a combination of both. ====Test suite==== The most common term for a collection of test cases is a [[test suite]]. The test suite often also contains more detailed instructions or goals for each collection of test cases. It definitely contains a section where the tester identifies the system configuration used during testing. A group of test cases may also contain prerequisite states or steps, and descriptions of the following tests. ====Test plan==== A test specification is called a [[test plan]]. The developers are well aware what test plans will be executed and this information is made available to the developers. This makes the developers more cautious when developing their code. This ensures that the developers code is not passed through any surprise test case or test plans. ====Test harness==== The software, tools, samples of data input and output, and configurations are all referred to collectively as a [[test harness]]. ===A sample testing cycle=== Although variations exist between organizations, there is a typical cycle for testing<ref>{{citation |url=http://www.ece.cmu.edu/~koopman/des_s99/sw_testing/ |contribution=Software Testing (18-849b Dependable Embedded Systems) |title=Topics in Dependable Embedded Systems |last= Pan |first=Jiantao |date=Spring 1999 |publisher=Electrical and Computer Engineering Department, Carnegie Mellon University }}</ref>: * '''[[Requirements analysis]]''': Testing should begin in the requirements phase of the [[software development life cycle]]. During the design phase, testers work with developers in determining what aspects of a design are testable and with what parameters those tests work. * '''Test planning''': Test strategy, [[test plan]], [[testbed]] creation. A lot of activities will be carried out during testing, so that a plan is needed. * '''Test development''': Test procedures, [[Scenario test|test scenarios]], [[test case]]s, test scripts to use in testing software. * '''Test execution''': Testers execute the software based on the plans and tests and report any errors found to the development team. * '''Test reporting''': Once testing is completed, testers generate metrics and make final reports on their [[test effort]] and whether or not the software tested is ready for release. * '''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 treated, fixed, rejected (i.e. found software working properly) or deferred to be dealt with at a later time. * '''Retesting the resolved defects'''. Once a defect has been dealt with by the development team, it is retested by the testing team. * '''Regression testing''': 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. == Controversy == {{main|Software testing controversies}} Some of the major controversies include: * '''What constitutes responsible software testing?''' - Members of the "context-driven" school of testing<ref>[http://www.context-driven-testing.com context-driven-testing.com]</ref> believe that there are no "best practices" of testing, but rather that testing is a set of skills that allow the tester to select or invent testing practices to suit each unique situation. <ref>[http://www.technicat.com/writing/process.html Article on taking agile traits without the agile method.</ref> * '''Agile vs. traditional''' - Should testers learn to work under conditions of uncertainty and constant change or should they aim at [[Capability Maturity Model|process "maturity"]]? The [[agile testing]] movement has received growing popularity since [[2006]] mainly in commercial circles <ref>[http://ieeexplore.ieee.org/Xplore/login.jsp?url=/iel5/10705/33795/01609838.pdf?temp=x IEEE article about differences in adoption of agile trends between experienced managers vs. young students of the Project Management Institute]. See also [http://www.ambysoft.com/downloads/surveys/AgileAdoption2007.ppt Agile adoption study from 2007]</ref>, whereas government and military software providers are slow to embrace this methodology, and mostly still hold to CMM.<ref>[http://www.stsc.hill.af.mil/crosstalk/2004/04/0404willison.html Agile software development practices slowly entering the military]</ref> * '''[[Exploratory test|Exploratory]] vs. scripted'''<ref>[http://ieeexplore.ieee.org/iel5/10351/32923/01541817.pdf?arnumber=1541817 IEEE article on Exploratory vs. Non Exploratory testing]</ref> - Should tests be designed at the same time as they are executed or should they be designed beforehand? * '''[[Manual testing|Manual]] vs. automated''' - Some writers believe that [[test automation]] is so expensive relative to its value that it should be used sparingly.<ref>An example is Mark Fewster, Dorothy Graham: ''Software Test Automation.'' Addison Wesley, 1999, ISBN 0-201-33140-3. See also [http://searchsoftwarequality.techtarget.com/news/column/0,294698,sid92_gci1297737,00.html Studies on automatic vs. manual testing]</ref> Others, such as advocates of [[agile development]], recommend automating 100% of all tests. * '''Software design vs. software implementation'''<ref>[http://java.dzone.com/news/why-evangelising-unit-testing- Article referring to other links questioning the necessity of unit testing]</ref> - 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, that the act of testing can also affect that which is being tested<ref>[http://channel9.msdn.com/forums/Coffeehouse/402611-Are-you-a-Test-Driven-Developer/ Microsoft Development Network Discussion on exactly this topic]</ref>. == Certification == 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. No certification is based on a widely accepted body of knowledge. This has led some to declare that the testing field is not ready for certification.<ref>{{cite web|first=Cem|last=Kaner|year=2001|url=http://www.testingeducation.org/general/nsf_grant.pdf|format=pdf|title=NSF grant proposal to "lay a foundation for significant improvements in the quality of academic and commercial courses in software testing"}}</ref> Certification itself cannot measure an individual's productivity, their skill, or practical knowledge, and cannot guarantee their competence, or professionalism as a tester.<ref>{{cite web|url=http://www.testingeducation.org/a/mest.pdf|format=pdf|first=Cem|last=Kaner|title=Measuring the Effectiveness of Software Testers|year=2003}}</ref> ===Software testing certification types=== Certifications can be grouped into: exam-based and education-based. * '''Exam-based certifications''': For these there is the need to pass an exam, which can also be learned by self-study: e.g. for ISTQB or QAI. * '''Education-based certifications''': Education based software testing certifications are instructor-led sessions, where each course has to be passed, e.g. IIST (International Institute for Software Testing). ===Testing certifications=== <!--this list is alphabetised--> * Certified Software Tester ('''CSTE''') offered by the ''Quality Assurance Institute'' ([[QAI]])<ref>[http://www.qaiworldwide.org/ Quality Assurance Institute]</ref> * Certified Software Test Professional ('''CSTP''') offered by the ''International Institute for Software Testing''<ref>[http://www.testinginstitute.com/ International Institute for Software Testing]</ref> * [['''CSTP''' (TM)]] (Australian Version) offered by ''K. J. Ross & Associates''<ref>[http://www.kjross.com.au/cstp/ K. J. Ross & Associates]</ref> * '''CATe''' offered by the ''International Institute for Software Testing''<ref>[http://www.testinginstitute.com/ International Institute for Software Testing]</ref> * '''ISEB''' offered by the [[ISEB|Information Systems Examinations Board]] * Certified Tester, Foundation Level ('''CTFL''') offered by the [[ISTQB|International Software Testing Qualification Board]] <ref name="istqb">{{cite web |url=http://www.istqb.org/ |title=ISTQB}}</ref><ref name="astqb">{{cite web |url=http://www.astqb.org/ |title=ISTQB in the U.S.}}</ref> * Certified Tester, Advanced Level ('''CTAL''') offered by the [[ISTQB|International Software Testing Qualification Board]] <ref name="istqb"/><ref name="astqb"/> * '''CBTS''' offered by the ''Brazilian Certification of Software Testing'' ([[ALATS]])<ref>[http://www.ALATS.ORG.BR/ ALATS]</ref> ===Quality assurance certifications=== * '''CSQE''' offered by the [[American Society for Quality]] (ASQ)<ref>[http://www.asq.org/ American Society for Quality]</ref> * '''CSQA''' offered by the ''Quality Assurance Institute'' ([[QAI]])<ref>[http://www.qaiworldwide.org/ Quality Assurance Institute]</ref> == See also == * [[Dynamic program analysis]] * [[Formal verification]] * [[Reverse Semantic Traceability]] * [[Static code analysis]] * [[GUI software testing]] * [[Web testing]] ==References== {{reflist}} ==External links== {{WVD}} *{{dmoz|Computers/Programming/Software_Testing/Products_and_Tools|Software testing tools and products}} *[http://www.economist.com/science/tq/displaystory.cfm?story_id=10789417 "Software that makes Software better" Economist.com] [[Category:Software testing| ]] [[ar:فحص البرمجيات]] [[be-x-old:Тэставаньне праграмнага забеспячэньня]] [[cs:Testování softwaru]] [[de:Softwaretest]] [[et:Tarkvara testimine]] [[es:Pruebas de software]] [[fr:Test (informatique)]] [[ko:소프트웨어 테스트]] [[it:Collaudo del software]] [[he:בדיקות תוכנה]] [[hu:Szoftvertesztelés]] [[nl:Testen (software)]] [[ja:ソフトウェアテスト]] [[no:Programvaretesting]] [[pl:Testowanie oprogramowania]] [[pt:Teste de software]] [[ro:Testarea software]] [[ru:Тестирование программного обеспечения]] [[sk:Testovanie softvéru]] [[sv:Programvarutestning]] [[ta:மென்பொருட் சோதனை]] [[te:సాఫ్టువేరు టెస్టింగ్]] [[th:Software testing]] [[vi:Kiểm tra phần mềm]] [[uk:Тестування програмного забезпечення]] [[zh:软件测试]]