Verifying Content-Security Policy with Selenium and Cuprite | Arkency Blog

Once upon a time, a fellow RailsEventStore enthusiast reported an issue. It turned out that the RES::Browser component was not compatible with a quite reasonable Content-Security Policy they were using in their Rails app. His report led to an interesting discussion. Eventually, one pull-request later, the project gained new contributor and a more CSP-friendly setup.How did we ensure that this improvement will not be broken in future releases without manual testing? Read on.
Verifying Content-Security Policy with Selenium and Cuprite | Arkency Blog #ruby #rubydeveloper #rubyonrails #blog

Nezir Zahirovic

Contractor Ruby On Rails (8+ years) / MCPD .Net / C# / Asp.Net / CSS / SQL / (11 years)

related articles