Grails 构建测试数据
是否建议使用 build-test-data 插件加载应用程序的引导（种子/初始）数据。插件教程非常好，位于 http://bitbucket.org/tednaleid/grails- test-data/wiki/Home ，但只提到加载测试数据。有一个关于 TestDataConfig 的部分，它允许设置默认数据。但如果数据需要以更大规模、具有复杂关系的方式持续存在，那么这是一个可行的选择吗？ 谢谢。
Is it advisable to use the build-test-data plugin to load the bootstrap (seed/initial) data for an application. The plugin tutorial is excellent at http://bitbucket.org/tednaleid/grails-test-data/wiki/Home , but only mention about loading test data. There is a section about TestDataConfig , which allows to set default data. But is it a viable option if the data needs to persist in a larger scale, with complex relations.\
thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
测试数据是该插件的主要焦点，但我将它用于各种数据加载情况，包括将数据引导到新系统中。
您唯一需要注意的是，根据设计，该插件将填补您未提供的所需数据中的任何漏洞。这意味着您应该指定您实际想要特定值的所有内容（或将其放入您提到的 TestDataConfig 中）。如果您不给 build-test-data 一个值，它会编造一些东西，而这可能是您不想要的东西。
围绕 buildLazy 新增的功能使您可以更轻松地连接到 BootStrap 配置中可能拥有的现有对象图。
Testing data is the primary focus of the plugin, but I use it for all kinds of data loading situations, including bootstrapping data into a new system.
The only thing you need to be aware of is that the plugin, by design, will fill in any holes in required data that you don't supply. This means that you should specify everything that you actually want specific values on (or putting it in the TestDataConfig that you mention). If you don't give build-test-data a value, it'll make something up and that might be something that you don't want.
The newly added functionality around buildLazy makes it even easier to hook into an existing graph of objects that you might have in a BootStrap configuration.
这取决于你的数据。如果您只需要管理员帐户信息、类别列表等一些信息，那么它应该可以正常工作。如果您使用初始种子数据测试您的应用程序并且一切正常，我会使用它。对于大型或复杂的数据导入，我将使用甘特脚本来创建和保存所有域对象。例如，我正在开发一个项目，该项目要求我将数据从遗留数据库移至 grails 应用程序中。为此，我运行一个脚本，该脚本使用 JDBC 调用从旧数据库中获取所有旧数据。然后，我根据这些数据创建并保存新的域对象。有关如何运行可以访问包括 Gorm 在内的整个 Grails 上下文的脚本的示例，请参阅 这个
It depends on your data. If you only need a few things like administrator account info, list of categories, etc it should work fine. I'd use it if you’re testing your app with the initial seed data and everything works fine. For large or complex data imports I'd use a gant script to create and save for all the domain objects. For example I'm working on a project that requires me to move data out of a legacy database into a grails application. For this I run a script that uses JDBC calls to get all the old data out of the legacy database. I then create and save new domain objects based off this data. For an example of how to run a script that has access to the entire Grails context including Gorm see this