Answer Posted / suneela
Its just like mediator between Development team and testing
team where we can store all the issues
Testing team will store the data like
1:issues with screen shots
2:criticality
3:Date/Time
4:Name of tester
5:Work request ID
ect
Dev team will store
1:what is the fix (code issues/data issue ..)
2:Date/Time
3:Name of person
4:Update the status as fixed
Once the issue is moved to "Fixed Queue" and code was
deployed in test env ..tester will test which are in fixed
queue and again update the status like
1:whether it is passed or failed ..if it is passed ,issue
is closed and if it failed again reroute to Development
Queue
This is the circular process between Dev and testing
team ..whenever queues are updated an automated emails will
generate to entire team which is useful to know the status
with in less time
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
what are all the things we will include in " what to be tested and what not to be tested" in Test Plan
what types of bugs will we find out in banking projects
What is test out put?
What is bug leakage?
How soon the bug should get fixed?
What is the difference between authentication and authorization in web testing?
How do you know the code has met specifications?
Explain briefly your project.
What is sanity?
explain fish model in detail?
What do you mean by Unit Testing, Integration Testing, System Testing, and User Acceptance Testing and when do you do them?
What Is risk Based testing?
List out test deliverables?
explain ur testing project? how can u nexplain . what should we explain ? i have not worked on any project?
What is known as data-driven testing?