16.03.2018, 00:12 | #1 |
Участник
|
stoneridgesoftware: How to Mitigate Risk with a Production System Smoke Test
Источник: https://stoneridgesoftware.com/how-t...em-smoke-test/
============== Modifications, code fixes and configuration changes to production systems are a necessity on a software implementation project. A formal testing procedure is recommended when major changes are made, but sometimes testing is minimized for smaller changes. Unfortunately, small changes can also lead to system outages and user frustration if not properly vetted or if key startup procedures are missed. Systems today are so complicated that even simple fixes can break existing functionality due to a relationship not documented or not completely understood. One way of mitigating the risk of outages caused by minor changes is to develop a standard production system Smoke Test. This smoke test should be performed after any change is made, but before all the users are given general access to the system. It would be ideal if the person performing this smoke test was independent of the group that had made the change or was not the group that stayed up all night long resolving the problem. Generally, smoke testing happens after formal testing, but in the case of minor system changes, formal testing may be considered unnecessary. The use of a “smoke test” in this case gives the systems group an early warning to issues that might easily be addressed before full production is resumed. Provided below are some examples of the tasks to be included in the standard smoke test. Standard Smoke Test Tasks: 1. Validate essential business processes For example:
For example:
For example:
Источник: https://stoneridgesoftware.com/how-t...em-smoke-test/
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору. |
|
|
|