Skip to main content

Severity vs. Priority



Severity  vs. Priority:
Severity - “Seriousness of a Defect”
  • Showstopper – the most serious concern like a system crash, Corrupted data etc.
  • Critical – A significant concern (broken functionality without a workaround).
  • Major – A concern due to broken functionality but has a Workaround.
  • Minor – A lesser concern (broken functionality with a workaround).
  • Trivial – An insignificant concern (cosmetic).
Priority - “Importance of a Defect”

  • Urgent – Highly visible and/or stops all project efforts
  • High – Stops some project efforts (and no workaround exists)
  • Medium – Slows project efforts (but a workaround exists)
  • Low – Barely visible and/or does not affect project efforts
Severity
Priority
Severity is used to determine the IMPACT of the defect on the application.
Priority is used to signify the LEVEL OF URGENCY of fixing the defect
It’s like Effect of defect on application
It’s like how soon the defect has to be fixed.
It is defined by Software Tester
Initially defined by Tester and Finalized by Project/Tech Manager
Ranges from Show stopper to Cosmetic defect
Ranges from Urgent to Low

Defect Categorization

Category
Definition
Example
High Severity
High Priority
A bug that corrupts the database, A bug results in 404 Error etc
Lift stops at 34th floor instead of 30th floor
High Severity
Low Priority
Application crashes due to weird testing, Crashes after 4000 sessions due to improper maintenance.
Banking site expiry screen
Low Severity
High Priority
Client names and Designations are placed one for the other, Blunder spelling mistakes etc
 Switching on the fan switches the lights as well.
Low Severity
Low Priority
Grammatical errors, Alignment issues, Some cosmetic issues are examples.
 ABC.com is shown as abc.com.

Comments

Post a Comment

We appreciate your valuable Suggestions/Feedback

Popular posts from this blog

Key Points of Leading RPA Tools

Key Points of Leading RPA Tools Automation Anywhere(AA) Blue Prism(BP) UI Path Developer friendly tool RPA Term was invented by Blue Prism Extremely User Friendly Offers Front and Back Office Robots It is an Enterprise grade RPA Solution tool Implementation Speed is high Script based, More Programming Skills required Supports only Back Office robots Re Usability is more since various integrations available with different workflows Smart Recorder Option available Code Insertion is difficult and not user friendly Free Community edition (PDF’s, Videos available for FREE) AA Bots can deploy in Physical Front Office machines & Cloud Extreme control over activities (Object Creation, Coding etc.) Con is - No Coding Annual support cost and license cost is higher What is Best RPA Tool...
4 comments
Read more

Types of Recording

Types of Recording: 4 types of recording modes are available Ø   Basic Ø   Desktop Ø   Web Ø   Citrix 2 ways of Recording Ø   Automatic Ø   Manual Basic – generates a full selector for each activity and no container, the resulted automation is slower than one that uses containers and is suitable for single activities. Desktop – suitable for all types of desktop apps and multiple actions; it is faster than the Basic recorder, and generates a container (with the selector of the top-level window) in which activities are enclosed, and partial selectors for each activity. Web – designed for recording in web apps and browsers (supported: Internet Explorer, Google Chrome), generates containers and uses the Simulate Type/Click input method by default. Citrix – used to record virtualized environments (VNC, virtual machines, Citrix, etc.) or SAP, permits only image, text and keyboard automation, and requires explici...
Post a Comment
Read more

HELLO WORLD

As of now, you've learned some basics of RPA & UI Studio . Now, It's a time to create your first program (Obviously " HELLO WORLD ") in UI Studio as below. Creating a New Sample Project : Here I’m displaying HELLO WORLD along with User Input with Flow Chart workflow 1)        Open UI Path studio 2)        On the Start tab, under the New section, click Blank . The New Project window is displayed. 3)        Enter NAME for the Project (say HELLOWORLD) & Select Project Location and Click on CREATE button. New Project (Main.xaml) is created in Chosen Location. 4)        Add/Drag and Drop any workflow/activity (like Flowchart) from Activities Panel 5)        Add Input Dialog activity 6)        Connect Input Dialog activity to Start node by selecting ‘Se...
1 comment
Read more