This HTML5 document contains 43 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
dctermshttp://purl.org/dc/terms/
dbohttp://dbpedia.org/ontology/
foafhttp://xmlns.com/foaf/0.1/
dbpedia-huhttp://hu.dbpedia.org/resource/
n11https://global.dbpedia.org/id/
dbthttp://dbpedia.org/resource/Template:
rdfshttp://www.w3.org/2000/01/rdf-schema#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
wikipedia-enhttp://en.wikipedia.org/wiki/
dbchttp://dbpedia.org/resource/Category:
provhttp://www.w3.org/ns/prov#
dbphttp://dbpedia.org/property/
xsdhhttp://www.w3.org/2001/XMLSchema#
wikidatahttp://www.wikidata.org/entity/
dbrhttp://dbpedia.org/resource/

Statements

Subject Item
dbr:Bug-driven_development
dbo:wikiPageWikiLink
dbr:Tester-driven_development
dbo:wikiPageRedirects
dbr:Tester-driven_development
Subject Item
dbr:Tester_Driven_Development
dbo:wikiPageWikiLink
dbr:Tester-driven_development
dbo:wikiPageRedirects
dbr:Tester-driven_development
Subject Item
dbr:Tester-driven_development
rdfs:label
Tester-driven development
rdfs:comment
In software engineering, tester-driven development, or bug-driven development, is an anti-pattern where the requirements are determined by bug reports or test results rather than, for example, the value or cost of a feature. The concept is generally invoked facetiously, and comes with the implication that high volumes of computer code are written with little regard for unit testing by the programmers. Projects that are developed using this anti-pattern often suffer from being extremely late. Another common problem is poor code quality.
dcterms:subject
dbc:Software_development_process dbc:Anti-patterns
dbo:wikiPageID
20541638
dbo:wikiPageRevisionID
1050038683
dbo:wikiPageWikiLink
dbr:Unit_testing dbr:Software_prototyping dbr:Quality_assurance dbr:Feature_creep dbr:Code_quality dbr:Agile_software_development dbr:Test-driven_development dbr:Software_project dbc:Software_development_process dbc:Anti-patterns dbr:Anti-pattern dbr:Requirement dbr:Requirements_management dbr:Software_test dbr:Bug_report dbr:Extreme_programming dbr:Extreme_programming_practices dbr:Software_engineering dbr:Software_feature dbr:Project_management
owl:sameAs
n11:4vKgh dbpedia-hu:Tesztelővezérelt_fejlesztés wikidata:Q7705844
dbp:wikiPageUsesTemplate
dbt:Reflist dbt:Software-eng-stub dbt:Short_description
dbo:abstract
In software engineering, tester-driven development, or bug-driven development, is an anti-pattern where the requirements are determined by bug reports or test results rather than, for example, the value or cost of a feature. The concept is generally invoked facetiously, and comes with the implication that high volumes of computer code are written with little regard for unit testing by the programmers. The term itself is a tongue-in-cheek reference to test-driven development, a widely used methodology in agile software practices. In test-driven development tests are used to drive the implementation towards fulfilling the requirements. Tester-driven development instead shortcuts the process by removing the determination of requirements and letting the testers (or the QA team) drive what they think the software should be through the testing (or QA) process. Projects that are developed using this anti-pattern often suffer from being extremely late. Another common problem is poor code quality. Common causes for projects ending up being run this way are often: * The testing phase started too early; * Incomplete requirements; * Inexperienced testers; * Inexperienced developers; * Poor project management. Things get worse when the testers realize that they don't know what the requirements are and therefore don't know how to test any particular code changes. The onus then falls on the developers of individual changes to write their own test cases and they are happy to do so because their own tests normally pass and their performance measurements improve. Project leaders are also delighted by the rapid reduction in the number of open change requests.
prov:wasDerivedFrom
wikipedia-en:Tester-driven_development?oldid=1050038683&ns=0
dbo:wikiPageLength
2507
foaf:isPrimaryTopicOf
wikipedia-en:Tester-driven_development
Subject Item
dbr:Tester_driven_development
dbo:wikiPageWikiLink
dbr:Tester-driven_development
dbo:wikiPageRedirects
dbr:Tester-driven_development
Subject Item
wikipedia-en:Tester-driven_development
foaf:primaryTopic
dbr:Tester-driven_development