Jump to content

Talk:Acceptance testing

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Chris Pickett (talk | contribs) at 06:09, 4 December 2006 (create merge discussion). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Please review and comment or edit.

Rsutherland 07:07, 7 June 2006 (UTC) I don't think these are the same. I design production functional test and test systems all the time, and I consider it to be a black box test method (hardware). For example a functional test is not a bata test, however a bata test may be functional or a white box method. Can we nuke this entire page and start over without trapping all the links to it?[reply]

The Reality Is

Rsutherland: All of these terms have been used in lieue of "acceptance test' at one time or other. Any test the sponsor is willing to sign off on is, by definition, an "acceptance test." If you want to add or extend the definition of any of these terms on this or another page, please do so. I see no reason to nuke the definition. You object precisely to— what? In practice, there are no clean definitions of anything— would it were not so! normxxx| talk email 05:50, 9 June 2006 (UTC)[reply]

Rsutherland 16:54, 10 June 2006 (UTC) kk, No nukes! I want to try some more ping's: I have always thought functional test methods were used for all sorts of things from reverse engineering, to checking scientific theory's. Any thoughts on that? I mostly work with electronic hardware (analog, power, and micro-controllers). To test these types of products there is a few consistent methods that may (or not) be nice to have in an encyclopedia, is this a good place?[reply]

Stephiee01 18:03, 16 August 2006 (UTC) As this relates to software testing environments, as previously stated, any test that can be used as an official sign off can be considered an acceptance test. Another key point to an acceptance test is that its execution is in a controlled environment, whereas, if a developer was running the same tests on his workstation, it would not be considered as an official sign off. Acceptance tests are typically run against customer/SRS type configurations that have been approved for the release for validation of its ability to run/function correctly in the pre-determined environment(s).[reply]

In terms of hardware engineering testing practices, I would add a section to the Acceptance Test page labeled as such, and link it to more relevant pages that talk about hardware engineering testing practices, should any exist.

Merge from User Acceptance Test

I think the two articles are covering the same subject matter. --Chris Pickett 06:09, 4 December 2006 (UTC)[reply]