Output domain

De Software testing
Revisão de 17h58min de 8 de março de 2010 por Magsilva (discussão | contribs) (moved Output to Output domain)
(dif) ← Edição anterior | Revisão atual (dif) | Versão posterior → (dif)
Ir para: navegação, pesquisa

Concepts

Facts

  • The output domain may be infinite. <bib>vincenzi-etal:2007</bib>
  • The output domain may be too large. <bib>vincenzi-etal:2007</bib>
  • Outputs have similar variety as inputs. <bib>vincenzi-etal:2007:slides</bib>
  • Output can be thought of the data displayed on a computer screen. <bib>vincenzi-etal:2007:slides</bib>, <bib>delamaro:slides:2009</bib>
  • Output can be thought of the data sent to interfacing systems and to external devices. <bib>vincenzi-etal:2007:slides</bib>, <bib>delamaro:slides:2009</bib>
  • Output can be thought of the data written to files or databases. <bib>vincenzi-etal:2007:slides</bib>, <bib>delamaro:slides:2009</bib>
  • Output can be thought of the the state or the environment modified by the system’s execution. <bib>vincenzi-etal:2007:slides</bib>, <bib>delamaro:slides:2009</bib>
  • To decide whether the output is correct against the product specification, an oracle is needed. <bib>vincenzi-etal:2007:slides</bib>
  • The expected output of a product is determined by the tester's understanding of the requirements during testing. <bib>mathur:2008, 11</bib>
  • The observed output of a program is compared with the expected output to determine if the program functions as desired. <bib>mathur:2008, 12</bib>