SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 7 of 7
  1. #1
    Member
    Join Date
    Dec 2003
    Location
    India
    Posts
    65
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Dividing a functionality into silk test cases

    Hi,
    I am testing a web application.
    A functionality of the application navigates thru several pages and does many actions on those pages and verifies the results of those actions.
    The manual testing test case is a single test case for this entire navigation and verification.
    What is the best practice while automating this functionality? Integrating all these steps into a single test case or dividing into multiple testcases and running all test cases from suit file or test plan??
    Can any one suggest me???

    Thanks in Advance
    San Tony
    <img border=0 title= alt=[Smile] src=smile.gif /] =================================
    Do not drive faster than your Guardian Angel can fly

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

    Re: Dividing a functionality into silk test cases

    Hi Tony,

    Always it is better to write smaller test cases. Smaller test cases are easier to maintain(debugging, modifying....). Call series of test cases from a test plan. So that you will have the flexibility to run failed test cases and you can merge the results.
    Bapanna Setti.K

  3. #3
    Member
    Join Date
    Dec 2003
    Location
    India
    Posts
    65
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Dividing a functionality into silk test cases

    Hi,
    Thanks for ur helping info....

    Regards
    San Tony
    <img border=0 title= alt=[Smile] src=smile.gif /] =================================
    Do not drive faster than your Guardian Angel can fly

  4. #4
    Senior Member
    Join Date
    Jul 1999
    Location
    Bellingham, WA USA
    Posts
    1,323
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Dividing a functionality into silk test cases

    In addition to that, you generally don't want to have Automated Test B depend on the success of Automated Test A. If each of these can be independently verified you will be better off and have far less frustration. Having long, multi-step processes in a single automated run is an invitation for this type of frustration.

  5. #5
    Advanced Member tonymro's Avatar
    Join Date
    Jul 1999
    Location
    Deep in the Coast Range Mountains of Oregon, USA
    Posts
    562
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Dividing a functionality into silk test cases

    The manual testing test case is a single test case for this entire navigation and verification
    <font size="2" face="Verdana, Arial, Helvetica">This is a problem I have encountered on almost every test automation project... improperly scoped and badly designed manual test cases. Usually, the project has an aggressive (and unrealistic )schedule, SQA management assumes that they can hand you a set of poorly designed test cases that can be turned into an automated solution in fairly short order.

    A properly designed and scoped test case will have a well defined base state, a properly scoped set of input stimuli, and a clear set of measurable expected results. And, as DJGray pointed out, each test case should be independent of any other test case.
    Sr. Software Test Automation Architect

  6. #6
    Member
    Join Date
    Dec 2003
    Location
    India
    Posts
    65
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Dividing a functionality into silk test cases

    Hi DJGray/TonyMro,
    Thanks for ur views.
    But the problem here is the functionality is dependent on one another. If one step is success, then only i'll get some thing in the next page and i'll get expected results. If the application fails to give expected results in one step, the remaining steps need not to be executed. That is why the manual testing test case was created as a single test case.
    I think it is better to devide the test case into multiple testcases and execute one by one depending on the result of the other.
    What is your suggestion on this??

    Thanks in Advance
    San Tony
    &lt;img border=0 title= alt=[Smile] src=smile.gif /] =================================
    Do not drive faster than your Guardian Angel can fly

  7. #7
    Senior Member
    Join Date
    Feb 2000
    Posts
    1,497
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Dividing a functionality into silk test cases

    You could run the testcases from a loop which checks the value of GetTestsFailedCount() after each one to determine whether to continue or stop.

    OR just rewrite TestCaseExit() to recognize a bException and exit the script.


    John

    [ 04-06-2004, 07:30 AM: Message edited by: John J. Miller ]

 

 

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.00%
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 03:38 AM.

Copyright BetaSoft Inc.