SPONSORS:






User Tag List

Results 1 to 4 of 4
  1. #1
    Junior Member
    Join Date
    Jan 2002
    Posts
    12
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Testing functionalities that will make up a future application

    We have a software which will be made available only in a few months. I know the specs and I would like to start programming some black box tests. Is it possible? Does anyone have an idea?

    Thanks in advance.

  2. #2
    Member
    Join Date
    Oct 2001
    Posts
    93
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Testing functionalities that will make up a future application

    Without having the GUI in a relatively stable state I would not try to Automate any tests. However, as with all testing the first stage should be planning. If you have the specs then you can start creating test plans. Once you have a UI (even if it does not function) you can start autoamting the tests as per your plans.

    Hope this helps.

    Paul

    ------------------
    Paul Tucker
    Merit AT
    www.merit-at.com

  3. #3
    Senior Member
    Join Date
    Jun 2000
    Location
    Sunyyvale CA USA
    Posts
    422
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Testing functionalities that will make up a future application

    Good point.

    As all automation tools works on GUI objects. If you have some mockups atleast u can use them as starting points. But if you foresee any database testing then you can proceed further in building testcases based on db schema available to you.

    ------------------
    Sree
    Sree

  4. #4
    Junior Member
    Join Date
    Oct 2000
    Location
    Cambridge MA USA
    Posts
    10
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Testing functionalities that will make up a future application

    Another thought.
    As soon as you can, have your friendly developer give you a prototype/mockup version of the GUI.

    Try to automate against that.

    You may well find that there are things the developer is doing which make your testing harder. Often, especially early in the cycle, you can influence the developers to do things (eg put in identifiers or change some underlying structure/construct/control) which will make the test automation easier/faster/better. Or at the very least, you'll have a better idea how long it will take to test some pieces of the GUI.




    ------------------

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.0.9 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Questions / Answers Form provided by vBAnswers (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominatevBulletin 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 02:00 PM.

Copyright BetaSoft Inc.