search

intel / ozone-wayland

Wayland implementation for Chromium Ozone classes
BSD 3-Clause "New" or "Revised" License
218 stars 82 forks source link

Unittests. #26

Open kalyankondapally opened 10 years ago

kalyankondapally commented 10 years ago

Currently, we don't have any unit tests to check our Ozone specific changes.

tiagovignatti commented 10 years ago

content_browsertests looks promiser. I'd start from there.

kalyankondapally commented 10 years ago

@tiagovignatti Any update on this ?

is #30 related to this ?

tiagovignatti commented 10 years ago

noupe. Sorry I didn't have time to check this carefully yet. But we may need to check this ASAP now due the new gardening process.

The idea is that every time we want to sync our Ozone to a new version of Chromium, we run a bunch of selected tests and compare the passes rate with the previous version -- somewhat similar from what Blink does weekly: https://groups.google.com/a/chromium.org/forum/#!topicsearchin/blink-dev/testing$20weekly%7Csort:date/blink-dev/fueEqeJOXCg

the amount of passes/fails will give to us an indicative where/what to fix, or simply if we shouldn't be bumping to a new Chromium version. That's more less the idea I have in my mind but I want also to find out what kind of tools Chromium already provide for testing and discuss a bit in ozone-dev ML how to stress Ozone with efficiency.

kalyankondapally commented 10 years ago

@tiagovignatti That's what I had in mind too, with an additional thought of pre-commit validation. I.e. with every pull request we run a set of tests and ensure we don't regress. Let's see how it goes in practice.

kalyankondapally commented 10 years ago

I am moving this to next milestone.