Chetan Rakheja’s Post

View profile for Chetan Rakheja, graphic

Automation Test Engineer At Orange | ISTQB Certified Tester | FinTech | Automation Tester | QA | SDET | Appium Automation | Selenium Automation | API Tester | I write code to test the code.

Breakdown of Severity & Priority for SDETs: Understanding the severity and priority of issues is crucial for Software Development Engineer in Test (SDET) roles. Here is a breakdown to guide you: - Severity: Reflects the impact of an issue on the system/application. - High: Critical defects causing system crashes, data loss, or security breaches. - Medium: Issues affecting important functionality but with workarounds. - Low: Defects with minimal impact or cosmetic in nature. - Priority: Evaluates the impact on business associated with the application. - High: Demands immediate attention to prevent business disruption. - Medium: Requires timely addressing but not immediate action. - Low: Can be handled at a later stage. Examples: 1) High Priority and High Severity: Critical bug preventing users from logging in. 2) High Priority and Low Severity: Typo in the application's welcome message. 3) Medium Priority and Medium Severity: Bug hindering profile picture uploads. 4) Low Priority and High Severity: Security vulnerability compromising user data. Follow Chetan Rakheja for more such amazing notes and content. Understanding these distinctions helps prioritize issues effectively in SDET roles. #SDET #SoftwareTesting #Severity #Priority #AutomationTesting

Aditya Sethi

Talks about #datavisualisation, #analytics, #datascience, #dataengineering, #webscrapping and #machinelearning. Github :- Github.com/adityasethi-in. | R programming | Python programming | Power BI | SQL | Airflow

4mo

Useful tips

Like
Reply

To view or add a comment, sign in

Explore topics