Changes for page 177 - River Crossing

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.eMagiz
	1	+XWiki.ebakker

Content

...	...	@@ -6,27 +6,33 @@
6	6	== **Automated Flow Testing** ==
7	7
8	8	To improve our offering regarding flow testing, we have now made it possible to define on the test case level whether that test case needs to run automatically every time a user makes a new version of a flow. This way, you can verify whether your changes did not introduce breaking changes on the flow level.
9		-
10		-[[image:Main.Images.Release Blog.WebHome@178-release-blog-1.jpg]]
11	11
12	12	//__Configuration__//
13	13	To do so, you can select the option automated test case by opening the Details pop-up of a test case.
14	14
	13	+[[image:Main.Images.Release Blog.WebHome@177-release-blog-1.jpg]]
	14	+
15	15	When choosing the option Yes and pressing Save, the overview of flow tests will reflect this change by showing an icon in front of the test case.
16	16
17	17
	18	+[[image:Main.Images.Release Blog.WebHome@177-release-blog-2.jpg]]
	19	+
18	18	After configuring this, eMagiz will automatically execute the test case(s) upon creating a new version. This process happens in the background, so you don’t have to wait for it to finish.
19	19
20		-
21	21	//__Analysis on flow level__//
22	22	To see the results of the automated flow test(s) on flow level, you can navigate to the History tab. Here you will see the overall test status (of all the test cases combined), and it provides you with a button to Show the specific test results.
23	23
	25	+[[image:Main.Images.Release Blog.WebHome@177-release-blog-3.jpg]]
24	24
25	25	//__Analysis on release level__//
26	26	On top of that, eMagiz will show you an overview for all flows in your release, whether the test cases have failed, are still running, have no tests in them, or whether the test cases within a flow all passed. This overview is shown whenever you want to deploy or make a new release active.
27		-
	29	+
	30	+[[image:Main.Images.Release Blog.WebHome@177-release-blog-4.jpg]]
	31	+
28	28	Note that you can always view the test results overview of any older release by navigating to the Details pop-up and selecting the Test results tab.
29		-
	33	+
	34	+[[image:Main.Images.Release Blog.WebHome@177-release-blog-5.jpg]]
	35	+
30	30	==** Data models and transformations in eMagiz Store** ==
31	31	//The following feature is a Beta feature and is therefor available upon request. Don’t hesitate to contact us at productmanagement@emagiz.com if you are interested in becoming an early adopter.//
32	32
...	...	@@ -33,7 +33,7 @@
33	33	With this release, we will make the last set of improvements to the eMagiz Store, and we’ll start to provide content within the eMagiz Store. We can unlock the latest advances, including content to the public in the upcoming release. So keep your eyes open for more information!
34	34
35	35	== **Old Transformation Tooling - Deprecated **==
36		-As a gentle reminder to all, we would like to highlight that the old transformation tooling will be deprecated after the 1st of June. We will execute the migration to update the resources in each flow on that day. Note that the migration will not create a new flow version or change the user that changed the resource last as we make no functional changes to the resources themselves. For detailed information, please keep an eye out for updates on https://status.emagiz.com.
	42	+As a gentle reminder to all, we would like to highlight that the old transformation tooling will be deprecated after the 1st of June. We will execute the migration to update the resources in each flow on that day. Note that the migration will not create a new flow version or change the user that changed the resource last as we make no functional changes to the resources themselves. For detailed information, please keep an eye out for updates on [[eMagiz Status>>https://status.emagiz.com||target="blank"]].
37	37
38	38	== **Bug Fixes** ==
39	39