Why software testing is sometimes ineffective: two applied studies of positive test strategy.
The term positive test strategy describes the tendency to test a hypothesis with test cases that confirm (i.e., aim to support) rather than disconfirm the hypothesis. Most demonstrations of this phenomenon have involved relatively abstract problems. The authors suggest that people use a positive t...
| Publicado en: | Journal of Applied Psychology Vol. 79; pp. 142 - 156 |
|---|---|
| Autores principales: | , , |
| Formato: | Artículo |
| Publicado: |
American Psychological Association
February 1994
|
| Materias: | |
| Acceso en línea: | Ver este registro en EBSCOhost |
| fields | @attributes: recordID: 1 pdfLink: plink: https://search.ebscohost.com/login.aspx?direct=true&db=ssf&AN=512388649&site=ehost-live header: @attributes: shortDbName: ssf uiTerm: 512388649 longDbName: Social Sciences Full Text (H.W. Wilson) uiTag: AN controlInfo: bkinfo: jinfo: jid: 00219010 JAY jtl: Journal of Applied Psychology issn: 00219010 maglogo: N pubinfo: dt: February 1994 vid: 79 pid: 34 pub: American Psychological Association artinfo: ui: 512388649 10.1037/0021-9010.79.1.142 ppf: 142 ppct: 14 formats: tig: atl: Why software testing is sometimes ineffective: two applied studies of positive test strategy. aug: au: Teasley, Barbee E. Leventhal, Laura Marie Mynatt, Clifford R. su: Hypothesis Computer software testing sug: subj: Hypothesis Computer software testing ab: The term positive test strategy describes the tendency to test a hypothesis with test cases that confirm (i.e., aim to support) rather than disconfirm the hypothesis. Most demonstrations of this phenomenon have involved relatively abstract problems. The authors suggest that people use a positive test strategy in a more applied setting as well, that is, in computer software testing. In 2 experiments, they examined how Ss with varying expertise performed functional testing of software. There was substantial evidence of the use of a positive test strategy: Ss tended to test only those functions and aspects of the software that were specifically described in the specifications as what the software was supposed to do. This effect was only partially mitigated by increasing expertise among testers and by more complete program specifications. Reprinted by permission of the publisher. pubtype: Academic Journal doctype: Article src: R language: English refInfo: copyright: @attributes: flag: N holdings: @attributes: islocal: N |
|---|