What is the best approach to testing a service when you add a new configuration? For example my service offers a service to a customer and based on the customer configuration, it will offer a different type of service. E.g. if the customer selects a particular currency they are offered a 20% discount compared to another currency.
The example above does not matter. What matters is the approach people are taken when doing CI\CD
The logic for working out the discount is in the domain and has unit tests around it. My question is if you have merchants configured with different rules to figure out the discount (all based of configuration and the domain works it out), then if a request comes in to change the configuration how do you verify it?
- Do you write more tests?
- Do you not test as already in unit tests?
- Manually test changes?
I have read xUnit Test Patterns and Test-Driven Development books along with many articles but have not come across how people manage this (configuration changes within service and verifying correctness).
I don't see this addressed in continuous delivery book either.