https://oryon.exense.ch/knowledgebase/2.10/ Recent content on exense: oryon Hugo -- gohugo.io en Sat, 01 Jan 2000 00:00:00 +0000 https://oryon.exense.ch/knowledgebase/2.10/guide/settings/ Sat, 01 Jan 2000 00:00:00 +0000 https://oryon.exense.ch/knowledgebase/2.10/guide/settings/ There are two settings files that the Oryon IDE considers: The file oryon-ide.settings in the user’s home directory. This is where all settings and preferences are stored to. The file oryon-ide.settings in the current working directory - on Windows, this will usually be the directory where the batch file to start the IDE resides in. If this file exists, its content will be used to provide fallback values for settings which are not found in the user’s own settings file. https://oryon.exense.ch/knowledgebase/2.10/getting-started/documentation/ Sat, 01 Jan 2000 00:00:00 +0000 https://oryon.exense.ch/knowledgebase/2.10/getting-started/documentation/ What is Oryon? Oryon is an automation tool for Java UI applications (typically fat clients) which allows users to easily record and replay interaction scenarios. During recording, scripts are generated which serve as a blueprint for subsequent (automated, simulated) interactions. Advanced users can leverage the groovy language to adapt the resulting scripts as needed, tailoring them exactly to their needs. Used in combination with step, Oryon can be employed in massively concurrent simulations, potentially involving thousands of simulated clients, and can benefit from the wide range of features provided by step itself (centralized results, collaborative web app, natural language bindings, etc). https://oryon.exense.ch/knowledgebase/2.10/getting-started/agent/ Sat, 01 Jan 2000 00:00:00 +0000 https://oryon.exense.ch/knowledgebase/2.10/getting-started/agent/ The Oryon agent is the component which allows to interact with a Java GUI application, i.e. to retrieve its UI state and to control it. The agent currently includes modules supporting the following Java UI technologies: Swing: generic module for applications using the Java Swing framework. SyriusSwing: custom module, specifically for the Swing version of Adcubum Syrius. SyriusFX: custom module, specifically for the JavaFX version of Adcubum Syrius. Installation and configuration The first and most important step to control Java GUI applications using Oryon is to configure the target application in a way which will run the Oryon agent alongside it (or rather, technically: inside it, as part of the same Java process). https://oryon.exense.ch/knowledgebase/2.10/guide/parameters/ Sat, 01 Jan 2000 00:00:00 +0000 https://oryon.exense.ch/knowledgebase/2.10/guide/parameters/ While recording scripts, many of the methods that you’ll encounter require one or more parameters. Starting with version 2.6.0, these parameters are set interactively using an enhanced dialog. Here is an annotated example screenshot, with explanations given below: 1: Context information At the top of the dialog, a short summary of the context is shown. It consists of the method name for which a value is required (clickTableRow in the example), and the current parameter (Row) for which a value is to be set. https://oryon.exense.ch/knowledgebase/2.10/guide/logging/ Sat, 01 Jan 2000 00:00:00 +0000 https://oryon.exense.ch/knowledgebase/2.10/guide/logging/ Starting with Oryon version 2.4.0, the Oryon agent allows to control its logging, primarily for circumstances where troubleshooting is required. For that purpose, two Java properties may be set (if they are not present, the system will use defaults as outlined below). oryon.loglevel Sample usage: -Doryon.loglevel=debug This setting defines the verbosity of the logging. The supported values are: ERROR WARN INFO DEBUG TRACE The default log level is INFO, which is not very verbose. https://oryon.exense.ch/knowledgebase/2.10/getting-started/ide/ Sat, 01 Jan 2000 00:00:00 +0000 https://oryon.exense.ch/knowledgebase/2.10/getting-started/ide/ The Oryon IDE is a full blown groovy editor with additional functionality tailored specifically for Oryon such as: an object tree representing the current state of the Java application currently connected to (on the left side) a central code editor view, with a tabbed interface allowing to edit multiple scripts at once a console displaying the output script executions at the bottom step-compatible input and output controls at the top and bottom Once a target application is running with the Oryon agent, you can start the IDE using the script startOryonIDE. https://oryon.exense.ch/knowledgebase/2.10/getting-started/step/ Sat, 01 Jan 2000 00:00:00 +0000 https://oryon.exense.ch/knowledgebase/2.10/getting-started/step/ To make the Oryon plugin usable from within step, add the following to the file step.properties on the step controller: plugins.oryon.home=/path/to/oryon-x.y.z => used by the plugin to access the oryon libraries plugins.oryon.errorhandler=../data/scripts/oryon_errorhandler.groovy => can be used to define a script that is executed in case of TECHNICAL_ERRORs during the keyword execution … and to the AgentConf.js: { "gridHost": "", "registrationPeriod": 1000, "gridReadTimeout": 20000, "workingDir": "src/test/work", "tokenGroups": [ { "capacity": 10, "tokenConf": { "attributes": { "key": "val" }, "properties": { "plugins. https://oryon.exense.ch/knowledgebase/2.10/guide/sso/ Sat, 01 Jan 2000 00:00:00 +0000 https://oryon.exense.ch/knowledgebase/2.10/guide/sso/ Please refer to the documentation of the JSLogin implementation for the recommended approach to handle external (Identity Provider-based) Syrius logins. This page will remain here for reference, but the mechanism of providing tailored Java implementations for each login procedure is considered obsolete. Newer versions of the Syrius software support a Single Sign On (SSO) feature. Starting with version 2.6.0, such constellations are also usable with Oryon in an initial implementation. https://oryon.exense.ch/knowledgebase/2.10/guide/jslogin/ Sat, 01 Jan 2000 00:00:00 +0000 https://oryon.exense.ch/knowledgebase/2.10/guide/jslogin/ This page documents the usage of the JSLogin mechanism for external (Identity Provider-based) authentication to Syrius. Starting with Oryon 2.10.0, this is the recommended approach. Legacy Java-based implementations are still supported, and can still be used as long as they remain operational, but they are deprecated and no longer maintained. In any case, they can be replaced by the more flexible mechanism described here. We recommend to start with the bundled authentication script that should work with Keycloak-based Identity Providers: https://oryon.exense.ch/knowledgebase/2.10/guide/apidocs/ Sat, 01 Jan 2000 00:00:00 +0000 https://oryon.exense.ch/knowledgebase/2.10/guide/apidocs/ If you are a regular Oryon user, you already know that the gui object you usually interact with provides a number of methods, such as gui.click("/Some/Button"); or gui.setText("/Some/TextField", "Oryon rocks!"); While most of these methods are named in a straightforward way, and Oryon’s recording capabilities greatly simplify the generation of scripts which use common functionality, not all available methods are “discoverable” using the graphical tools alone. Therefore, we also provide Javadoc documentation of the relevant interfaces. https://oryon.exense.ch/knowledgebase/2.10/guide/syrius-node-pruning/ Sat, 01 Jan 2000 00:00:00 +0000 https://oryon.exense.ch/knowledgebase/2.10/guide/syrius-node-pruning/ Introduction As you know, Oryon interacts with Syrius by referencing components using XPath selectors on a component tree. In a nutshell, this tree corresponds to the hierarchical structure of the visual elements shown to the user. The structure is provided by the Syrius server, and rendered by the Syrius application. However, it has been observed that there are nodes which are present in the tree, but not actually rendered. Such nodes cannot be interacted with, and cause the tree (and therefore the XPaths) to be more complicated than they need to be. https://oryon.exense.ch/knowledgebase/2.10/whatsnew/releases/ Sat, 01 Jan 2000 00:00:00 +0000 https://oryon.exense.ch/knowledgebase/2.10/whatsnew/releases/ Version 2.10.0 New features Agent/Syrius: new mechanism for scriptable external logins Bugfixes IDE: Fix special character handling on macOS IDE: Fix popup window display on secondary screens on macOS Other groovy-dateutil is now included for use in the IDE, thus allowing to use simplified methods for date manipulation in scripts. minor logging fixes Version 2.9.0 New features Agent, driver, and IDE: Java 17 and 21 are now officially supported in addition to Java 11.