作为应用程序生命周期管理(ALM)的一部分,在测试方面没有快捷方式,但以下是在部署生产模型更改之前如何进行测试的指南,以最大程度地减少部署问题。作为利用ALM的决定的一部分,您应该创建“变更结构”并具有更改控制过程,如概述here。假设这已经到位,这里有一些技巧可以帮助最大程度地减少部署的不需要数据问题。
驾驶后的发展活动应具有与初始发展相同的重要性。作为其中的一部分,任何更改都应具有关联的user story,在那中验收标准。Acceptance criteria are the key to signing off a piece of development; it is the first part of testing known as ‘component’ or ‘functional’ testing. Functional testing should validate the work and prove out calculations (e.g. does the top-down value get allocated across all lower members correctly). However, depending on the level of complexity within the change, further testing may be necessary. More information on user stories and functional testing can be foundhere,as well as the训练课程。
Depending on the segregation of duties or customer requirements, the source data for the test model could be pointing to a QA environment or a production system. It is recommended that the开发模型始终用作来源for all test and production models. The advantages of this are as follows:
It is also recommended that the development and test environments are held within a separate workspace; this helps segregate responsibilities between developers and the business team (if that is required).
本文不会因为太多而贯穿所有测试协议,但是以下是如何检查更改前后的值的几个想法。
This approach works well if you expect changes to the values in certain parts of the model or you need a detailed analysis of particular differences. This approach involves creating a brand new“variance” model通过新更改验证方差。该模型将是剪切版本或生产模型的“外壳”。仅当您同时访问测试和生产工作区时,此方法才有可能。
The detailed steps from above are as follows:
注意,一旦设置了“方差”模型,就不需要重复步骤2。如果您重复生产模型(步骤3),则无需重复步骤5A;您需要做的就是将导入源重新映射到新复制的测试模型中。这是在“设置”选项卡 - “源模型”中完成的。
This approach works if you are expecting no change to the overall values in the model.
笔记:如果要使用此方法,强烈建议将设置构建步骤(步骤1)包含在单独的修订标签中,并在开始在主要更改上开发之前进行同步。这是因为您可能需要修改更改并运行另一个同步。
详细步骤如下:
在上述两种情况下,如果数据尚未预期:
如上所述,如果测试结果不如预期,并且更正问题的更改级别是实质性的,那么重新启动可能会更快,而不是更改修订标签中包含的更改的元素。
为了重复开幕词,没有测试的快捷方式。测试水平和风险或错误的水平将取决于变化水平。另一个最佳实践to mention, in conclusion, is to set and test revisions regularly. This, coupled with a structured development program, should help minimize issues in deployment and drive efficiency in your ALM process.
See part three of the series to understand how to recover from the worst-case scenario— a synchronization has caused data loss.
Just reading this i was wondering if reverting a modem back to before a revision tag using the history log track sets the model back before the revision tag and hence erasing the revision tag from the model, hence making a model with accidental structural changes and revision tag compatible again
并不是说是为了了解历史日志和ID如何处理修订。