<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Asynchronous Testing on Step Documentation</title>
    <link>https://step.dev/knowledgebase/31/categories/asynchronous-testing/</link>
    <description>Recent content in Asynchronous Testing on Step Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 19 Aug 2019 09:30:25 +0100</lastBuildDate><atom:link href="https://step.dev/knowledgebase/31/categories/asynchronous-testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Async packages</title>
      <link>https://step.dev/knowledgebase/31/plugins/async-event/</link>
      <pubDate>Wed, 10 Apr 2019 14:24:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/plugins/async-event/</guid>
      <description>Async and event-driven functionality is implemented in Step in the form of what we called the Event Broker, a central component allowing developers and plan users to manage the transmission of events, as well as a series of controls and built-in keywords.
Event Broker overview The basic semantics and the different means to access the broker are illustrated on the following figure:
The private members of the Event are as follows.</description>
    </item>
    
    <item>
      <title>Event Broker API</title>
      <link>https://step.dev/knowledgebase/31/devdocs/eventbrokerapi/</link>
      <pubDate>Wed, 22 May 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/devdocs/eventbrokerapi/</guid>
      <description>The Java APIs and libraries discussed in this section are currently only available in Step Enterprise Edition EventBroker The EventBroker Service and API allow asynchronous communication to happen in Step as well as synchronization between keywords, between plans and between keywords and plans. It is particularly useful in scenarios where a thread (or a &amp;ldquo;user&amp;rdquo;) needs to wait for specific events before performing the next task.
These events can be created internally (from within a keyword or plan) using various types of clients (Java, REST, prepopulated Keywords and Artefacts).</description>
    </item>
    
    <item>
      <title>Event Broker Monitor</title>
      <link>https://step.dev/knowledgebase/31/userdocs/eventbrokermonitor/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/userdocs/eventbrokermonitor/</guid>
      <description>If you&amp;rsquo;ve purchased the Async package or are running the Premium Enterprise version of Step, you&amp;rsquo;ll be able to monitor in real time what&amp;rsquo;s happening in the EventBroker by navigating to the EventBrokerMonitor view:
The Stats tab provides global statistics on the broker, such as the current amount of messages present in it and the high mark (or water mark), oldest &amp;amp; youngest events, etc.
The next two tabs provide users with the ability to browse and search for events, and organizes the query results either by Id or Group.</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>
    
  </channel>
</rss>
