• DocumentCode
    2340681
  • Title

    End-to-end integration testing

  • Author

    Paul, Raymond

  • Author_Institution
    OASD C3I Investment & Acquisition, Dept. of Defense, Washington, DC, USA
  • fYear
    2001
  • fDate
    2001
  • Firstpage
    211
  • Lastpage
    220
  • Abstract
    Testing is still the primary means for ensuring software quality. In spite of more than 20 years of research in testing, most testing techniques still focus on module testing and white-box testing. However, in practice, integration testing and functional testing have been found to be most useful and effective. To respond to this need, the DoD recently initiated a project on End-to-End (E2E) integration testing. This approach takes the functional approach to integration testing even though design and architecture information can also be incorporated into the test specification. This approach also allows risk analysis, test case/script generation, regression testing, ripple effect analysis, statistical analysis, and remote project management and collaboration via XML
  • Keywords
    formal specification; program testing; project management; risk management; software quality; statistical analysis; DoD; E2E integration testing; XML; architecture information; end-to-end integration testing; functional approach; functional testing; integration testing; regression testing; remote project management; ripple effect analysis; risk analysis; software quality; statistical analysis; test case/script generation; test specification; testing techniques; Collaboration; Investments; Java; Object oriented modeling; Project management; Risk analysis; Software quality; Software testing; Statistical analysis; System testing;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    Quality Software, 2001. Proceedings.Second Asia-Pacific Conference on
  • Conference_Location
    Hong Kong
  • Print_ISBN
    0-7695-1287-9
  • Type

    conf

  • DOI
    10.1109/APAQS.2001.990022
  • Filename
    990022