🖌️
Product Process Documentation
  • Product Process Documentation
  • Definition of Done (DoD)
    • General checkpoints
      • Specific checkpoints by team
    • Important process: QA review & PO review
      • QA Review
      • PO Review
  • Work Items
    • Product Backlog Item (PBI)
    • Bug
      • Basic rules for creating a bug
      • How to report a Bug
    • Bugs Management
  • Code Standards
  • Different Test Levels
    • Unit Test
      • Frontend Unit Testing
        • What is a Unit Test?
        • How do I know if I am developing a good unit test?
        • AAA (Arrange, Act and Assert)
        • Overloaded test suits
        • Setup & Teardown
          • JEST Mocks
          • FakeTimers
        • Istanbul Annotations
        • C8 Annotations
        • JEST Runner (Debug unit tests with Jest)
    • Component Test
      • Frontend Component Testing
        • What is Component Testing?
        • Best practices
        • Bad practices
        • Setup
          • Sandbox
          • Mocks, Services and Providers
          • Test scenario
    • Integration Test
      • Frontend Integration Testing
        • What is a Integration Test?
        • AAA (Arrange, Act and Assert)
        • Best Practices
        • Bad practices
        • Setup & Teardown
        • How to create a scenario
          • Create the migrated app
          • Add to project
        • How to debug
        • Common problems
      • Testing Driven Development Guide and recommendations
    • Functional Test
    • Security Testing
      • Security Testing Tools
      • Frontend Security Testing
    • Performance testing
    • Best Practices
    • Test Documentation
  • Run test projects
    • General steps
    • Specific steps by team
  • DevOps
    • Pipelines
    • Builds
    • Specific information by team
    • Test plan
    • Service Hooks for Azure DevOps Notifications
      • Slack Notifications
      • Microsoft Teams Notifications
  • Dashboards
    • General
    • QA Dashboards
  • Release Process
    • General Steps
    • Specific steps by team
  • Migration Cells
    • Basics of testing process
  • Release process
  • References
Powered by GitBook
On this page

Was this helpful?

  1. DevOps

Test plan

This section will explain how to add steps in the test plan. The purpose of this is that anybody can be able to understand what is the test do.

PreviousSpecific information by teamNextService Hooks for Azure DevOps Notifications

Last updated 3 years ago

Was this helpful?

What is the test plan?

In DevOps Test Plans for Azure, we develop and use the test plans for automated and manual testing. Include the development, quality assurance, and business analysis team to attach test cases. We can run tests on all the requirements created by each team. Different teams and their views contribute to the testing workflow, adding to the capability of testers.

General steps

  • First, open the test project, update the project with the last version (git pull) to ensure that we have the last changes and then, run the all-test methods. If something is wrong, we have to fix it or talk with the team members asking if a change caused a regression if one change did a regression.

  • Second, we are going to add the steps in one of the test methods that doesn’t have or in a new test method. In this point we have to go into the and add a new test case, we can do it through this button:

If we don’t have the option as shown in figure 9, we just have to click on New work item, choose it and pin it. Then a dialog box like the following will appear:

We need to add a title related to the test method in our respectively project, then add the tags, if it is necessary (this is important because queries use these tags to put every single test case in one specific folder). Ask for DevOps or SDET members If we do not have knowledge about the tags, area and iteration. After that, we put the state in Ready, click on Save & Close button and move on into the area path that the test case was saved. We will see other test cases like this:

  • Third, click on our test case and a dialog will appear like this:

​In this case, the dialog has all information related to the test method. Now, we must add all steps that the test method does. We click on this option:

  • Finally, we will see the steps section and we can add all steps related to the test method, like this:

  • To associate a test method with a test case we just need to copy the id in the test case which is the following:

We press right click in our specific method, then click on Associate to Test Case as follows:

​Last but not least, we copy the id (as we saw in figure 15) in the input as follows:

​

Figure 10: Test case dialog
Figure 11: Test cases in the Test Plan
Figure 12: Test case dialog
Figure 13: Maximize steps button
​Figure 14: Steps section
Figure 15: Id test case
Figure 16: Associate to test case
Figure 17: Input associated with a test case
test plan
Figure 9: Add new test case