Search: "flow test"

Running a Flow Test

crashcourse-platform-create-running-a-flow-test--channel-trace.png

crashcourse-platform-create-running-a-flow-test--failure-details.png

crashcourse-platform-create-running-a-flow-test--failure-result.png

crashcourse-platform-create-running-flow-test

{{container}}{{container layoutStyle="columns"}}((( In this microlearning, we'll cover how to run a flow test in eMagiz. Flow testing involves evaluating each component of a flow to ensure it works as expected with given inputs.

Prerequisites == * Basic knowledge of the eMagiz platform * Understanding of the Flow testing concept == 2. Key concepts == This microlearning centers around running a flow test.

. * You can run a flow test by pressing the play button. * Feedback is given in various formats. == 3.

Configure a Flow Test

crashcourse-platform-create-configuring-flow-test--add-test-case-button.png

crashcourse-platform-create-configuring-flow-test--added-a-test-case.png

crashcourse-platform-create-configuring-flow-test--entered-a-name.png

crashcourse-platform-create-configuring-flow-test

Configuring a Flow Test == Configuration of a flow test is necessary for two scenarios. On the one hand, you want to add a new flow test to test a scenario for which you have not yet a flow test available. On the other hand, you want to be able to edit an existing flow test to alter the input, output, or naming of the existing flow test.

Edit Flow Test

crashcourse-platform-exercise-edit-flow-test

This exercise will show you how to edit your existing flow tests in such a way that you achieve a succesfull test in which the actual output matches the expected output.

Following that build a flow test for the offramp that uses one of the expected outputs as an input for that flow test and test and edit it in such a way you also achieve a success on this flow.

{{video attachment="crashcourse-platform-exercise-edit-flow-test-update.mp4" reference="Main.Videos.Microlearning.WebHome"/}} )))((({{toc/}}))){{/container}} {{/container}}

Understanding Flow Testing

As we work with flows in eMagiz we call it Flow testing. Flow tests are always combined with specific pieces of elements that make the unit operational, such as test data, test messages, or access to services that produce data.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create--understanding-flowtesting-testing-stages.png]] == 3. Creating Flow tests in eMagiz == Flow tests in eMagiz are created in the Create phase while developing your flow.

* It will speed up the development of the flow itself * The flow test allows having a better reference for other team members how the flow should behave * The flow test can help to validate the entire integration flow during User Acceptance Testing * During issue resolution, the flow test can be reused with the attached test messages to pinpoint issues.

Define and run Flow Test

crashcourse-platform-exercise-define-and-run-flow-test

This exercise will show you how to define your first flow test based on a provided example message and how you can subsequently run this flow test within the platform.

Exercise == In this exercise, please ensure that you create a basic flow test given the input message provided and run it for a first time to see what happens.

{{video attachment="crashcourse-platform-exercise-define-and-run-flow-test-update.mp4" reference="Main.Videos.Microlearning.WebHome"/}} )))((({{toc/}}))){{/container}} {{/container}}

intermediate-testing-emagiz-api-gateway-testing-the-api-gateway--flow-test-configuration.png

First, we take a look at flow testing, secondly, we turn our attention to Swagger UI. * Flow testing is meant for testing the exit gates * Swagger UI is meant for testing the whole operation as a client * Both play an intricate part in testing your API Gateway === 3.1 Flow Testing === In the [[Crash Course Platform>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]] we have several microlearnings on the topic of [[flow testing>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-configuring-flow-test||target="blank"]]. Please take a look at those microlearnings first if the concept of flow testing is new to you. As described there, the flow testing functionality also works for API Gateway exit gates.

* By user regression testing, we mean: A test that is designed to verify whether existing functionality is not impacted by newly added functions. == 3. Automated flow test == The purpose of automated flow tests is to prevent undesired impact on flows when applying certain changes.

The remainder of this section will explain how to setup a automated flow test. //__Configuration__// To configure an automated flow test, you can select the option automated test case by opening the Details pop-up of a test case.

//__Analysis on flow level__// To see the results of the automated flow test(s) on flow level, you can navigate to the History tab.

Within eMagiz, we have a dedicated unit testing functionality called "flow testing." One of the key benefits of flow testing is that your integration does not have to be deployed.

The main functionality within the eMagiz platform to perform regression testing on your integrations is called "Automated flow testing." There is an option to automate every flow test. When a flow test is automated, it will run all automated flow tests once a new version is committed.

{{container}}{{container layoutStyle="columns"}}((( In this microlearning, we’ll cover how to delete test messages for flow testing in eMagiz. Flow testing involves checking each component within a flow using specific inputs and expected outcomes.

Prerequisites == * Basic knowledge of the eMagiz platform * Understanding of the Flow testing concept == 2. Key concepts == This microlearning centers around deleting test messages for flow testing.

In this case, we have no input message anymore so the flow test will not work anymore. [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-deleting-test-messages--delete-test-message-result-canvas.png]] {{info}} Although the message is now removed from a specific flow test it is still available to use as a blueprint for any other flow test (or the same one in the future).

{{container}}{{container layoutStyle="columns"}}((( In this microlearning, we'll explore how to edit test messages for flow testing in eMagiz. Flow testing involves evaluating components of a flow using specific inputs and expected outcomes.

Prerequisites == * Basic knowledge of the eMagiz platform * Understanding of the Flow testing concept == 2. Key concepts == This microlearning centers around editing test messages for flow testing. With flow testing, we mean: Testing each separate component (unit) within the context of a flow based on a supplied input (and an expected outcome).