Management of test data in system development

... ... ...

There are few development sites that manage test data correctly and make the test process of system development effective.

There are automated tests and frameworks that support them, but I don't think there are many development sites that have mastered them. In addition, there are many sites such as "I don't have time to write test code for automatic testing" and "No such man-hours have been prepared from the beginning." I think that the site of system development is a low-tech industry that has not even undergone an industrial revolution and is mainly manual work that has not been fully mechanized.

What about developers? Even if I feel a problem at the development site, I will not do my best to make proposals to improve development efficiency to my boss. Because they are busy with the work in front of them, and they are busy with time every day. I spend my days fighting tight schedules and bugs without thinking about how much profit will be produced as a result of system development.

On the other hand, what about well-known IT companies that are making a lot of money? Leading the fields of system development and applications, they look back on their work every day, constantly working on improvements, and are steadily causing an industrial revolution in industries below the industrial revolution. The mechanism is not open to the public, but it has created something that seems to have never been done manually, and has produced results and contributed to the world. Probably, it seems that we are working to improve the tools for system development in-house, reduce waste, and make the system development site more rational. Of course, some might argue that you can do it because you have that much capital, but that doesn't mean you can continue low-tech development because you don't have the capital. Not a little. We should invest in the field environment of system development and get out of this situation as soon as possible. Expense calculation in the field of system development is very easy. It's an unwavering fact, but most of the development costs are developer labor costs. If developers don't do unnecessary work, it directly leads to cost reduction. It's time to seriously consider which is cheaper, the labor cost of doing wasteful work or the amount of investment in the development site that avoids wasteful work.

Consider the test process in the field of system development. Testing is to ensure that a system works properly, but many systems have in common an input and an output. What kind of data is input and what kind of data is output? In the test process, the system is verified to be operating correctly by performing such a series of confirmations. If you don't manage the inputs in this test well, you can't be sure that the output was correct even if you do the test. As a result, trouble occurs in the system that delivered the product without finding the bug hidden in the system. It's a story that is often heard, but it wasn't expected. I think many developers have problems managing test data? In fact, as I am involved in development, I see many sites that have such problems. What kind of tests did the administrator who manages the system development also perform? What kind of test data did you use to test even after checking? I haven't been able to supervise. Therefore, I would like to explain that DBUpdateTool works very effectively as a means to solve such problems.

Manage test data in Excel file

An easy way to manage test data is to use Excel. Perhaps the most common method is to have an Excel workbook, enter the table name in an Excel sheet, retrieve the data from a tool that references table data in the database, and paste it into an Excel cell. Some tools do not copy the column names, so you may have to enter only the column names manually. Then, prepare a worksheet function that generates an "INSERT" or "DELETE" statement in any cell in each row, and use the generated "INSERT" or "DELETE" statement as a tool for executing SQL. Copy and execute SQL. Isn't the test data replaced by repeating this for the required number of tables? If you're still doing this kind of work, it seems very stupid and poor.

The problem can be solved with DBUpdateTool

With DBUpdateTool, you can create and replace test data without much hassle. The labor cost of developers is very high. In system development, most of the cost is the labor cost of the developer, so reducing the wasteful work done by the developer by even one minute is the key to reducing the cost of the entire system and generating the maximum profit. .. The cost performance of DBUpdateTool is the best. It will surely yield more than 10 times the investment amount. We hope that you will introduce it and your system development will become smarter.



About me

I'm "Hi-Neko" from the LASIS Support Center. We will continue to develop better products, so we look forward to working with you.

Lasis Corporation