https://step.dev/knowledgebase/30/categories/keywords/ Recent content in Keywords on Step Documentation Hugo -- gohugo.io en Mon, 19 Jun 2023 00:00:00 +0000 https://step.dev/knowledgebase/30/userdocs/keywords/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/userdocs/keywords/ This section will focus on registering and using already-developed keywords. To learn how to develop a keyword, check the Developer guide overview. What is a Keyword? Keywords in Step are the fundamental building blocks of Plans. They encapsulate the automation logic (often called scripts). They can represent fully automated flows or finer-grained actions, such as user interactions or service calls. Employing finer granularity is generally preferred as it enhances reusability across multiple business flows through Plans. https://step.dev/knowledgebase/30/userdocs/keywords/keywords-deployment/ Mon, 19 Jun 2023 00:00:00 +0000 https://step.dev/knowledgebase/30/userdocs/keywords/keywords-deployment/ You can add and manage Keyword by manual registration or automatically using package file. In this guide, we will first discuss ways of adding Keywords via package file. For description about the manual way of adding Keywords, please see the section: Adding a new Keyword by manual registration. Adding a new Keyword by manual registration In order to use your Keywords with Step, you need to register them. This can be done through the web interface or the Java API. https://step.dev/knowledgebase/30/plugins/jmeter/ Wed, 10 Apr 2019 14:24:01 +0100 https://step.dev/knowledgebase/30/plugins/jmeter/ The JMeter integration plugin allows you to integrate existing JMeter tests into Step as Keywords, which can then be used in Plans like any other Keyword. This means that you can use existing JMeter tests for massively parallel load test executions (distributed across multiple Agents), synthetic monitoring or any other disciple supported by Step. It supports following features: Passing of Keyword inputs to JMeter Passing of Parameters (properties) to JMeter Automatic generation of performance measurements based on the JMeter samples Attachment of the JMeter logs Installation On-premises installation The JMeter plugin is provided by default with Step Open source and Step Enterprise, but JMeter needs to be downloaded separately on the controller and the following option should be modified accordingly in the step. https://step.dev/knowledgebase/30/plugins/soapui/ Wed, 10 Apr 2019 14:24:01 +0100 https://step.dev/knowledgebase/30/plugins/soapui/ The SoapUI plugin allows you to execute parametrized test cases on Step Java agents. Note that an example of a SoapUI project is available in our samples repository available on github. Installation In order to use the SoapUI plugin, you have to point the controller to your SoapUI installation. Note that the controller will automatically send to the agent the jar files needed from SoapUI. This configuration is done by adding the following property to your step. https://step.dev/knowledgebase/30/plugins/pdfcompare/ Wed, 10 Apr 2019 14:24:01 +0100 https://step.dev/knowledgebase/30/plugins/pdfcompare/ Step’s PDF and Image compare plugins allow users to respectively validate the exactness of a rendered PDF or image file (called actual) when compared against a model (called expected document). As the PDF default comparison is an image-based comparison of every page of the actual document against that of the expected document, and as image types with multiple pages (such as tiff) are supported, both plugins work in a very similar manner.