This user Story does not require Testing

I have seen this happen in different teams that I have been part of in my 6 years of experience in testing. Developers , Managers and sometimes Testers also discuss among themselves and proceed to a conclusion that a story does not need testing. it can have some reasons as : 

Minor change : This is just a one line change and it won't have any impact anywhere. For a tester, any change has the capability to crash the whole production. That’s why we test to find issues that users don’t have to face.

Database changes : Reasoning is like this the change is only at database level it doesn’t have any change in the code so no testing needed. As far as I know the values we see on ui have direct or indirect impact from db changes. Why not to test it ?

Analytics Changes: For an analytics related change, Developer adds analytics events which are fired when user interacts with application for tracking purposes. it doesn't have any impact on user behavior. Why should it be tested ? I have seen in a past project,  an analytics change which caused a mobile application crash. After that the team understood it needed to be tested .

Infra / Environment / configuration related change: Sometime it happens that DevOps wants to do some optimisation/ changes for services and assumes that tester only tests Developer code not DevOps changes. This here is a misunderstanding of tester's duties.

There can be xyz reasons provided to skip the story for testing the ultimate cause I think is to save time. However the same team will not think twice to invest more efforts and time to fix when an issue comes. I can say that for any change, the tester in the team should be able to come up with a couple of things that he/she wants to test. If they need help to understand the change , help them.

For any story with testing skipped, Team should be ready to face Impacts: 

1. Production Failure : If tester does not test the change then real user will and not in a good way. Real users will use your application in a myriad of ways causing issues which were not thought of while making the change. 
2. Investigation Time: If something is skipped from the process then it would be difficult to find out the root cause. Sometimes testers are involved in investigation for production issues. It would be difficult for anyone to find out the root cause if they don’t know what got released to production.
3. Impact on Mental Model : Most people don't know this but testers create models for application under test. It is basically a mental model of how an application responds to different interactions . If any change is skipped for testing then the tester will not update his mental model for application and don’t consider it as part of testing for any change afterwards.