This session aims to cover a lot of ground and explore some power tips, expert tricks, new features, lesser-known hacks to help you impress your colleagues and get your work done faster.

In this session, Denis Markovtsev will demonstrate the benefits of Rapise’s built-in intelligence that significantly reduces the maintenance costs of tests.

In this session, Denis Markovtsev will demonstrate how to set up the recorder at the beginning of a test automation project to ensure the generation of resilient XPATH locators and readable object IDs.

This practical session will demonstrate the best practices of automating the testing of a complex system using Rapise while iterating on the process and verifying and refining the approaches.

In this session, Alexey Grinevich explores Inflectra’s own scriptless language - Rapise Visual Language (RVL) - a module that offers benefits far beyond easy test scripting.

In the session, Alexey Grinevich and Denis Markovtsev unveil awesome new features that improve the test automation experience for every Rapise user.

This session aims to cover a lot of ground and explore some power tips, expert tricks, new features, lesser-known hacks to help you impress your colleagues and get your work done faster.

In this session, we will discuss how you can organize your products into templates, what customizations can be part of your template, and how you can clone products and templates.

In this session, we will present a roadmap to helping users adapt to the concepts in the Inflectra toolset (primarily Spira and Rapise) and give you handy tips and quick wins to keep your users happy and engaged.

In this session, we will discuss how the project associations work for requirements and other artifacts. We will also cover some of the more common use cases that take advantage of this unique feature.

In this advanced session, we will explore the mechanics of creating an end-to-end DevOps toolchain using Spira plus associated tools such as Jenkins, Git, AWS, xUnit, RemoteLaunch, and Rapise.

This session will look at the different ways you can scale your agile projects into programs and portfolios using SpiraPlan.

In this session, we will build on our earlier discussions of Spira's risk management, analysis, and mediation functionality and dive into the how's of implementing FMEA using Spira's risk management module.

In this session, we will explain the concept of product baselines and why you may want to use them. We will create baselines at critical points during a release and then review the change history.

This session demonstrates how you can create custom graphs in Spira to be used by members of your team on the reporting dashboards.

In this session, we will share recommendations and best practices for using Spira and TaraVault to manage your source code, with examples using both Git and Subversion.

In this session, we will discuss the different workflows available in Spira (requirements, test cases, tasks, documents, releases, and incidents) and how you can combine them to create a project workflow that works for you.

In this session, we will walk you through how to set up the integration between Spira and Atlassian Jira and Microsoft Azure DevOps (ADO), with a live demonstration of synchronizing defects, user stories, and tasks (ADO only) between the different systems.

This session introduces the use of Entity SQL to create data queries that can populate sections of the report. The session will demonstrate some basic queries, including using joins, aggregations, and calculations.

This advanced session focuses on taking an existing report and modifying its template and format to display the data differently.

This session will cover the basics of setting up a CI pipeline in Jenkins, connecting it to Spira, and adding some simple unit tests, API tests, and Rapise UI tests.

Discover how Inflectra’s Remote Launch helps orchestrate automated tests for automation tools that integrate with Spira, including Rapise.

This session outlines some of the more advanced features available in SpiraTest for authoring test cases: use of linked test steps to create modular, componentized tests, and test case parameters to create a hierarchy of test cases.