SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 4 of 4
  1. #1
    Junior Member
    Join Date
    Mar 2004
    Location
    China
    Posts
    3
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    At what stages of Software Life Cycle be appropriate for black or white box testing?

    I'm new here and just begins the learning of Software Testing.

    I want to ask a question:
    At what stages of Software Life Cycle would be more appropriate for black box testing vs white box testing?

    And here's my opinion:
    I think white box testing is heavy used in the Unit level or Unit testing.
    And in the later integration testing and validation testing, black box testing is being used mostly.
    In short, at the stage of coding of Software Life Cycle, white box testing will be more appropriate.
    And after that (at what stage now?) black box testing is more appropriate?
    Just to say hi~

  2. #2
    Senior Member
    Join Date
    Apr 2001
    Location
    N. Mankato, MN
    Posts
    319
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: At what stages of Software Life Cycle be appropriate for black or white box testing?

    Remember that black box, grey box and white box are a type of testing. So these can all be used a various points in the SLC.

    Black box testing means that you don't know the internal working of the system. So this could be done in the requirements phase writing test cases or later once a module has been completed.

    Grey box testing means that you know some of the internal components of the system. So this could also be done in the requirements phase writing test cases or at the start of the design phase.

    White box testing means that you know the entire internals of the system, which allows you to test inputs/outputs, etc. This could also be done in the requirements phase writing test cases to test these inputs/outputs or at the start of the design phase.

    In short, as to the appropriate section on where to use black box or white box testing depends on culture and maturity of your organization because these 3 types of testing can be used throughout the entire lifecycle.

    I hope that helps! [img]images/icons/smile.gif[/img]

  3. #3
    Junior Member
    Join Date
    Mar 2004
    Location
    China
    Posts
    3
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: At what stages of Software Life Cycle be appropriate for black or white box testing?

    It's really helpful.
    Thank you very much~
    Just to say hi~

  4. #4
    Junior Member
    Join Date
    Aug 2002
    Location
    Marlton, NJ
    Posts
    3
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: At what stages of Software Life Cycle be appropriate for black or white box testing?

    I look at it from another point, White box testing when you have access to the code should be done by the team lead or BA before the coder is done with the module. Code reviews fall into this type of testing. The programmer was supposed to create module x that retrieves or updates or does what ever with or without parameters. Look at the code, does he do it, does it do what it is supposed to correctly, and will the next programmer understand what he did, how and why. This is after the programmer has done his unit testing, he may get it to work but if it breaks something or the next programmer will not understand how he did it - what good is it.

    Black box testing, for me, comes from functional specs, but is done when some functional area is complete, Sales entry, reporting, etc. The software was commissioned to do something, data entry, reporting, what ever. As a black box testor you don't care how it was done, just that it works. Does it take in the data, and produce the results. Does it do it in a timely manner, does it exchange messages with other systems or databases, without messing up, can it handle the absolute max amount of entries, transactions, hits or whatever. If you are doing black box testing, are you having your users do it, even if the software works if the users cannot/willnot change their business process to use it - it is no good, it must be useable as well as functional. Thats why prototypes are created as soon as possible. Functional specs are used to create test cases and those cover newly created software and any place that might be affected.
    If it does not pass the tests, and the test was created with valid criteria, the software is not done. Blackbox testing indicates if it works and is it useable, so when some functional area is complete it should be tested, before programmers move on to other areas or another project.

    PJH

 

 

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 10.71%
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 01:39 AM.

Copyright BetaSoft Inc.