Categories

    Tags

Regression Testing?

Home Forums General Regression Testing?

This topic contains 6 replies, has 1 voice, and was last updated by Profile photo of Admin Admin 9 years, 9 months ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #2136
    Profile photo of Admin
    Admin
    Keymaster

    HI,

    How we can perform Regression Testing manully? i.e, There is no support of automation tools.

    Regards,
    Naveen

    #2137
    Profile photo of pvsimha
    pvsimha
    Participant

    Regression Testing …..

    First you have to find out the Depend Test cases for the Test case in which you found that Bug……

    Suppose if you found a bug while Testing the Withdrawal for a bank application.. ITs dependent Test senarios will be
    Balance…..
    Personal A/c details Screen.
    Mini statement Screen.
    Etc….

    You have to check all theses Screens after that Bug is fixed…

    This is an example…

    You have to think more logically for every scenario…

    Thats it

    #2138
    Profile photo of ashoksr
    ashoksr
    Participant

    Regression Testing: It could be defined as, executing the entire test cases adhocly after the bugs being fixed in the first iteration of the testing. This can be done on once the release candidate is decided or else on the most stable build ready to release to cross check there would not be any issues that are from the fix of defects or addition of new enhancements or it may be some missed out issues in the first iteration or execution of the testing.

    Thanks
    Ashok

    #2139
    Profile photo of tanu
    tanu
    Participant

    I would like to tell you about the link where u can get answers to your questions…below is the link…

    [url=http://www.onestoptesting.com/:39x2liz2]http://www.onestoptesting.com/[/url:39x2liz2]

    [b:39x2liz2]check out!!![/b:39x2liz2]

    #2140
    Profile photo of storniai
    storniai
    Participant

    If there is no support for test automation tools, then you should prioritize regression tests carefully. As mentioned earlier in this topic, one should use e.g. ad-hoc principles to identify the test cases that have highest probabilities to reveal errors. In general, the most effective way to accomplish this is probably re-running of the test cases that are linked somehow with the bug fixes and added functionality. In addition, to increace the confidence on the release canditate, one should check also the main areas of the unaffected code as well if there is time.

    In general, I would recommend that try to re-run all tests that covers the recently made changes to the code, but also re-run few test cases from the unaffected areas to increace the overall confidence on the software functionality.

    rgds,
    Sami

    #2141
    Profile photo of qualsoft
    qualsoft
    Participant

    Execute the related test cases after the bug is fixed.

    #2142
    Profile photo of softomania
    softomania
    Participant

    Execute the same test case on the various builds until the
    bug found is closed. It mustnt involve any tools.

    [url=http://softwareqatestings.com:vsx2rihw]Software testing tutorial[/url:vsx2rihw]

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.

New User?

Register
Do NOT follow this link or you will be banned from the site!