Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-2427

Create structure to document non-tested features

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.6.0-alpha1
    • Component/s: None
    • Labels:
      None

      Description

      We need to ensure that all features that we document in the user guide also work. The standard way to do this is by using e2e tests. However, not all features are tested this way.

      We need to ensure that we keep track of features that are not automatically tested as part of our e2e-suite so we can manually test them for releases.

      AT:

      • There is a place in the optimize github wiki where the features that need to manually be tested are listed
      • There is a description about how to test each feature
      • The release guide has a link to this list
      • The list does not have to be complete yet. This ticket is about creating an adequate structure, not about the content. Doing it for a single example feature is sufficient

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              sebastian.stamm Sebastian Stamm
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: