Tricentis has acquired Q-up: a test data management (TDM) platform architected to provide secure, reliable, and compliant test data on-demand. With a business-friendly, self-service interface and a lightweight provisioning agent, test data access is reduced from weeks to seconds. [Read the press release]

Tricentis Tosca users have probably witnessed how our existing TDM capabilities enable faster, more sophisticated, and more sustainable test automation. With on-demand access to stateful test data, testers can seamlessly access the exact test data needed for even the most complex test scenarios.

Tricentis’ enhanced TDM capabilities give users multiple options for the design, generation, and management of test data. This allows users to select the best strategy for their architecture, development phase, and/or release cadence. For example, users might want to start by rapidly configuring “smoke tests” that closely mirror production data, then later use synthetic test data generation to increase test coverage and complete negative testing prior to delivery.

Learn more—and see the solution in action—at the webinar: Q-up + Tricentis: Secure and Flexible Test Data Management for Continuous Testing

 

Why Expand our TDM Solution?

The short answer to this question is four letters: GDPR. Unless you communicate via carrier pigeon, you’re probably aware that GDPR is now in effect. However, the impact on application development (and software testing in particular) isn’t getting nearly as much attention as the volume of “privacy policy updates” overwhelming our inboxes.

Here’s why app dev teams can’t write off GDPR as “a Marketing problem”:

  • Someone is (hopefully) testing the applications that your development teams are building.
  • You can’t execute realistic tests without appropriate test data (e.g., name, address, billing details, etc.).
  • If that test data happens to include any personal data of any EU residents, it must be collected, processed, stored, and declared in accordance with GDPR—or you might be responsible for the company incurring fines of up to 4 percent of the company’s annual global turnover or €20 million (whichever is greater).

With GDPR now in effect, the business risk associated with using production data for software testing has become prohibitive. Organizations are suddenly realizing that TDM must become a critical component of a complete data privacy and security policy.

“For years, companies have been obtaining test data by extracting data from production environments,” explained Q-up Managing Director Andreas Günther. “GDPR will finally put an end to this approach by requiring extracted production data to be masked deterministically and irreversibly. This may be a blessing in disguise, because simply extracting data from production does not deliver data that’s optimized for the purpose of testing. Since organizations are already being forced to re-examine their TDM processes, now’s the perfect time to bring their overall TDM strategy in line with the demands of modern delivery processes.”

“To ensure that these new requirements don’t impede software delivery speed, we’re expanding our solution with fast, intuitive ways for testers to add GDPR-compliant test data to their tests—either through extraction and masking or synthetic test generation,” added Wolfgang Platz, Tricentis founder and Chief Strategy Officer.  “We’ve long recognized that TDM is a linchpin for Continuous Testing. Now, we’re expanding the Tricentis Continuous Testing Platform with a unique and innovative approach to providing secure test data.”

TDM - Test Data on Demand

Test Data that’s GDPR Compliant…and Stateful

Even before GDPR, obtaining and applying appropriate test data has always been tricky.

One of the greatest challenges associated with test data management is setting up and manipulating stateful data. Stateful test data not only produces the specific application conditions that are required to set up a realistic test; it also enables you to drive the test through a complex series of steps. It’s essential for executing end-to-end regression tests.

For example, imagine you want to test the reversal of fraudulent charges on a credit card account. First, you’d need to get the account into the “state” where an account was created and had a history of charges. Then, the test would need to indicate that certain charges were fraudulent and reduce the amount due accordingly. If your TDM solution can’t handle this, it’s not “stateful.”

With Tricentis, any tester can rapidly access the exact data needed for a given scenario and evolve it throughout the course of the test (no DBA or programming required).  With a comprehensive repository of stateful test data objects, you simply select the data set that corresponds to your test and indicate how it should change at each step. This enables continuous testing of scenarios that might otherwise be impractical to automate. [See Tricentis TDM product details]

TDS

TDM Support Extended to SAP Testing

With Q-up, Tricentis users also gain a new level of TDM support designed specifically for SAP testing. Tricentis now offers a fully-integrated set of capabilities for the design, generation, provisioning, and management of test data for all available SAP environments such as SAP ECC (AnyDB), SAP S/4HANA (SAP HANA), and even SAP BW/4 HANA (SAP HANA). We help you:

  • Access and generate test data via the modern oData protocol (SAP API)
  • Directly extract data from SAP tables via the RFC protocol
  • Invoke SAP BAPIs and function modules
  • Extract data from SAP queries
  • Extract SAP BW objects (BEx queries)
  • Using Batch Input techniques for background processing / data generation

Additionally, wizards are available to help you rapidly create compliant test data from Oracle, DB2, and SQL.

Stay connected– subscribe

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

X
X