Bug Life cycle & Severity vs Priority

Bug Life cycle & Severity vs Priority and some other Software testing questions

Bug LifeCycle:
1. Tester will find and verify a valid bug
- Tester will assign the bug to a dev
2. Developer will analyze the bug and decide 1 of the following:
- Accept the bug (the bug is valid and will be fixed now)
- Defer the bug (the bug is valid, but will be fixed later)
- Reject the bug (the bug is not valid, and will not be fixed now or later)

3. If the Developer Accepts the bug, they will begin fixing the issue. Once fixed, Dev will assign the bug to the Tester for re-testing.

4. Tester will perform re-testing. If the re-testing fails, the bug is re-assigned to the devloper and we start again from Step 2.
- If re-testing passes, the test case is marked as passed and the bug is closed

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Severity vs Priority:
- Severity: The level of seriousness of this issue. The degree to which it impacts the application.
- Set by the Testers


- Priority: The order in which the bug/defect will be worked on. Determined based on the needs of the business as compared with other issues.
- Set set by Developers

-----------------------
Test strategy is a high-level document which defines the approach for software testing. It is basically derived from the Business Requirement document. Test strategy is developed by project manager or business analyst. It is kind of static document which sets the standards for testing so not updated often.
-----------------------------
A test strategy is an outline that describes the testing approach of the software development cycle. It is created to inform project managers, testers, and developers about some key issues of the testing process.
-------------------------
A Test Strategy document is a high level document and normally developed by project manager. This document defines “Software Testing Approach” to achieve testing objectives. ... However, for larger projects, there is one Test Strategy document and different number of Test Plans for each phase or level of testing.
-----------------------------
A TEST PLAN is a document describing software testing scope and activities. It is the basis for formally testing any software/product in a project. ISTQB Definition. test plan: A document describing the scope, approach, resources and schedule of intended test activities.
--------------------
What are software testing strategies?
The strategies describe ways of mitigating product risks of stakeholders in the test level, the kind of testing to be performed and which entry and exit criteria would apply. A software testing strategy is an outline which describes the software development cycle testing approach.
--------------------------
What is the entry and exit criteria?
Entry criteria for testing can be defined as “Specific conditions or on-going activities that must be present before a process can begin”. The Software Testing Life Cycle (STLC) specifies the entry criteria required during each testing phase.
----------------------------
What is the purpose of test strategy?
A test strategy is an outline that describes the testing approach of the software development cycle. It is created to inform project managers, testers, and developers about some key issues of the testing process.
-------------------------
What are testing techniques?
A software testing method in which the internal structure/design/implementation of the item being tested is not known to the tester. These tests can be functional or non-functional, though usually functional. Test design techniques include Equivalence partitioning, Boundary Value Analysis, Cause-Effect Graphing.
--------------------------