Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2023.1

...

The Data Repository Server is the server that stores the data. You can deploy a single server that multiple teams can share , or deploy multiple servers so that each team has its own sandbox.

...

The scope of a data repository is entirely up to you. It can be extremely broad , or very specific. As you structure repositories, consider the record types that will need to be shared as well as the export/import and backup/restore cycles. For instance, you might want to create one repository for services that share the same record types , and a different one for services that use a very different set of record types. For another example, assume you have two teams: one that will be frequently modifying data then restoring the original data, and another set of teams that needs continuous access to a stable version of that same data set. In that case, it would probably make sense to have 2 different data repositories.

Not all data repositories have to be represented in every team member’s Data Repositories view. For example, assume your division is sharing a Data Repository Server that hosts 20 repositories. Members of Team A might only be working with 3 three of those repositories, so they would need only those 3 three repositories connected to their Data Repositories view. Another team might choose to connect to 1 one of those repositories along with 5 five additional repositories.

Data Set

...

A record type has a name, a certain number of columns (also known as fields), and a hierarchy defined. The scope of record types is at the repository level (for example, the same "book" record type definition applies across all data sets that use the "book" record type).

Repository Connection

A Repository Connection adds a Data Repository to the Data Repositories view, which helps you review and edit the structure and contents.

...

A repository data source is a "wrapper" for the repository data source that allows you to consume it in Parasoft messaging tools—in tools in the same manner as way you would consume data from an Excel data sheet, CSV file, or other supported data source. Through the data source wrapper, you can segment what repository data you want to use for a given suite (for instance, only certain rows). You can also create "data groups." With data groups, you can group similar sets of data (such as development environment test data and load/performance test data), then easily switch which data set is used at any given time without having to edit the tool or data source configurations.

...

Icons also alert you if a repository is locked and, if so, by which user. For example, the following screenshot shows a repository locked to the user "cynthia".  Locking repositories requires authentication through Continuous Testing Platform (CTP).To show the Data Repositories view, choose go to Parasoft > Show View > Data Repositories.

...