Quality is delighting customers
Started Sep 20, 2012 0 Replies 0 Likes
In a large application, how can we track the customer changes? Is it good to use RTM to track the changes or any other tool available to track the changes? if RTM, how it can be tracked? Pls…Continue
Started this discussion. Last reply by sriram sundaram Sep 20, 2012. 5 Replies 0 Likes
If the system not responding to the request within the designed/developed time frame then its called...a. Failureb. Errorc. Mistaked. Fault Continue
Started this discussion. Last reply by Karthikeyan Sep 18, 2012. 4 Replies 0 Likes
Guys can you please answer the following...Which one is the following called Confidence Testing?a. Smoke Testingb. Sanity Testingc. Regression Testingd. System TestingContinue
Started this discussion. Last reply by Nagaraju.Velde Sep 6, 2012. 7 Replies 0 Likes
"What is Stress Testing and when its to be done in the application? Guys pls answer this..."Continue
© 2022 Created by Quality Testing.
Powered by
Comment Wall (11 comments)
You need to be a member of Quality Testing to add comments!
Join Quality Testing
Hi Karthikkeyan,
I am Lyn and currently working as Quality Analyst. I was searching for Software Metrics and came across your profile. As our company needs Software Product and Software Process metric and as ii am doing for first time. I need your help.
Thanks& Regards,
Lyn
Hello Karthikeyan,
Many Many Happy Returns of the Day & Hope all "UR" wishes comes true by GOD's Grace ............enjoy !!! TC GOD BLESS U ALLLLLL
Thanks & Regards
Kapil
kapildevkapoor@gmail.com
+919326814689
Hello Karthikeyan,
Many Many Happy Returns of the Day & GOD Fulfill ur Dreams ............enjoy !!! TC GOD BLESS U ALLLLLL
Thanks & Regards
Kapil
kapildevkapoor@gmail.com
+919326814689
Hello,
regarding your question:
Priority:
1-Fix ASAP
2-Fix Soon
3-Fix if Time
Severity
1-Crashes System
2-Major Bug No Workaround
3-Major Bug With Workaround
4-Trivial Bug
1) low priority & low severity: a typo in the installation manual
2) low priority & high severity: When applying a very complicated and unlikely scenario, the server crashes
3) high severity & high priority: When applying a very common and likely scenario, the server crashes
4) high severity & high priority: same as point 3 (?)
kr
Hey,
Inspection:
Objective: Fine anomales, verify resolution, verify product quality
Desicion-making: Review team choose predefined product dispositions; defects must be removed
Change Verification: Leader verifies that action items are closed; change verification left to other project controls
Groupsize: Three to six people
Group Attendance: Peers meet with documented attendance
Group leadership: Trained facilitator
Presenter: A reader
Output: Anomaly list; anomaly summary; inspection document
WalkThrough:
Objective: Fine anomalies; examine alternatives, improve product, forum for learning
Decision-making: The team agrees on changes to be made by the author
Change Verification: Leader verifies the action items are closed; change verification left to other project controls
Groupsize: Two to seven people
Group attendance: Technical leadership and peer mix
Group leadership: Facilitator or author
Presenter: Author
Output: Anomaly list; action items; decisions; follow-up;Jast have a lool...
http://en.wikipedia.org/wiki/Risk_management
If you have further questions - just PM me!
Hi karthi,
Surely I will inform you the required Openings here...
Regards,
Gaurav.
Hi
hows u
Hello Karthikeyan,
Happy Republic Day n Welcome to QT..............enjoy Testing!!! TC GOD BLESS U ALLLLLL
Thanks & Regards
Kapil
+919326814689
View All Comments