Automated-Testing | Sample code illustrating possible approaches | Runtime Evironment library

One option we looked at was to generate a csv instead of rendering in the browser. The csv was much easier to parse through than trying to hack the AJAX in the browser. We abandoned the effort because it ended up not yielding us the benefits we hoped.

We have added a string-fit test in GUIX Studio for the 6.1.9.1 patch release, under Edit -> Run String Fit Test. This release has been pushed to the App Store and will be rolling out over the next couple of days. This tests to insure every string in every language fits within the assigned widgets. Of course you can assign and re-assign strings at runtime, so Studio can't test for that, only the know assignments of widgets and fonts can be statically tested by GUIX Studio.

For our own internal regression testing, we build our test apps as Win32 apps and write python scripts to generate events into those apps to drive them. We do md5sum calculations of the canvas memory and compare the computed value with "golden values" to insure nothing has been broken. We haven't yet instrumented anything similar to support on-target regression testing but we have this feature in our backlog, I will see if we can get this on the priority list for the next release.

Best Regards

I don't how to fix that to push the commit to the branch itself connected to the tag as i need to update the kustomize.yaml there after each building

As far as Git itself is concerned, there is no connection between a branch name and a tag name.

At the Git level, any name—any reference—is simply a name that stores a hash ID. Branch names in particular are constrained to store only commit hash IDs, while tag names can store the hash ID of any internal Git object. A tag is said to be a lightweight tag if it stores a commit hash ID, or an annotated tag if it stores the hash ID of a tag object. This tag object then typically stores the hash ID of some commit.

You can use git branch --points-at to find branch names that select some particular commit, and git tag --points-at to find tag names that select some particular commit. For details, see the git branch and git tag documentation.

Note that you can give git tag the commit hash ID here, and it still finds annotated tags. Technically, it finds the annotated tag regardless of whether you name the tag object itself, or its target commit:

Please change variables.triggerRepoName to variables['triggerRepoName']. It should solve your issue.