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
    Aug 2007
    Posts
    2
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Differentiating ChangeRequest with Bug during test

    While conducting the testing we come across a situation in which we identifies some missing requirements in FS document, In order to cope up with this we creates a change request so that FS document can be updated. I think this violates the process. I have proposed some changes in the current process.

    Since Requirements are essential part of system in case if they get missed, it should not be cater as Change Request. If bugs is identifies in FS document then A Bug should be address to Business analyst team they should make correction in Document and then QA will close the Bug with FS updated status. Now for Development team a separate Change Request will be initiated So that they can proceed with the development against that Bug.

    Quality-assurance team will log change request for FS, In case if there are some new functionalities or feature needs to be added in System. Please Provide your feedback in this regard as i am unable to build a mutual Consensus among my colleagues on this issue. [img]/images/graemlins/confused.gif[/img]

  2. #2
    Junior Member
    Join Date
    Dec 2011
    Posts
    7
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Differentiating ChangeRequest with Bug during test

    Formally speaking you would create a change request if a change is needed in the system scope that is not currently in the requirements. So only if both the requirements and the system need to be changed, otherwise you could create a bug against the system or against the low level documentation.
    Then normally it would go thru the change board who will decide on it and a positive decision would initiate the change in the documentation(there might be more than one document that need to be changed) and the development.
    An important point here is that you would not change the requirements documentation before it is decided if the CR will be accepted or not.

    But ofcourse the details of this process could really be different depending on the organization and especially the roles in the organization so it's not really that simple to identify the best process here. Just use the simplest process possible without going against the fundamentals.

  3. #3
    Member
    Join Date
    Sep 2008
    Location
    India
    Posts
    394
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Differentiating ChangeRequest with Bug during test

    In simple words:

    1. Bug - When the application doesn't behave as per requirements.
    2. Change request - When there is some additional requirement to be added or if there is a modification to the existing requirement.
    Best Regards,
    Sanket Vaidya

    Om - Effortless Text Generation http://sourceforge.net/p/omfortesting/home/description/

  4. #4
    Member
    Join Date
    Jul 2011
    Posts
    63
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Differentiating ChangeRequest with Bug during test

    If QA finds a gap in requirement then it should be added as a bug and assigned to BA's. Once the issue is resolved i.e. BA's update document and correct the requirement then QA should close bug. And then a change request can be initiated for Dev team.

    IF QA feels that a particular requirement is correct but can be changed to have a better quality application/end product then it should be first discussed with BA's if they are Okay with the suggestions then a change request would do the needful. BA's should update the req doc in that case a change req should be initiated for Dev team.
    _____________________
    Regards,
    mbalajiwale

 

 

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 06:08 AM.

Copyright BetaSoft Inc.