What is the best approach to testing a service when u add 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?
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 dont see this addressed in continuous delivery book either
If you have confidence in your unit tests, then you should not need to do any more testing.
If you do not have confidence in your unit test, then you need to
rethink them. But in any case, you should not need to create tests
specific to a configuration change (presuming that you are talking
about changes like switching the base currency of the customer).
You wouldn't create a test each time a customer buys something,
so why should changing their configuration parameters be any
You received this message because you are subscribed to the Google Groups "Continuous Delivery" group.
I don't know of specific published guidance in this area. If it
exists, I would look for the question of when changes to master
data could be treated like a transaction and when they need to be
treated more like a change in logic. But I suspect that such
questions depend entirely on the structure of your solution, on
the degree to which you have made implicit assumptions about the
values of the configuration data. For example, if you build a
system where you assume that base currency of a customer will not
change, and then it changes, you are apt to need to review the
processing logic and perhaps also your data structures. And that
means adding tests. But if you have already built into your system
the logic to handle such changes, then your normal testing
(presumably automated) should be sufficient.
ThanksRobert.Do u known of any guidance in this area? I dont see any mention in books, articles on how to handle configuration changes