We need to figure out a way to test in safari. Maybe using BrowserStack? @sindresorhus @Zirro

Travis supports osx as an OS, which has Safari.

Travis supports osx as an OS, which has Safari.

Worked like a charm ☺️

There are some future issues:

• Validate some inconsistencies in safari (text-decoration)
• Testcafe does not support pseudo-elements selector (Add possibilty to use CSS pseudoclasses and pseudoelements in Selectors DevExpress/testcafe#2813)

Even so, everything seems to be alright. @sindresorhus @Zirro

Why are there duplicate test files for each browser?

Each browser has it's own style property values, like some line-heights and vendor properties (-webkit-appearance, -webkit-text-size-adjust, -moz-tab-size). What's more, we need to run some assertions that is valid only in one browser, like "Remove the inner border and padding in Firefox.", that does not even exists on chrome and safari (-moz-focus-inner).

I've sepparated the tests into two types. The rules.ts files are assertions in a page loading the modern-normalize CSS, the objective is to assert if the given rule is applied correctly. The validation.ts files are assertions in a page without the CSS module, the objective is to catch the changes on the newest browsers versions and remove the old rules.

I would really appreciate some feedback and improvements. It was troublesome to test some scenarios like safari's font on different platforms (my pc vs travis mac). 😁

@rafaelfbs Sorry for leaving this for so long. I just had to many PRs to review. Can you fix the failing tests?

@sindresorhus Tests passing.

Looking good. Thanks for working on this ❤️