In my limited experience, configuration changes (small 1-3 line changes to a project config file), either completely break the program or do not seem to bring noticeable changes to the user-experience.
- As a QA should I be worried about my developers telling QA that only cursory smoke testing is required for a small configuration deployment?
- Are there any implicit, more nasty, and intermittent types of bugs that could be introduced through configuration changes?
I want to be a thorough QA contributor but also allow my team's developers to move quickly through the deployment and CI pipeline.
This is the particular change that brought about my question:
<add key="LightningQueueSettings.OldestMessageInProcessedHistory" value="10m" />
<add key="LightningQueueSettings.MapSize" value="1073741824" />
This occurred in a
JasperService.exe.config file. This change allows tons more messages from our database to propogate to this queue (it was being overflowed).