HTTP cookies are an essential part of many web based applications, useful for tracking session and state information. But they can also be exploited to leak information to third party sites using a ...
I found this which was really helpful for pre-testing:
What do publishers need to do in order to get ready for February?
Publishers can begin testing whether their sites are affected by going to chrome://flags<>> and enabling #same-site-by-default-cookies and #cookies-without-same-site-must-be-secure to see whether anything breaks. They should also migrate to HTTPS secure pages, if they haven’t done so already.
lifted from https://digiday.com/media/what-is-chrome-samesite/