Home > Archive > Software Testing > September 2006 > Difference between smoke test and build acceptance test?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Difference between smoke test and build acceptance test?
|
|
| peyo2@o2.pl 2006-09-25, 4:18 am |
| Hi all,
Can you explain the difference between smoke test and build
acceptance test? Are they synonymous?
Thanks and Regards,
Peter
| |
| ifernandez.redsauce@gmail.com 2006-09-25, 7:06 pm |
| User Acceptance Tests
This is a suite of tests that demonstrates to the client (the user)
that the object of the testing is able to accomplish the tasks it was
designed for, at least in a minimum way.
Smoke tests
It is a small (and usually fast in time) subset of tests executed over
the product just to ensure that it works in a first instance. Usually,
a smoke test is executed just after a build. If the smoke test is not
passed, the QA team should be capable of rejecting this version of the
product.
Hope this be helpful :)
Iv=E1n Fern=E1ndez
QA Manager
www.redsauce.net
| |
| James Bond 007 2006-09-25, 7:06 pm |
|
<peyo2@o2.pl> wrote in message =
news:1159179862.941370.189790@d34g2000cwd.googlegroups.com...
> Hi all,
>=20
> Can you explain the difference between smoke test and build
> acceptance test? Are they synonymous?
>=20
> Thanks and Regards,
>=20
> Peter
I think they are synonymous. Another term you will see is basic sanity =
test. It is a very short and quick suite of tests (maybe only 1 or 2 =
tests) that verify that the build was good, the system is stable and =
that it can be used for further development and testing efforts.
|
|
|
|
|