We use the solution to manage test cases. 

The solution used for DevOps Pipeline.

Broadcom Test Data Manager is used for test data management requirements, along with data generation, data masking, data subsetting, and service virtualization. Also, the solution can be connected to your automation tool.

Data masking, exactly what this tool is created for. We are going to use it for the incorporation into test or development environments.

We are managing a lot of customer data, and the idea is to not have, or approve, or give a lot of permissions to read all this data. We need to mask them, but we still need to work with them, which means that developers need access to a lot of data.

We have needed a tool where the data provided for developers should be easy and anonymized. This is probably the one and only tool with so many sophisticated features. We need those features for masking/anonymizing data with statistical distribution and with preparation of test/dev data (a lot of data).

Generate synthetic test data.

It has performed fine. It provides us the capabilities that we were anticipating.

We are using it to implement test data management.

It is a new implementation so there were some challenges. But so far, it has been good.

We use a lot of creating data mods and test matching features. We did establish the subsetting cloning process as well, but based on the client requirements. Creating data mods and using test matching features are something which we have found fits our purpose. We use most of the test matching features in our testing processes and also the integration with App Test is something we heavily use.

TDM is something people do all the time. You cannot say it is something you're going to do from scratch. For every client, there is a different scenario. There are a lot of use cases. But a couple of use cases are common everywhere. One of them is the data when it is not there in production. How do you create that data? Synthetic data creation is one use case challenge that is common across the board.

In addition, the people who do the testing are not very conversant with the back end or with the different types of databases, mainframes, etc. And most of the time they don't write very good SQL to be able to find the data they are going to do their testing with. So data mining is a major concern in most places. 

The use cases are diverse. You cannot point to many common things and say that this will work or this will not. Every place, even though it's a TDM scenario, is different. Some places have very good documentation, so you can directly start with extraction, masking, and loading. But for most places that is not possible because the documentation is not there. There are multiple use cases. You cannot say that one size fits all.

In the testing cycle, when there is a need for test data management tools, we use CA TDM to put up the feed.

We use it for enterprise-level solutions.

One thing that we're using Test Data Manager for, is to build data marks so that we can test APIs of our application using users from every company within our application.

We use it for data generation, for performance testing, and other test cases. We also use data masking and data profiling for functional testing. Data masking is one of the important aims in our procurement of this tool because we have some sensitive data in production. We have to mask it to use it in a testing environment. Our real concern is masking and we are learning about this subject.

Test Data Management solution for our DevOps model, which is very useful. Data privatization (GDPR enable), synthetic test data generation, and test data provisioning are its main interesting features.

Monitoring network devices using SNMP. It works very well. 

We are having a serious trouble delivering and providing development environments and test environments for the diversifications that we use at the bank. What we are trying to do is use the time for that delivery, and that is why we are exploring using CA tools for networks. We already have the Server Virtualization tool, and now we are entering into the test of the management phase of tables.

As part of the DevOps function, what we are trying to do is create a subset in masked environments that is the basis for our development and testing. In the health care industry, we have a lot of concern with PII and PHI, so making sure that it is not exposed in non prod environments. Also, lessening the amount of disk space which is used for these environments, making it faster, speedier to market, etc.

So far, it is performing well. We are still in our initial build out phase, but it is all coming together. 

What we do is we generate data that we use to generate like socials. We can also virtualize the bureaus that the software calls out to, so we can get a good response back that we can simulate.