Problem description
- Automated smoke testing on production environments after deployment
- Testing of activation of real contracts on production environments between DSO and AGR
There is already a TestMessage in the specification, but many times this will not be enough as it does not trigger all the logic that an activation of a real contract would.
Solution proposed
Add an optional DryRun or Test flag attribute to the generic metadata of all messages. This can be handled appropriately by still doing the full processing logic, but not really activating the power and leaving this data out of official reports.
Alternative solutions
- A special
ContractID or CongestionPoint value indicating a 'test' that all parties must agree on. Introduces more coupling and limits the number of use cases that can be tested to the set of values agreed beforehand.
Problem description
There is already a TestMessage in the specification, but many times this will not be enough as it does not trigger all the logic that an activation of a real contract would.
Solution proposed
Add an optional
DryRunorTestflag attribute to the generic metadata of all messages. This can be handled appropriately by still doing the full processing logic, but not really activating the power and leaving this data out of official reports.Alternative solutions
ContractIDorCongestionPointvalue indicating a 'test' that all parties must agree on. Introduces more coupling and limits the number of use cases that can be tested to the set of values agreed beforehand.