Is your feature request related to a problem? Please describe.
This repo contains some parts of dq-components.

Describe the solution you'd like
Migrate this repo to its respective dq-component

Description

As a domain expert interested in resilience scenarios, I would like to create a resilience verification scenario that probes a service in my application as a means to verify if it correctly responds before and after a fault load is injected.

Acceptance Criteria

• The probing scenario's endpoints match the selected services from the service failure template
• The probing scenario's HTTP methods match the selected service from the service failure template
• Additional data fields for HTTP body key-value pairs can be added by a "+" button
• The data fields are marked as mandatory fields (*)

Description

As a domain expert interested in resilience scenarios, I would like to create a service failure scenario by selecting an application service by using a service identifier or selector to observe if my application is able to handle the shutdown gracefully.

Acceptance Criteria

• There exists a data field for declaring a service identifier or selector
• There exists a data field for random selection in case multiple services exists with the same selector
• There exists a data field for describing the quantity of services that suffer from a shutdown
• The template shows an error message if the mandatory fields are kept empty

Description

As a domain expert interested in monitoring, I would like to create a monitoring specification template by dragging the monitoring specification icon onto the canvas to model a monitoring specification with regard to the observed domain story.

Acceptance Criteria

• There exists an icon for monitoring specifications that can be dragged onto the domain story
• Upon dropping the icon on a domain story, a new view is created for a monitoring specification
• Upon dropping the icon on a domain story, a button is created that allows viewing the monitoring specification template
• The view can be closed by clicking on the "close" button inside the view
• The view shows a "close" button
• The view shows a "save" button
• The view contains the following data input fields:
  • entering a name for the monitoring specification
  • selecting a service from a list of existing services
  • selecting one HTTP endpoint as a measurement endpoint from a list of possible endpoints of the previously selected service
  • entering a time duration in hours:minutes as the observation period
  • entering a response time threshold in milliseconds

Current Behavior:

Each template creates a new object. However, multiple tests are not yet summarized into one final object

Expected Behavior:

Multiple objects should be summarized in one JSON Structure.

Description

As a domain expert interested in runtime quality analysis, I would like to have supporting information text on the data fields to understand what information I need to provide.

Acceptance Criteria

• Each data field contains an information icon

• On hovering the information icon, a supporting text is shown that explains the data field

Current behavior:

Checkboxes are off center and if checked the information is currently not included into the template object.

Expected behavior:

Additional information is saved into template object and checkboxes are centered with the text.

Description

As a domain expert interested in runtime quality analysis, I would like to open a view that shows the results from my runtime quality analysis tests so that I can inspect and interpret the results together with a technical expert.

Acceptance Criteria

• When the system receives results, a button shows that can be clicked with the text 'results'

• When the 'results' button is clicked, a separate modal view opens

• The modal view contains an excerpt of the runtime quality analysis results

Description

As a domain expert interested in resilience scenarios, I would like to define the environment in which the prototype executes the modeled resilience scenario.

Acceptance Criteria

• There exists a data field to define the execution environment
• The user may choose from two data fields as environments: (1) testing and (2) production
• The template shows an error message if the execution environment field is kept empty

Description

As a domain expert interested in resilience scenarios, I would like to describe the expected response from a service in case of a modeled application-type resilience scenario in order to verify that the service works as expected.

Acceptance Criteria

• Data fields in the response object description can be added via a "+" button that creates new name/value (key/value) pairs on the template
• The user can define an HTTP response status code in the template
• The user may select from a selection of valid status codes in the template (200 – OK, 201 – Created, ... )
• The data fields HTTP status code and HTTP response object are marked as mandatory fields (*)

Description

As an domain expert interested in runtime quality analysis, I would like the elements on the canvas show a color highlight to differentiate them of elements I already created a test for.

Acceptance Criteria

• When a specification or test has been saved, the respective element is highlighted with a colored border

Description

As a domain expert, I would like to import a mapping specification of my current domain story to allow precise modeling of runtime quality analysis tests and results representation.

Acceptance Criteria

• The user can import a mapping specification via an "import mapping" button

Currently the confirmation modal is implemented and binded to the resilience template save button which is the old behavior.

Expected: When the generate and push button is pressed by the user, the summary view should be opened and shown to the user where he confirms that all information is correct and that he wishes to push the object to the message-queue (or equalizer backend)

The resilience template object class must be updated with the new template information as the modeling approach has changed.

Priority: high

Current behavior:
Upon attempting to create another load test on a separate activity/actor/work object, the modal opens showing only the header and ruler element but no other input elements (see screenshot).

Expected behavior:
The modal opens showing the header, ruler element and the other input elements respective to a load test.

Description

As a domain expert interested in resilience scenarios, I would like to specify the type of resilience scenario to know which services and resources will be affected by my modeled scenario.

Acceptance Criteria

• there exists a data field for resilience scenario types
• the user may choose from two inputs: (1) application and (2) infrastructure

Description

As a domain expert interested in resilience testing, I would like to open a summary view that shows my currently modeled resilience scenarios so that I can verify the models before generating the scenarios.

Acceptance Criteria

• When the user saves a resilience template, a summary view is created

• The summary view can be opened by clicking a button that is labeled as 'resilience scenarios'

• The summary view holds all information from all currently modeled resilience scenarios on the canvas

Description

As a domain expert interested in resilience scenarios, I would like that the prototype removes the context view for resilience scenarios that is specific to a resilience scenario ID in case I remove the resilience scenario from the domain story canvas

Acceptance Criteria

•  Context modal view is remove when resilience scenario icon is removed from domain story canvas

Description

As a domain expert interested in loadtesting, I would like to open a summary view that shows my currently modeled loadtest specifications so that I can verify the models before generating the tests.

Acceptance Criteria

• When the user saves a loadtest specification a summary view is created

• The summary view can be opened by clicking a button that is labeled as 'loadtest specifications

• The summary view holds all information from all currently modeled loadtest specifications on the canvas

Description

As a domain expert interested in runtime quality analysis, I would like to select the service ID of a service instance if multiple service instances are available for one particular service to freely decide which service will fail during a resilience scenario.

Acceptance Criteria

• By default, the randomized selection has a value of 'yes' (shown as an info text on the label)

• The service instance ID list is by default disabled

• If the user selects no, then the disabled attribute is removed from the selection

• The user can select one service ID if the value for randomization is 'no'

• The resilience template contains a data checkbox with the value 'no' that can be clicked

• Depending on the value of randomization, the list of service IDs is disabled or active

  • Disabled, if randomized

  • Active, if not randomized

Description

As a domain expert and technical expert, I would like to create a mapping between the current domain story and the application's architecture to enable runtime quality analysis modeling on the domain level

Acceptance Criteria

• The users can open a view via a "+" button that represents a new mapping

• After adding a new mapping, the view can be opened via a "open mapping" button

• The mapping input fields can be saved via a "saved" button

• The mapping view can be closed via a "close" button

• The mapping view lists data input fields mandatory to create a mapping

• The system notifies the user if mandatory information is missing

• The mapping can be generated and sent to an dqualizer interface via a "generate" button

Background

For modeling the runtime quality analysis questions (Laufzeitqualitätsanalyse Fragestellung), we'd like to use an adapted version of Domain Storytelling.

In this ticket, different frontend libraries/frameworks for modeling business processes/domain stories with our particular needs should be evaluated.

Task List

1. What are domain stories? Get familiar with domain storytelling.
2. Model / draft your own domain story.
3. Become familiar with Domain-Story-Modeler
4. Look out / search for Libraries / Framework that allow modeling of domain stories similar to domain-story-modeler, see bpmn.io
   • It should be possible to create additional / custom annotations (e.g., load test, resilience test, monitoring) which can be connected to nodes (work objects and actors) and activities

Description

As a domain expert interested in resilience scenarios, I would like to create a resilience scenario template by dragging the resilience scenario icon onto the canvas to model a resilience scenario with regard to the observed domain story.

Acceptance Criteria

• There exists an icon for resilience scenarios that can be dragged onto the domain story
• Upon dropping the icon on a domain story, a new view is created for a resilience scenario
• Upon dropping the icon on a domain story, a button is created that allows viewing the resilience scenario template
• The view can be closed by clicking on the "close" button inside the view
• The view shows a "close" button
• The view shows a "save" button
• The view contains the following data input fields:
  • entering a name for the resilience scenario
  • selecting a fault type for the resilience scenario from a list of two fault types (service failure, service delay)
  • selecting an injection level for the resilience scenario from a list of abstraction levels (application, infrastructure)
  • entering a start time
  • selecting an environment for the resilience scenario from a list of environments (production, testing, staging)

Description

As a domain expert interested in runtime quality analysis, I would like to receive a pre-determined list of available HTTP endpoints (measure points) that I can select for the load test in order to limit my decision to reasonable targets.

Acceptance Criteria

• List of pre-determined HTTP endpoints is provided by Mapping object

• Selection only shows available HTTP endpoints

Description

As a domain expert interested in runtime quality analysis, I would like to save my inputs to change them later on or to generate the final object when I am done with modeling.

Acceptance Criteria

• Mandatory fields must be selected or filled out with information

• User receives a notification if mandatory information is missing

• If a loadtest template is saved and the 'generate' button is still disabled, it becomes active

Current behavior:

Loadtest does not know to which element it belongs to in the final object

Expected behavior:

When a loadtest has been saved, the canvas element's name (ID) should be saved along with the template object.

Description

As a domain expert interested in resilience scenarios, I would like to generate a resilience scenario template object from a previously modeled resilience scenario template that I can provide to dqualizer in order to run the resilience scenario according to my specifications.

Acceptance Criteria

• There exists a "Generate" button in the resilience scenario template
• The system asks if I really want to generate the resilience scenario template object when clicking on the "Generate" button
• The system checks the content of the resilience scenario template on completeness before attempting to create the object
• Confirming the generation closes the confirmation modal and retrieves the persisted template object from memory