<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Functional Testing on Step Documentation</title>
    <link>https://step.dev/knowledgebase/31/categories/functional-testing/</link>
    <description>Recent content in Functional Testing on Step Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 18 Oct 2022 10:24:01 +0100</lastBuildDate><atom:link href="https://step.dev/knowledgebase/31/categories/functional-testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Plan library</title>
      <link>https://step.dev/knowledgebase/31/libraries/plans_lib/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/libraries/plans_lib/</guid>
      <description>All of the plans documented in this section can be downloaded and then imported into your own private instance by following this procedure.
Basics Here are a few basic, yet non-trivial plans which will help you get started with the most useful and common constructs. We will be practicing with a very simple source type called &amp;ldquo;Json String&amp;rdquo;, which will help us distribute data across iterations and threads.
We can pass an arbitrary array of Json objects and then access them object by object.</description>
    </item>
    
    <item>
      <title>Controls</title>
      <link>https://step.dev/knowledgebase/31/userdocs/plans/controls/</link>
      <pubDate>Thu, 23 May 2019 07:00:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/userdocs/plans/controls/</guid>
      <description>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.</description>
    </item>
    
    <item>
      <title>Jira Xray</title>
      <link>https://step.dev/knowledgebase/31/plugins/jira-xray/</link>
      <pubDate>Tue, 18 Oct 2022 10:24:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/plugins/jira-xray/</guid>
      <description>Starting with version 20, Step Enterprise Edition provides support for integration with the popular Xray Test Management plugin for Jira. Both the Cloud and the Server edition of Xray are supported.
Installation and Configuration In order for Step to integrate with Jira and Xray, the systems will need to communicate with each other. The requirements differ between the editions of Xray, so please follow the steps for the Xray edition you want to integrate with.</description>
    </item>
    
    <item>
      <title>ALM</title>
      <link>https://step.dev/knowledgebase/31/plugins/hp_alm/</link>
      <pubDate>Wed, 10 Apr 2019 14:24:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/plugins/hp_alm/</guid>
      <description>The Micro Focus ALM integration plugin provides an out-of-the-box integration of Step with ALM.
With the ALM integration plugin you create, design and manage your automated test cases in ALM, run them on step&amp;rsquo;s Execution Engine, and evaluate the run results and test reports at the same place in ALM. This plugins is therefore the perfect solution for users requiring the best of the 2 worlds: the unique power of the Step Execution Engine with the test management and reporting features of ALM.</description>
    </item>
    
    <item>
      <title>SoapUI</title>
      <link>https://step.dev/knowledgebase/31/plugins/soapui/</link>
      <pubDate>Wed, 10 Apr 2019 14:24:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/plugins/soapui/</guid>
      <description>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.
Soap UI version 5.6+ is required.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.</description>
    </item>
    
    <item>
      <title>PDF and Image compare</title>
      <link>https://step.dev/knowledgebase/31/plugins/pdfcompare/</link>
      <pubDate>Wed, 10 Apr 2019 14:24:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/plugins/pdfcompare/</guid>
      <description>Step&amp;rsquo;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.</description>
    </item>
    
    <item>
      <title>New case study: Solving the Win32 issue using C#</title>
      <link>https://step.dev/knowledgebase/31/whatsnew/news/new-case-study-dotnet/</link>
      <pubDate>Thu, 10 Oct 2019 10:31:00 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/whatsnew/news/new-case-study-dotnet/</guid>
      <description>We&amp;rsquo;re announcing the publication of a new case study and several tutorials documenting how we&amp;rsquo;ve helped clients automate workflows involving Win32 applications. The end-to-end testing of proprietary Win32 applications is known by testers as a difficult task. However, in certain scenarios, ignoring these applications can prove to be catastrophic and this is why we&amp;rsquo;ve decided to help our client cover this part of his application landscape.
Take me to the Case StudyJust click the button above to access the case study.</description>
    </item>
    
    <item>
      <title>A new tutorial for Android testing on step</title>
      <link>https://step.dev/knowledgebase/31/whatsnew/news/new-android-tutorial/</link>
      <pubDate>Sun, 01 Sep 2019 11:39:07 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/whatsnew/news/new-android-tutorial/</guid>
      <description>Today we&amp;rsquo;re publishing a step-by-step tutorial allowing step users to run automation against Android devices. This tutorial will take you from the installation of the Android Studio and SDK, to a local execution of Appium scripts as keyword and then all the way to a parallel execution on multiple devices using step&amp;rsquo;s agent.
Keep in mind that exense offers highly competitive prices on managed Android emulators in the cloud. Check out our price calculator here for more information.</description>
    </item>
    
    <item>
      <title>New Case Study: the end-to-end testing of asynchronous systems</title>
      <link>https://step.dev/knowledgebase/31/whatsnew/news/new-case-study-async/</link>
      <pubDate>Mon, 19 Aug 2019 09:30:25 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/whatsnew/news/new-case-study-async/</guid>
      <description>This fresh case study explores different types of server-side architectectures which introduced challenges for E2E testers due to asynchronism. Each case originates from a different client and different technical context, yet we&amp;rsquo;ve been able to adress the corresponding issues with a unified approach. This means among other things that, as step&amp;rsquo;s async services evolve, each client will benefit from upgrades and additional functionality.
Take me to the Case StudyJust click the button above to access the case study.</description>
    </item>
    
    <item>
      <title>New Case Study: Android in the cloud</title>
      <link>https://step.dev/knowledgebase/31/whatsnew/news/new-case-study-android/</link>
      <pubDate>Fri, 26 Jul 2019 15:43:32 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/whatsnew/news/new-case-study-android/</guid>
      <description>Throughout this case study, we&#39;ve layed out a foundation for Android automation. In fact, the toolkit is so powerful that we were able to give the keys to our client so that they could operate the emulator farm themselves. This case study also covers the challenges of having to test new authentication mechanisms, in particular mobile authentication relying on Push notifications (Firebase).
Take me to the Case StudyJust click the button above to access the case study.</description>
    </item>
    
  </channel>
</rss>
