Someone needs to take 5 minutes of their time to explain to testers what the actual fuck a "cache" is, the next time I'm receive these "urgent calls" fixable by pressing F5 I'm joining ISIS.

Start packing your bags then.. this will not happen only once, but multiple times!

How far away are your testers?

Our are well aware of what a cache is and quite a lot more and some have been doing coding.

Even our PM started out as a dev.

Two words: version queries.

How about you do it?

Don't enable cache for QA 🤪
I know... weird idea.

@C0D4 How do you simply 'not enable' browser cache? Always a case of working to disable it, no?

@spongegeoff
If only there was a header you could send.

Cache-Control

Or even appending a timestamp to a asset so each get request is served the lasted version.

There's plenty of ways to force a browser to not have a hard cache of files.

@jespersh I'm not going to change the very fragile building pipeline that has been built over several years to make sure we could use AngularJS in 2022.

@C0D4 So by 'not enabling' you do mean 'actively preventing' - the various headers, versioning etc .

@spongegeoff you can do it server side, which ensures even the most unintelligent QA can stop complaining, or somehow make the QAs use incognito / private mode of their browser to test your site.

I know which one is easier long term 😅

Besides, if you can't add a header for certain file types, your fragile pipeline probably needs the chopping block.

*Doorbell rings*
FBI, OPEN UP.

You are in a CryISIS. However you simply need to convince the testers that they are now part of an automotive test. They are dummies anyway. Use them appropriately.

The opposite can happen too.

We once explained to our customer service department how caching works. Later found out they pretty much respond to most technical issues filed by customers with instructions on how to clear the cache and try again..

Not a terrible bet "if something is wrong and not entirely obvious...could be cache" but it's gone too far