Regression testing pbi in Azure board

-
Regression testing a Product Backlog Item (PBI) in Azure Boards involves retesting the PBI after changes have been made to ensure that the new changes have not introduced any new defects or issues. Here are the general steps to perform regression testing on a PBI in Azure Boards:

1. Identify the PBI to be tested: Select the PBI that has been modified or updated and needs regression testing.

2. Understand the scope of changes: Review the changes made to the PBI, including code changes, feature enhancements, bug fixes, etc.

3. Create test cases: Based on the scope of changes, create or update test cases to cover all the scenarios that need to be tested for regression.

4. Execute test cases: Execute the test cases on the updated PBI to verify that the changes have been implemented correctly and that existing functionality has not been impacted.

5. Report defects: If any defects are found during regression testing, report them in Azure Boards and track them to resolution.

6. Re-test: After defects have been fixed, re-run the regression tests to ensure that the issues have been addressed and no new defects have been introduced.

7. Update test documentation: Finally, update the test documentation to reflect any changes made during regression testing.

By following these steps, you can effectively conduct regression testing on a PBI in Azure Boards to ensure the quality and stability of your software product.

Comments

Post a Comment

Popular posts from this blog

What Does a SM-SCRUM MASTER do “All the Day”

-
What Does a SM-SCRUM MASTER do “All the Day” ·         Facilitate the Daily Scrum (Timeboxed) o    Facilitate the Daily scrum meetings for the team and maintaining the time box ·         Arrange the Follow-up meetings o    Arrange the follow-up meetings for the detailed discussion after the daily scrum meeting, if anything is raised in the daily scrum meeting ·         Meeting with the PO – PRODUCT OWNER o    To arrange the meeting with the PO to support the Backlog creation and the Road Map preparation ·         Facilitating the SCRUM EVENTS   o    such as – BACKLOG REFINEMENT, SPRINT PLANNING, SPRINT REVIEW AND SPRINT RETROSPECTIVE meetings. ·         Meetings with the Team’s Manager                     o  SM will have the meetings with the Team’s manager to discuss about the people’s issues, Trainings etc. ·         Contribute to Community of Practice o    SM with communicate with the other SM’S and contribute to the Agile community of practice in the company
Read more

When to choose scrum and when to choose kanban? Explained with examples

-
Scrum and Kanban are two popular frameworks used in Agile project management. The choice between Scrum and Kanban depends on the nature of the project and the team's preferences. Here are some examples of when to choose Scrum and when to choose Kanban: When to choose Scrum: 1. Complex projects with evolving requirements: Scrum is suitable when the requirements of a project are likely to change during the development process. It allows for flexibility and iterative development with regular feedback loops. Example: Developing a new software product where the requirements are not fully known initially. The Scrum framework enables the team to adapt to changing customer needs and deliver a more satisfactory product. 2. Projects that require rigorous planning and structured timelines: Scrum is beneficial when a project requires a strict timeline and frequent checkpoints for progress assessment. The framework provides a clear structure for planning and organizing work. Example: Building a
Read more

Kanban board setup for AMS teams in SAP

-
To set up a Kanban system for AMS teams in SAP, you can follow these steps: 1. Define the workflow: Understand the specific stages involved in the AMS (Application Management Services) process. This can include stages like ticket creation, assignment, analysis, development, testing, deployment, and closure. Determine the sequence and dependencies of these stages. 2. Create Kanban columns: Map each stage of the AMS process to a separate column on the Kanban board. For example, create columns like "To Do," "In Progress," "In Review," "Ready for Deployment," and "Completed." 3. Define work item types: Classify the types of work that the team will handle. This can include different types of tickets or tasks like bug fixes, enhancements, or system configurations. Assign a specific color or label to each work item type. 4. Set WIP limits: Establish work-in-progress (WIP) limits for each column to avoid bottlenecks and promote smooth flow. Def
Read more