It's entirely driven by your organization's needs and understanding what you require before deciding on a feasibility schedule for any tool. However, I would say that the Broadcom Test Data Manager has almost all the features we're looking for in a testing tool. It aligns well with the market in terms of capabilities and functionalities. You can get 80-90 percent of features and capabilities within the product. I rate it a nine out of ten.
I would say implementing test data management requires a lot of effort and time. Many organizations fail to provide sufficient support and time since most organizations think that they have the tools, licenses, and people to solve their problems. However, that's not the case. Even if you have experienced people, it takes time. So, in my first organization, it took almost four years for us to give synthetic data generation capabilities. Certainly, we should implement Broadcom Test Data Manager, but the organization doing so should have time and patience. Overall, I rate the solution a nine out of ten.
Practice Head - Digital Testing at a tech services company with 10,001+ employees
Real User
2019-01-10T08:22:00Z
Jan 10, 2019
I have been acquainted with this tool for three-and-a-half years and, since it was acquired by CA, we have worked pretty closely with CA to give feedback on what is expected out of the tool. We have worked very closely with the developers, as well, to enhance the tool. We have two or three clients using it.
It's important to know the requirements of your system, for example, the security policies you have to observe. The requirements may include a concern about relational or other database systems. You have to know your systems. Depending on your system, consider using one or more consultants, because we had a problem just using one. Also, compare all the tools by doing proofs of concept. That's important. We have been using it for three months, but before that we also did a proof of concept in stages for about a year. Regarding future use, we plan to use it in automation testing with content integration tools. Before running the automated tests, we will prepare our generated data with TDM. We also have a future plan for storage virtualization and use of Docker applications. It is possible that for Docker we would also use the TDM rule set. I want to believe it's scalable. We have five testers using it to write rules. We also have 20 business analysts using and running these rules. In terms of maintenance, two developers would be enough. Our consultant coached our developers regarding our requirements. A testing engineer would also be okay for maintenance.
There are, let's say, five market-standard tools you can choose from. If you choose CA TDM, you need to bring out all your questions for your PoC journey. You have four weeks to get answers to whatever questions you have. There is a set of experts at CA and partners have expertise as well. Both will be able to answer your questions. Next, you need to supply a roadmap. For example, "I need X, Y, and Z to be tackled first." And the roadmap that comes out of the due diligence needs to be followed word-for-word. So proper planning is essential. There are three teams which are at the base of your TDM journey. One team is a central data commandment team, one is a federated team, and the third is for creating small tools that you might require at that point in time. To start, you need three to four people. But we have gotten into all types of data: Big Data, RPA, performance; etc. Wherever data is needed, our team is providing the data. In a bank, for example, where I did two rounds of due diligence, one lasting eight weeks and the other, three years later, lasting six weeks, we even implemented bots. When we started there the team was 50. Even though we automated the whole thing, more than what anyone might have even imagined, the team is still 40-plus.
Learn what your peers think about Broadcom Test Data Manager. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
I would certainly recommend this product, because of the vast variety of data it provides for testing and its different features, like subsetting and cloning. I have heard of products which can do cloning and similar stuff, but there are many additional features in this tool, which is very useful for the testing and finding defects. We found we mostly use one or two features, so we need to be very clear on what we need before choosing a product. Test Data Manager is good, and there are a lot of advantages that you get from using the tool, especially for testing and incubating with the App Test, which is something that we use a lot.
Broadcom Test Data Manager focuses on creating, managing, and provisioning test data for software testing, ensuring data privacy and compliance, and supporting testing across multiple environments efficiently.
Broadcom Test Data Manager integrates with databases, automates data generation, and enhances test data quality and reliability, leading to improved testing accuracy and faster release cycles. It includes a self-service portal, ease of use, and capabilities for data generation,...
It's entirely driven by your organization's needs and understanding what you require before deciding on a feasibility schedule for any tool. However, I would say that the Broadcom Test Data Manager has almost all the features we're looking for in a testing tool. It aligns well with the market in terms of capabilities and functionalities. You can get 80-90 percent of features and capabilities within the product. I rate it a nine out of ten.
I would say implementing test data management requires a lot of effort and time. Many organizations fail to provide sufficient support and time since most organizations think that they have the tools, licenses, and people to solve their problems. However, that's not the case. Even if you have experienced people, it takes time. So, in my first organization, it took almost four years for us to give synthetic data generation capabilities. Certainly, we should implement Broadcom Test Data Manager, but the organization doing so should have time and patience. Overall, I rate the solution a nine out of ten.
I would give Broadcom TDM a rating of eight out of ten.
I have been acquainted with this tool for three-and-a-half years and, since it was acquired by CA, we have worked pretty closely with CA to give feedback on what is expected out of the tool. We have worked very closely with the developers, as well, to enhance the tool. We have two or three clients using it.
It's important to know the requirements of your system, for example, the security policies you have to observe. The requirements may include a concern about relational or other database systems. You have to know your systems. Depending on your system, consider using one or more consultants, because we had a problem just using one. Also, compare all the tools by doing proofs of concept. That's important. We have been using it for three months, but before that we also did a proof of concept in stages for about a year. Regarding future use, we plan to use it in automation testing with content integration tools. Before running the automated tests, we will prepare our generated data with TDM. We also have a future plan for storage virtualization and use of Docker applications. It is possible that for Docker we would also use the TDM rule set. I want to believe it's scalable. We have five testers using it to write rules. We also have 20 business analysts using and running these rules. In terms of maintenance, two developers would be enough. Our consultant coached our developers regarding our requirements. A testing engineer would also be okay for maintenance.
There are, let's say, five market-standard tools you can choose from. If you choose CA TDM, you need to bring out all your questions for your PoC journey. You have four weeks to get answers to whatever questions you have. There is a set of experts at CA and partners have expertise as well. Both will be able to answer your questions. Next, you need to supply a roadmap. For example, "I need X, Y, and Z to be tackled first." And the roadmap that comes out of the due diligence needs to be followed word-for-word. So proper planning is essential. There are three teams which are at the base of your TDM journey. One team is a central data commandment team, one is a federated team, and the third is for creating small tools that you might require at that point in time. To start, you need three to four people. But we have gotten into all types of data: Big Data, RPA, performance; etc. Wherever data is needed, our team is providing the data. In a bank, for example, where I did two rounds of due diligence, one lasting eight weeks and the other, three years later, lasting six weeks, we even implemented bots. When we started there the team was 50. Even though we automated the whole thing, more than what anyone might have even imagined, the team is still 40-plus.
I would certainly recommend this product, because of the vast variety of data it provides for testing and its different features, like subsetting and cloning. I have heard of products which can do cloning and similar stuff, but there are many additional features in this tool, which is very useful for the testing and finding defects. We found we mostly use one or two features, so we need to be very clear on what we need before choosing a product. Test Data Manager is good, and there are a lot of advantages that you get from using the tool, especially for testing and incubating with the App Test, which is something that we use a lot.