SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 8 of 8
  1. #1
    Senior Member
    Join Date
    Jun 2008
    Location
    The Land of Snake Charmers
    Posts
    212
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Smoke and Build Verification Testing

    Hi

    What would be the distinguishing factors between Smoke testing and Build Verification Testing?

    I "think", Build Verification Test is performed by developers ONLY, however Smoke testing may be performed by either developers or testers?

    Am I correct in my assumption?

    Please share thoughts? (if possible, please refer to online sources/authors/books)

  2. #2
    Moderator
    Join Date
    Sep 2001
    Location
    Yankee Land
    Posts
    4,055
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Smoke and Build Verification Testing

    Why not check out the previous threads on Smoke Testing and Build Verification and see if what you know is covered there?
    - M

    Nothing learns better than experience.

    "So as I struggle with this issue I am confronted with the reality that noting is perfect."
    - Unknown

    Now wasting blog space at QAForums Blogs - The Lookout

  3. #3
    Senior Member
    Join Date
    Mar 2007
    Location
    Waterloo, Ontario, Canada
    Posts
    3,628
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Smoke and Build Verification Testing

    You've got the right idea, yes. They are essentially the same with the exception that BVT is usually conducted at a development level. That doesn't mean it is never performed at a QA level, though. This will all boil down to organizational setup and policies.
    Brent
    --------------------
    9 out of 10 people I prove wrong agree that I'm right. The other person is my wife.
    --------------------

  4. #4
    Member
    Join Date
    Dec 2006
    Location
    Montréal, Québec, Canada
    Posts
    91
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Smoke and Build Verification Testing

    Hi

    I agree with Brent.

    BVT is usually performed at development.
    It can be done by the developers themselves or by automates (i.e, automatic build management tool).

    In both cases, it doesn't mean that QA can not perform this task.

    It is up to customer's policies and project's processes.

    Robin
    There is no age to learn.
    And life is an learning adventure.

  5. #5
    Senior Member
    Join Date
    Sep 2008
    Location
    Neverland
    Posts
    947
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Smoke and Build Verification Testing

    Hi.. please go through these links

    http://techiecorner.blogspot.com/200...sting-and.html

    http://www.softwaretestinghelp.com/s...ng-difference/

    Build Verification Testing is AKA Sanity testing

    Regards,
    Tinker
    Regards,
    Tinker

    "The most wasted of all days is one without laughter."
    -e e cummings

  6. #6
    Apprentice
    Join Date
    Jul 2008
    Location
    Australia
    Posts
    46
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Smoke and Build Verification Testing

    BVT is usually done by developers but most organisations prefer testers to do this. In my previous work i was responsible for setting up the test environment and installing build.

    A smoke test is a cursory examination of all of the basic components of a software system to ensure that they work

  7. #7
    Apprentice
    Join Date
    Oct 2013
    Posts
    44
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0
    Hi,

    I agree with Brent.......
    Smoke testing is done by QA...and the BVT should done by Developer only, either manual or by automatic(by using build management tool)

  8. #8
    Member
    Join Date
    Feb 2016
    Posts
    131
    Post Thanks / Like
    Blog Entries
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0
    Build Verification test is an arrangement of tests keep running on each new form to confirm that build is testable before it is discharged to test group for further testing. These experiments are core functionality test cases that guarantee application is steady and can be tried altogether. Normally BVT procedure is robotized. In the event that BVT fizzles that assemble is again get doled out to designer for fix.There has dependably been a civil argument in the product testing industry on the most proficient method to pass a work for testing. Straightforward and straightforward we utilize BVT/Smoke testing to check the wellness of incorporate with the test environment.
    Last edited by brknny; 03-16-2016 at 05:27 AM.

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 7.89%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 11:59 PM.

Copyright BetaSoft Inc.