![]() ![]() We cannot give someone data which will be rejected from system Z. Nobody has a clue how that data gets there for testing, because that end-to-end testing has never happened. Suppose I have a system, and that system gives data to system Y, and Y gives data to system Z. From what I have seen, most companies lack the basic building blocks for testing. I have been working in testing environments for the last 10 or eleven years. In the testing cycle, when there is a need for test data management tools, we use CA TDM to put up the feed. ![]() But for most places that is not possible because the documentation is not there. 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. ![]() You cannot point to many common things and say that this will work or this will not. So data mining is a major concern in most places. 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. 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. How do you create that data? Synthetic data creation is one use case challenge that is common across the board. One of them is the data when it is not there in production. But a couple of use cases are common everywhere. For every client, there is a different scenario. You cannot say it is something you're going to do from scratch. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |