Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-2116

Replace Test Scopes with new version

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.4.0, 7.4.0-alpha3
    • None
    • documentation
    • None

      The scopes in http://docs.camunda.org/latest/guides/user-guide/#testing-overview are outdated. On consulting we use a different version of the scopes which help us a lot out there at the customer.

      The image in the docs should be replaced by this.

      As Daniel had some thoughts about details I attach the PPT so you can still adjust details.

        This is the controller panel for Smart Panels app

          1. testing scopes.pptx
            385 kB
          2. scopes.png
            scopes.png
            142 kB

            [CAM-2116] Replace Test Scopes with new version

            Daniel Meyer added a comment -

            closed for review

            https://github.com/camunda/camunda-docs-manual/commit/7f9541f4da9cf305de2c9f8fdbb58d0a88c7f626

            Daniel Meyer added a comment - closed for review https://github.com/camunda/camunda-docs-manual/commit/7f9541f4da9cf305de2c9f8fdbb58d0a88c7f626

            Thorben Lindhauer added a comment -

            Review feedback:
            The Java EE example is very hard to understand if you are not a Java EE guy (acronyms galore). I propose to add some more general explanations to the "Scoping Tests" section, so readers can get the general idea without understanding the example.

            For example, we could elaborate on scopes and layers and say that the inner-most scope

            • mocks the most dependencies
            • is farthest away from the real world
            • is cheap to set up
            • makes it easy to write a multitude of process-focused tests

            and that the outer-most scope

            • mocks the least or no dependencies
            • is closest to real world
            • is expensive to set up
            • is therefore restricted to integration testing of certain scenarios, not all possible scenarios

            Then we can say that for every layer/scope, one needs ways to mock the desired dependencies and ways to test in that scope.

            Then give simple examples of what a scope could be (e.g. gateway expression) and how process dependencies can be mocked (e.g. in-memory database).

            Then have the Java EE example that shows how one could define the scopes.

            Thorben Lindhauer added a comment - Review feedback: The Java EE example is very hard to understand if you are not a Java EE guy (acronyms galore). I propose to add some more general explanations to the "Scoping Tests" section, so readers can get the general idea without understanding the example. For example, we could elaborate on scopes and layers and say that the inner-most scope mocks the most dependencies is farthest away from the real world is cheap to set up makes it easy to write a multitude of process-focused tests and that the outer-most scope mocks the least or no dependencies is closest to real world is expensive to set up is therefore restricted to integration testing of certain scenarios, not all possible scenarios Then we can say that for every layer/scope, one needs ways to mock the desired dependencies and ways to test in that scope. Then give simple examples of what a scope could be (e.g. gateway expression) and how process dependencies can be mocked (e.g. in-memory database). Then have the Java EE example that shows how one could define the scopes.

            Daniel Meyer added a comment -

            Thanks. I see the point and agree with it. However, I do not think that further improving this section is woth it it at this point.#
            For the moment I want to close this issue and not improve it further.

            Daniel Meyer added a comment - Thanks. I see the point and agree with it. However, I do not think that further improving this section is woth it it at this point.# For the moment I want to close this issue and not improve it further.

              meyer Daniel Meyer
              ruecker Bernd Ruecker
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: