🖌️
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. Different Test Levels

Test Documentation

PreviousBest PracticesNextRun test projects

Last updated 1 year ago

Was this helpful?

In all the different levels of testing, it is necessary to use basic tags and follow some standards to document each test created into the code.

In the image above, it is possible to see the different parts necessary to document each test. These parts must always be in any test and any test level to improve the quality of the documentation. The next points explain each part in detail in order to avoid any misunderstanding:

1 - Feature: This tag is to describe the feature to test, and it can also describe a page or windows to test. However, it is normally a functionality or big feature like the following examples:

[Feature(“Login”)]
[Feature(“Assessment Mode”)]
[Feature(“First Page UI”)]

2 - Summary: It describes in a better way the scenario to test, explains inputs, outputs, the purpose of the test, etc. In addition, it is necessary to add the link of the test created and documented in Azure DevOps, for example:

/// <summary>
/// This test checks the functionality of the login using a correct user and password
/// <seealso href=”https://collaboration.artinsoft.com/ + the rest of the link”/> 
/// <summary/>

/// <summary>
/// This test checks the result when the assessment mode is used
/// <seealso href=”https://collaboration.artinsoft.com/ + the rest of the link”/> 
/// <summary/>

/// <summary>
/// This test checks the good functionality of the buttons on the first page of the UI
/// <seealso href=”https://collaboration.artinsoft.com/ + the rest of the link”/> 
/// <summary/>

3- Test Category: This tag is used to describe a group of tests. It is possible to use only the level of test or to create any other category depending on the context of the projects, for example:

[TestCategory(“Unit Testing”)]
[TestCategory(“Transformations”)]
[TestCategory(“E2E”)]

4 - Scenario: This tag describes the scenario to test, in other words, it is used to describe the title of the test to know easier and faster what the test does, for example:

[Scenario(“Login with correct data”)]
[Scenario(“Check the basic use of assessment mode”)]
[Scenario(“Check buttons functionality”)]
Parts of test documentation