menu search
brightness_auto
Ask or Answer anything Anonymously! No sign-up is needed!
more_vert
Type of errors and its priorities?  Who will handles these test scenario

7 Answers

more_vert
 
done_all
Best answer

In testing, it is important to prioritize errors based on their severity and impact on the functionally of the software. This allows testers to focus their efforts on the most important issues first, and to prioritize the resolution of critical defects over less significant issues.


Here are a few factors that may be considered when prioritizing errors in testing:


. Severity:

  The severity of an error is a measure of how seriously  it affects the functionality of the software. Errors that result    in the software crashing or failing to function at all are typically considered more serve than those that cause minor    issue or inconveniences.


. Impact:

   The impact of an error is a measure of how many users or processes are affected by the error. Error that impact a       large number of users or processes are typically considered more important than those that only affect a small           number of users or processes.


. Urgency:

  The urgency of an error is a measure of how quickly it needs to be fixed. Errors that have a high impact or that          pose  a risk to the software or users may need to be fixed as soon as possible, while less urgent errors may be          addressed at a later time.

thumb_up_off_alt 0 like thumb_down_off_alt 0 dislike
more_vert
Logical, syntax and not handled erros. The first one are the most important and less obvious one. Such errors can lead to incorrect work of software in some occasions that are not that easy to catch. It is sometimes very hard even to detect them. Not handled errors are less important and can be much easier to find. Syntax errors are the simpliest ones and can be very easy to detect during the programming process. The first two types is the responsibility of QA engineer. Third type is a matter of programmer.
thumb_up_off_alt 0 like thumb_down_off_alt 0 dislike
more_vert
These are software errors. The errors are priorities based on the necessity like high priority, low priority etc. It was defined in jira software while logging an error.
more_vert
Sanity testing is done.The priority classification are: Immediate – The bug should be resolved immediately. It is a production error, it required immediate resolution.

High - This bug should be resolved as soon as possible in the normal course of development activity, before the software is released. 

Medium – This bug should be repaired after serious bugs have been fixed.
thumb_up_off_alt 0 like thumb_down_off_alt 0 dislike
more_vert

In software testing, there are three main types of errors:

  1. High-priority errors: These are critical errors that affect the functionality of the software or prevent it from working altogether. Examples include crashes, data loss, security vulnerabilities, and other issues that significantly impact the user experience.

  2. Medium-priority errors: These are errors that affect the software's usability and performance, but do not necessarily prevent it from functioning correctly. Examples include UI glitches, slow response times, and other issues that can be worked around but still impact the user experience.

  3. Low-priority errors: These are minor errors that do not significantly impact the user experience. Examples include typos, formatting issues, and other cosmetic errors.

Test scenarios are typically handled by software testers or quality assurance professionals. They create and execute test cases that simulate different usage scenarios and try to identify as many potential errors as possible.High-priority errors will typically be addressed first, followed by medium- and low-priority issues.

thumb_up_off_alt 0 like thumb_down_off_alt 0 dislike
more_vert
Priorities of errors in testing can vary depending on the context, severity, and impact of the errors. Generally, critical errors that affect functionality and user experience take the highest priority, followed by major errors that impact performance or security, and then minor errors that have less impact on the system. It's important for testers to prioritize and report errors based on their potential impact on the overall quality of the system.
thumb_up_off_alt 0 like thumb_down_off_alt 0 dislike
more_vert
When testing software, it is important to prioritize errors based on their severity and potential impact. Generally speaking, errors should be prioritized from most severe to least severe. The most severe errors are those that can cause data loss or system crashes. These should be addressed first. After that, errors that can cause incorrect results or unexpected behavior should be addressed. Finally, errors that have a minor impact or are cosmetic should be addressed last. The person responsible for handling test scenarios will depend on the specific organization and their processes.
thumb_up_off_alt 0 like thumb_down_off_alt 0 dislike
more_vert
Priority is defined as the order in which the defects should be resolved. The priority status is usually set by the testing team while raising the defect against the dev team mentioning the timeframe to fix the defect. The Priority status is set based on end users requirement.
thumb_up_off_alt 0 like thumb_down_off_alt 0 dislike
Whenever you have a question in your mind, just drop it on Answeree. Help our community grow.
...