https://step.dev/knowledgebase/30/userdocs/plans/ Recent content in Plans on Step Documentation Hugo -- gohugo.io en Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/userdocs/plans/keywords-in-plans/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/userdocs/plans/keywords-in-plans/ Keywords serve as the fundamental building blocks for implementing automation. From a business perspective, a Keyword symbolizes a functionality to be automated. It might represent a fully automated flow or be as simple as a single user action or service call. A Plan represents an automated scenario and will normally consist of one or more Keywords. Whenever a Keyword is encountered during Plan execution, it leads to a Keyword call. This section focuses on the usage of Keywords within a Plan. https://step.dev/knowledgebase/30/userdocs/plans/controls/ Thu, 23 May 2019 07:00:01 +0100 https://step.dev/knowledgebase/30/userdocs/plans/controls/ Step supports a wide range of so-called controls to build-up complex flows in Plans. The supported controls range from classical control structures (like if blocks, loops, etc) to use-case specific controls like thread groups for load-testing, data-sets, etc. This page provides details about all the controls supported by Step. General controls Set The Set control allows to define a variable and assign it a value. Variables defined with Set controls can be accessed according to their scope throughout Plans and sub Plans. https://step.dev/knowledgebase/30/userdocs/plans/plans-variables/ Thu, 23 May 2019 07:00:01 +0100 https://step.dev/knowledgebase/30/userdocs/plans/plans-variables/ Variables are used throughout plans to pass information from one node to another, or to store the result of a dynamic computation. Variable types Similar to any programming language, Step supports the use of variables in Plans. The variables declared and used in a Plan are called Plan variables. A Plan variable is a container that stores a data value under a specific name. Like in classical programming languages, Step supports the following types of variables: https://step.dev/knowledgebase/30/userdocs/plans/other-plans/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/userdocs/plans/other-plans/ Calling another Plan To enable modular design of Plans Step makes it possible to recursively call other Plans. Using the Visual Plan Editor you can easily call other Plans using the tab “Other plans” from the component list: Using the plain-text syntax other plans can be called using the following syntax Call plan "Test Case 01" Call plan "Test Case 02" Call plan "Test Case 03" Composite Keywords You can also achieve modularity using so called composite keywords. https://step.dev/knowledgebase/30/userdocs/plans/visual_plan_editor/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/userdocs/plans/visual_plan_editor/ The Visual plan editor is the most basic and straight-forward way to create a Plan in Step. When using the Visual interface, you create your Plan in a code-free intuitive editor that gives instant access to the libraries of available Keywords and Controls. Using the Visual interface makes it possible to create a Plan in an intuitive manner without technical skills and prior knowledge of Step. It is also well-suited for complex automation plans which require a visual representation of the Plan. https://step.dev/knowledgebase/30/userdocs/plans/plaintext_plans/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/userdocs/plans/plaintext_plans/ In addition to the Visual Plan editor Step comes along with a full-featured parser which enables the creation of Plans using a plain-text human-friendly syntax. The plain-text format has different advantages over the Visual interface. Using the plain-text format makes it possible to manage Plans in a same manner as code and thus enables the use of version control system like git, text editors, etc. It also enables the integration with classical Test-Management Tools initially developed for manual test specification and thus based on plain-text test-cases specifications. https://step.dev/knowledgebase/30/userdocs/plans/java_plans/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/userdocs/plans/java_plans/ Programmatic plans are the object-oriented representation of a plan. It can be particularly useful for developpers to design, execute and maintain Plans directly in Java. See programmatic examples as part of the stepClient API here.