✰ When a tester finds a bug .The bug is assigned with new or open status.
✰ The bug is assigned to development project manager who will analyze the bug .He will check whether it is a valid defect. If it is not valid bug is rejected, now status is rejected.
✰ If not, next the defect is checked whether it is in scope. When bug is not part of the current release such defects are postponed.
✰ Now, Tester checks whether similar defect was raised earlier. If yes defect is assigned a status duplicate.
✰ When bug is assigned to developer. During this stage bug is assigned a status in-progress.
✰ Once code is fixed. Defect is assigned with fixed status.
✰ Next the tester will re-test the code. In case the test case passes the defect is closed.
✰ If the test case fails again the bug is re-opened and assigned to the developer. That's all to Bug Life Cycle.
Concern with functionality of application. It deals with the impact of the bug on the application.
Concern with application from the business point of view.
It answers: How quickly we need to fix the bug? Or How soon the bug should get fixed?
✰ High Priority and Low Severity:
Company logo is not properly displayed on their website.
✰ High Priority and High Severity:
Suppose you are doing online shopping and filled payment information, but after submitting the form, you get a message like "Order has been cancelled."
✰ Low Priority and High Severity:
If we have a typical scenario in which the application get crashed, but that scenario exists rarely.
✰ Low Priority and Low Severity:
There is a mistake like "You have registered success" instead of successfully, success is written.
Bug release is when a build is handed to testing team with knowing that defect is present in the release. The priority and severity of bug is low. It is done when customer want the application on the time. Customer can tolerate the bug in the released then the delay in getting the application and the cost involved in removing that bug. These bugs are mentioned in the Release Notes handed to client for the future improvement chances.
Regression Testing: When changes in the code of the software are made to fix the previous bug. Then testing needs to be perform to ensure that it will not generate a new bug in the application and it works as specified and that it has not negatively impacted any functionality that it offered previously.
Regression Testing is important because of following reason:
✰ That the application works even after the alteration in the code were made.
✰ The original functionality continues to work as specified even after doing changes in the software application.
✰ The alteration to the software application has not introduced any new bugs.
✰ Frequency of use of test case.
✰ Time Comparison (automated script run much faster than manual execution).
✰ Re-usability of Automation Script.
✰ Adaptability of test case for automation.
✰ Exploitation of automation tool.
✰ Application should be stable enough to be tested.
✰ Testing always under time constraint.
✰ Understanding requirements, Domain knowledge and business user perspective understanding.
✰ Which tests to execute first?
✰ Testing the Complete Application.
✰ Regression testing.
✰ Lack of skilled testers.
✰ Changing requirements.
✰ Lack of resources, tools and training.
It is a number given to install-able software that is handed over to customer by the developer or tester. The information of build, release and version are displayed in software help page. Using this build and release customer can let the customer team know which release version build thet are using.
It is a number given to installable software that is given to testing team for testing by the development team. Build number assigned are incremental and sequential.
✰ QA team is responsible for monitoring the process to be carried out for development.
✰ Responsibilities of QA team are planning testing execution process.
✰ QA Lead creates the time tables and agrees on a Quality Assurance plan for the product.
✰ QA team communicated QA process to the team members.
✰ QA team ensures traceability of test cases to requirements.
✰ Purchasing the license of tool (QTP, selenium, QC, LR).
✰ Lack of skilled Tester to run the tool.
✰ Expectation that automated tests will find a lot of new defects.
✰ Maintenance of automated tests.
✰ Technical problems of tools.