AuroraMiddleware/gtk
1
0
Fork 1
mirror of https://gitlab.gnome.org/GNOME/gtk.git synced 2025-01-03 17:21:11 +00:00
Code Issues Projects Releases Wiki Activity
cb339f85b8
gtk/testsuite/gsk/meson.build

605 lines
17 KiB
Meson
Raw Normal View History

build: Drop the install-tests option We no longer use installed tests in CI, so lets reap the benefit and simplify our build setup for tests.
2022-12-20 04:11:20 +00:00
compare_render = executable('compare-render',
testsuite: Add render node replay tests This takes a render node tree and "replays" it by using the GtkSnapshot machinery. We don't necesserily expect to get back an exactly equal render node tree back, since GtkSnapshot applies various small optimizations where possible, but the original and the replayed nodes should render to identical textures. Signed-off-by: Sergey Bugaev <bugaevc@gmail.com>
2023-08-16 15:46:20 +00:00
['compare-render.c', '../reftests/reftest-compare.c', 'replay-node.c'],
tests: Link compare-render statically This is a temporary change, only needed until we make the new snapshot and rendernode apis public.
2024-08-05 20:09:42 +00:00
dependencies: libgtk_static_dep,
Try to fix win32 build of compare-render
2024-08-06 04:53:19 +00:00
c_args: common_cflags + ['-DGTK_COMPILATION'],
testsuite: Add selected gl renderer test node files
2017-12-25 11:56:21 +00:00
)
build: Drop the install-tests option We no longer use installed tests in CI, so lets reap the benefit and simplify our build setup for tests.
2022-12-20 04:11:20 +00:00
node_parser = executable('node-parser', 'node-parser.c',
testsuite: Add tests for the new node parsing code This adds a test tool gsk/node-parser that takes node files and parses them. A few of these node files have been added, for crashes I encountered while developing the new parsing code.
2019-03-19 04:29:20 +00:00
dependencies: libgtk_dep,
Pass common_cflags to testuite/gsk executables
2020-05-18 09:44:38 +00:00
c_args: common_cflags,
testsuite: Add tests for the new node parsing code This adds a test tool gsk/node-parser that takes node files and parses them. A few of these node files have been added, for crashes I encountered while developing the new parsing code.
2019-03-19 04:29:20 +00:00
)
Move working tests to new directory These are tests that are working on both GL and Cairo now. Some tests got black boxes over the areas that aren't easy to compare.
2019-03-19 07:16:07 +00:00
compare_render_tests = [
gsk: Add test for clipped big glyphs Tests the fix in the previous commit 93715b963eed9975b9b7a. Sadly, the flipped variant of this test fails with the cairo renderer, so it is marked as -nocairo. All the other renderers pass it.
2024-01-12 04:04:31 +00:00
'big-box-glyph-nocairo',
testsuite: Add some texture tests In constrast to our other tests, these use textures that are big enough to force slicing with setting GSK_MAX_TEXTURE_SIZE, which we will use in the following commits to improve test coverage.
2023-03-19 14:05:52 +00:00
'big-checkerboard',
'big-checkerboard-scaled-down',
'big-checkerboard-scaled-down-nearest',
gsk: Add a test for scaled textures GL and cairo disagree on this one, and have forever. Whee!
2023-03-20 00:25:14 +00:00
'big-checkerboard-scaled-down2',
rendernodeparser: Parse images differently Instead of encoding the raw data, encode the full image to a PNG. And instead of stuffing that encoding into a string, use a full data: url. And then remove the width and height properties, because they're now implicitly included in the data. And then change the parser to match. And because the parser now parses regular urls on top of data: urls, we can now load any random file.
2019-05-09 01:56:25 +00:00
'blend-difference',
Add another test
2023-04-30 20:16:32 +00:00
'blend-modes',
testsuite: Sort gsk compare tests Easier to find things that way.
2021-04-01 21:03:54 +00:00
'blend-invisible-child',
Add a test for rotated blend nodes
2023-05-01 00:28:12 +00:00
'blend-in-rotate',
testsuite: Sort gsk compare tests Easier to find things that way.
2021-04-01 21:03:54 +00:00
'blend-normal',
gl: Fix padding in icon library The previous code would not pad the left side with the left column of pixels but with the top row. Test attached.
2023-10-25 19:12:23 +00:00
'blurred-lines',
testsuite: Disable all failing tests on GL renderer Of all the recently added tests, disable the ones that fail on the GL renderer, so that CI passes.
2023-12-26 03:17:21 +00:00
'blur-child-bounds-oversize-nogl',
cairo: Handle clipped blur content This is the result of experimenting with corner cases when blurring. The result is a test that tests when the child of a blur node is clipped out but the blurred child is not, the blurred parts are still visible. This immediately broke the cairo renderer, so the fix is included.
2023-12-05 16:07:54 +00:00
'blur-contents-outside-of-clip',
testsuite: Disable all failing tests on GL renderer Of all the recently added tests, disable the ones that fail on the GL renderer, so that CI passes.
2023-12-26 03:17:21 +00:00
'blur-huge-contents-outside-of-clip-nogl',
ngl Fix bottom-right border render failure The wrong index was used for offsetting the bottom border rect. Test included.
2021-09-16 00:28:56 +00:00
'border-bottom-right',
Add a compare test for colorstates in borders
2024-08-05 16:09:49 +00:00
'border-colorstates',
Add another gsk test
2023-04-15 20:55:24 +00:00
'border-one-rounded',
testsuite: Add a test for borders inside opacity Tests the latest fix.
2024-01-08 08:13:39 +00:00
'border-opacity',
testsuite: Add a test for zero width borders See previous commit for an explanation of the problem. This test actually draws a rounded border, but the rounding is clipped away. What is remaining is the 4 corners of the border, where the top/bottom color is red and the left/right color is green. But because the bottom/right side has a width of zero, the result should be all red.
2024-01-25 18:34:28 +00:00
'border-zero-width-color',
testsuite: Sort gsk compare tests Easier to find things that way.
2021-04-01 21:03:54 +00:00
'borders-rotated',
'borders-scaled',
testsuite: Add a test for contained clips Related: #6322
2024-01-12 18:28:35 +00:00
'clip-contained',
Update gsk tests Add a clip-coordinates-2d test that is similar to clip-coordinates-3d, but actually uses a 2D transform.
2020-09-02 22:05:16 +00:00
'clip-coordinates-2d',
testsuite: Unify renderer exclusion naming Instead of using "-3d" to exclude Cairo rendering, use "-no$renderer" to allow excluding any renderer. And because we use contains() for the check, we can exclude multiple renderers by naming the test sth like "test-nogl-nocairo.node"
2023-12-19 17:04:18 +00:00
'clip-coordinates-nocairo',
testsuite: Sort gsk compare tests Easier to find things that way.
2021-04-01 21:03:54 +00:00
'clip-in-rounded-clip1',
'clip-in-rounded-clip2',
'clip-in-rounded-clip3',
testsuite: Add a test for previous commit Related: #6389
2024-02-04 20:56:15 +00:00
'clip-in-smaller-rounded-clip',
testsuite: Add a test for a clipping cornercase If the new clip cannot intersect with the old clip and there is a global opacity setting, things can go wrong. So test that they don't.
2023-12-29 21:08:44 +00:00
'clip-intersection-fail-opacity-nogl',
testsuite: Make clipped-repeat test work universally Cover the rounded corners so that they cause no visible difference in the end result.
2023-05-21 03:40:26 +00:00
'clipped-repeat',
Move working tests to new directory These are tests that are working on both GL and Cairo now. Some tests got black boxes over the areas that aren't easy to compare.
2019-03-19 07:16:07 +00:00
'clipped_rounded_clip',
testsuite: Sort gsk compare tests Easier to find things that way.
2021-04-01 21:03:54 +00:00
'clip-nested1',
testsuite: Add clip-translate-offscreen test This was an experiment where an offscreen was translated inside an existing clip. Because renderers try to limit offscreens to the clip rect, this is interesting, because they might get the translation wrong.
2023-05-10 19:56:53 +00:00
'clip-translate-offscreen',
rendernodeparser: Parse images differently Instead of encoding the raw data, encode the full image to a PNG. And instead of stuffing that encoding into a string, use a full data: url. And then remove the width and height properties, because they're now implicitly included in the data. And then change the parser to match. And because the parser now parses regular urls on top of data: urls, we can now load any random file.
2019-05-09 01:56:25 +00:00
'color-blur0',
rendernodeparser: Parse cairo script Use cairo-script-interpreter to parse the scripts that generate cairo nodes. This requires libcairoscriptinterpreter.so to work properly, but if it isn't found we disable this (unimportant for normal functioning) code and just emits a parser warning. The testsuite requires it however or it will fail. A new test is included that tests all of this.
2019-05-28 03:51:20 +00:00
'color-matrix-identity',
testsuite: Add color-matrix-merge testcase This tests the merging of nested color matrix nodes feature of GtkSnapshot, which was broken before commit 082fdfdb241bb5dc38cd2c71c5650fd87ce1dded. Signed-off-by: Sergey Bugaev <bugaevc@gmail.com>
2023-08-17 09:44:34 +00:00
'color-matrix-merge',
nodeparser: Fix parsing of color-matrix node Negative offsets in the color matrix were inverted because it used the rect parser.
2022-05-18 19:16:33 +00:00
'color-matrix-parsing',
Add a compare test for color states This checks that the red values in all 4 default color states come out identical to a plain old red png.
2024-08-03 20:43:40 +00:00
'color-states',
gl: Interpolate gradient colors as premultiplied Tests included
2024-08-11 15:31:40 +00:00
'conic-gradient-premultiplied-nocairo',
testsuite: Add a test for conic gradients Make all colorstops red, so that it's obvious what color each pixel is.
2023-12-27 00:43:03 +00:00
'conic-gradient-with-64-colorstops',
gsk: Respect offscreen_for_opacity of first child The container node constructor forgot to initialize that value from the first child. Testcase included. Fixes #6350
2024-01-22 17:21:47 +00:00
'container-single-child-offscreen-for-opacity',
testsuite: Add crossfade-clip-both-children test This one tests a crossfade between two non-overlapping nodes with a clip region that covers neither of the two nodes. This tests that renderers can deal with clip regions that doesn't overlap nodes in a situation where they will most likely want to create an offscreen. As offscreens are typically clipped to the clip region, this would cause an empty offscreen and that can cause failures.
2023-05-10 20:14:26 +00:00
'crossfade-clip-both-children',
testsuite: Disable all failing tests on GL renderer Of all the recently added tests, disable the ones that fail on the GL renderer, so that CI passes.
2023-12-26 03:17:21 +00:00
'cross-fade-clipped-with-huge-children-nogl',
testsuite: Add cross-fade-in-opacity test Making sure that an opacity node doesn't end up reviving a node that's hidden because the cross-fade has progress 0 or 1.
2019-04-24 10:48:59 +00:00
'cross-fade-in-opacity',
Add a test for rotated cross-fade nodes This one checks that we don't apply the modelview transform twice with cross-fades.
2023-05-01 00:20:12 +00:00
'cross-fade-in-rotate',
Add some more gsk tests The css-background test contains a node pattern that is optimized in the ngl renderer.
2021-04-01 21:00:31 +00:00
'css-background',
testsuite: Add tests for dihedral transforms Just to make sure stuff shows up in the right place.
2024-07-09 18:43:58 +00:00
'dihedral',
testsuite: Add render tests for all the empty nodes Test that rendering empty nodes succees. For a lot of nodes the resulting rendering isn't clearly defined, in those cases we overdraw those regions (sometimes the whole image) with black.
2019-05-20 01:32:30 +00:00
'empty-blend',
'empty-blur',
'empty-border',
rendernodeparser: Parse Cairo nodes We also print the script, but we don't parse it yet.
2019-05-25 22:50:13 +00:00
'empty-cairo',
testsuite: Add render tests for all the empty nodes Test that rendering empty nodes succees. For a lot of nodes the resulting rendering isn't clearly defined, in those cases we overdraw those regions (sometimes the whole image) with black.
2019-05-20 01:32:30 +00:00
'empty-clip',
'empty-color',
'empty-color-matrix',
'empty-container',
'empty-cross-fade',
'empty-debug',
testsuite: Add test for empty glshader node Everyone should draw the error pink here, because that's what the renderers not supporting it do, and it's also what the default shader does. So no matter if a renderer supports GL shaders or not, it should draw the same pink.
2024-07-11 06:02:57 +00:00
'empty-glshader',
testsuite: Add render tests for all the empty nodes Test that rendering empty nodes succees. For a lot of nodes the resulting rendering isn't clearly defined, in those cases we overdraw those regions (sometimes the whole image) with black.
2019-05-20 01:32:30 +00:00
'empty-inset-shadow',
Skip some tests with small textures When textures are too large, we will scale them down to fit the max texture size, which will cause comparisons to fail.
2023-05-01 20:00:24 +00:00
'empty-linear-gradient',
Add more mask node tests
2023-02-15 00:04:34 +00:00
'empty-mask',
testsuite: Add render tests for all the empty nodes Test that rendering empty nodes succees. For a lot of nodes the resulting rendering isn't clearly defined, in those cases we overdraw those regions (sometimes the whole image) with black.
2019-05-20 01:32:30 +00:00
'empty-opacity',
'empty-outset-shadow',
'empty-repeat',
'empty-rounded-clip',
'empty-shadow',
'empty-texture',
'empty-transform',
Add compare tests for fill and stroke nodes
2023-08-07 11:09:42 +00:00
'fill',
Add another path fill test This uses the other fill rule.
2024-03-09 04:34:30 +00:00
'fill2',
testsuite: Add clipped overly large paths ... to make sure that renderers clip any masks they generate for paths.
2023-12-29 06:13:49 +00:00
'fill-clipped-nogl',
testsuite: Add tests for pixel grid accuracy See previous commit for details.
2024-01-09 16:16:05 +00:00
'fill-fractional-translate-gradient-nogl',
'fill-fractional-translate-nogl',
testsuite: Add opacity handling test for fill nodes
2023-12-27 17:18:12 +00:00
'fill-opacity',
testsuite: Add a test for previous fix Fill a rectangle with fractional coordinates << 1.0 but scale it up so that it ends up being nice integers. Makes sure that nobody does any bad rounding here.
2024-01-08 07:25:34 +00:00
'fill-scaled-up',
testsuite: Add a test filling 3d content Checks that a simple Cairo fallback cannot be used.
2023-12-27 16:00:13 +00:00
'fill-with-3d-contents-nogl-nocairo',
testsuite: Add a test to exhaust the glyph cache See previous commit.
2024-01-14 04:11:01 +00:00
'glyph-cache-overflow',
testsuite: Overflow slices of glyph cache This test is specifically engineered to trigger an overflow in the glyph renderer that was theorized on IRC with an earlier patchset. If only one slice was available, and that slice was not high enough to hold the glyph we were trying to put in there, it would allocate a slice that was too small. The check for the size was missing. So now add a test that fills up all the slices in the glyph cache apart from one and than tries to add one final glyph that is too large for the last slice.
2024-01-22 06:43:31 +00:00
'glyph-cache-overflow-slices',
Add glyph hinting tests Add tests that demonstrate different rendering with and without hinting, to prove that hinting has an effect.
2024-03-02 17:58:55 +00:00
'glyph-hinting-none',
'glyph-hinting-slight',
Add tests for glyph positioning These tests check that we round glyph positions to integral device pixel coordinates when hinting is enabled, and to device subpixel positions if it isn't.
2024-03-03 18:54:33 +00:00
'glyph-hinting-position-nogl-nocairo',
'glyph-subpixel-position',
Add a glyph scaling test The glyph in this test has extents that will be made smaller by hinting, which poses some challenge for our renderers. The scaled glyph rendering is too big for the 'small texture' text setup, so we allow the test to fail there.
2024-02-29 01:57:44 +00:00
'glyph-scaling',
Add glyph antialiasing test This test checks that the antialias font option has the indended effect.
2024-02-29 17:39:17 +00:00
'glyph-antialias',
renderers: Handle large viewports When large viewports are passed to gsk_renderer_render_texture(), don't fail (or even return NULL). Instead, draw multiple tiles and assemble them into a memory texture. Tests added to the testsuite for this.
2022-02-25 02:40:57 +00:00
'huge-height',
'huge-width',
testsuite: Sort gsk compare tests Easier to find things that way.
2021-04-01 21:03:54 +00:00
'inset-shadow-multiple',
rendernode: Bail if matrix is invalid Invalid matrices are okay in GSK (and GL), but not in Cairo. Testcase included.
2020-12-24 05:32:17 +00:00
'invalid-transform',
testsuite: Sort gsk compare tests Easier to find things that way.
2021-04-01 21:03:54 +00:00
'issue-3615',
testsuite: Add a forgotten test The test existed in git but wasn't hooked up. So let's do that by: 1. Adding it to the build 2. Adapting it a bit so rounding errors really don't trigger (as the original commit claimed they shouldn't). 3. Re-renaming it because this was actually about 3d gradients
2023-12-25 18:20:48 +00:00
'linear-gradient-3d-nocairo',
testsuite: Disable all failing tests on GL renderer Of all the recently added tests, disable the ones that fail on the GL renderer, so that CI passes.
2023-12-26 03:17:21 +00:00
'linear-gradient-nonorthogonal-scale-nogl',
gl: Interpolate gradient colors as premultiplied Tests included
2024-08-11 15:31:40 +00:00
'linear-gradient-premultiplied-nocairo',
testsuite: Add test for gradients Test that it can do 64 color stops. Should ensure that renderers either can do unlimited amounts or have fallbacks in place.
2023-05-17 21:16:34 +00:00
'linear-gradient-with-64-colorstops',
gpu: Allocate Vulkan descriptor pools dynamically Instead of allocating one large descriptor pool and hoping we never run out of descriptors, allocate small ones dynamically, so we know we never run out. Test incldued, though the test doesn't fail in CI, because llvmpipe doesn't care about pool size limits. It does fail on my AMD though. A fun side note about that test is that the GL renderer handles it best in normal operationbecause it caches offscreens per node and we draw the same node repeatedly. But, the replay test expands them to duplicated unique nodes, and then the GL renderer runs out of command queue length, so I had to disable the test on it.
2024-07-22 10:55:47 +00:00
'lots-of-offscreens-nogl',
Add a test for mask nodes
2023-02-12 03:20:24 +00:00
'mask',
testsuite: Add a test for mask out of bounds effects Inverted alpha masks have an effect on the source, even if the mask doesn't cover the source at all - or worse, is completely clipped out. The GL renderer handles this fine, but Cairo and Vulkan had optimizations that got this wrong.
2023-07-03 18:51:51 +00:00
'mask-clipped-inverted-alpha',
testsuite: Add tests for empty mask children The compare tests use an empty container node, but running them with --replay ends up with empty nodes in snapshots due to how containers are replayed. Related: !7396 Related: #6761
2024-07-01 18:24:23 +00:00
'mask-empty-mask',
'mask-empty-source',
gsk: Add a render test for mask modes
2023-02-15 01:26:17 +00:00
'mask-modes',
testsuite: Add compare tests for mask modes inside an opacity node
2023-12-23 22:53:04 +00:00
'mask-modes-in-opacity',
gsk: Fix luminance in Cairo and GL renderer In particular, fix the combination of luminance and alpha. We want to do mask = luminance * alpha and for inverted mask = (1.0 - luminance) * alpha so add a test that makes sure we do that and then fix the code and existing tests to conform to it.
2023-07-03 18:45:53 +00:00
'mask-modes-with-alpha',
testsuite/gsk: add render test for mask(texture|color)
2023-10-06 17:52:53 +00:00
'mask-texture-color-alpha',
testsuite: Add a test for a recent mipmap generation bug Tests the fix in ab1fba6fdcbf273604258061c1b7fad1ae7eef97. Related: #6298 Related: !6704
2024-01-04 00:35:23 +00:00
'mipmap-generation-later',
vulkan: Handle generating mipmaps for 1x1 images Testcase included.
2024-03-19 00:33:32 +00:00
'mipmap-with-1x1',
testsuite: Sort gsk compare tests Easier to find things that way.
2021-04-01 21:03:54 +00:00
'nested-rounded-clips',
gsk: Fix mis-scaled text rendering This was happening when rotated text was partially redrawn. A test that failed before this change is included. Fixes: #6504
2024-03-04 19:49:01 +00:00
'offscreen-forced-downscale',
gpu: When transforming to simpler transform, we might be all clipped When transforming back from a complex transform to a simpler transform, the resulting clip might turn out to clip everything, because clips can grow while transforming, but the scissor rect won't. So when this process happens, we can end up with an empty clip by transforming: 1. Set a clip that also sets the scissor 2. transform in a way that grows the clip, say rotate(45) 3. modify the clip to shrink it 4. transform in a way that simplifies the transform, say another rotate(45) 5. Figure out that this clip and the scissor rect do no longer overlap Catch this case and avoid drawing anything.
2024-08-10 00:33:45 +00:00
'offscreen-forced-downscale-all-clipped',
testsuite: Check that pixel grid math respects offsets
2024-01-09 22:27:07 +00:00
'offscreen-fractional-translate-nogl',
testsuite: Add a test for pixel alignment of offscreens The test ensures that offscreens render to the same pixel grid as the actual image, and they are not offset by fractions of a pixel. The Cairo renderer fails here because Cairo's clipping code rounds pixel values wrong.
2023-12-30 05:05:19 +00:00
'offscreen-pixel-alignment-nogl-nocairo',
testsuite: Add another test for pixel alignment Tests the rounding fixes from the previous commit. I'm not disabling it on GL because it succeeds - but that is somewhat by accident I guess.
2024-02-11 18:58:05 +00:00
'offscreen-pixel-alignment2',
Move working tests to new directory These are tests that are working on both GL and Cairo now. Some tests got black boxes over the areas that aren't easy to compare.
2019-03-19 07:16:07 +00:00
'opacity_clip',
testsuite: Add a test for opacity + color-matrix nodes These are 2x2 combinations that: 1. Use a texture child node vs a color child node This should force an offscreen vs straight up use a texture. 2. Switch opacity and color-matrix Either put the color matrix into the opacity node or put the opacity into the color matrix. This is worth testing because renderers often combine opacity into the color matrix to avoid offscreens. And they do that because applications often create faded out symbolic images, which end up as a combination of these nodes.
2023-12-01 11:13:30 +00:00
'opacity-colormatrix-combinations',
testuite: Add opacity-overdraw test Tests that overdrawing of content inside an opacity node happens before the opacity is applied. This is broken in the GL renderer and causes the opacity.ui reftest to fail.
2021-09-15 05:37:57 +00:00
'opacity-overdraw',
testsuite: Sort gsk compare tests Easier to find things that way.
2021-04-01 21:03:54 +00:00
'opacity-overlapping-children',
gpu: Draw proper shadows again The fix in commit 5e7f227d broke shadows while trying to make them faster. So use a better way to make them faster. With the normalized blur radius, we can now conclude that all the values too far from p.y will cause the gauss() call to return close to 0, so we can skip any y value that is too far from p.y. And that allows us to put an upper limit on the loop iterations. Tests included Fixes #6888
2024-07-28 18:10:56 +00:00
'outset-shadow-corner-blur',
'outset-shadow-corner-blur-huge-nocairo-nogl',
gpu: Fix shadows even more Math is hard. But this time, it comes with a test!
2024-07-30 15:24:17 +00:00
'outset-shadow-corner-blur-normal',
gpu: Don't blur tiny blur radii We get those wrong, and there's not really a visual effect. And since we do a check anyway, just disallow them and treat them as unblurred.
2024-07-29 23:44:05 +00:00
'outset-shadow-corner-blur-tiny',
Move working tests to new directory These are tests that are working on both GL and Cairo now. Some tests got black boxes over the areas that aren't easy to compare.
2019-03-19 07:16:07 +00:00
'outset_shadow_offset_both',
'outset_shadow_offset_x',
'outset_shadow_offset_y',
'outset_shadow_rounded_top',
testsuite: Add a compare test for previous commit Test that scaled border nodes properly scale their offsets. Related: #6412
2024-02-09 01:51:15 +00:00
'outset-shadow-scale-offset',
Move working tests to new directory These are tests that are working on both GL and Cairo now. Some tests got black boxes over the areas that aren't easy to compare.
2019-03-19 07:16:07 +00:00
'outset_shadow_simple',
Add a compare test for premultiplied colors This test checks a that a specific combination of mask with alpha inside opacity works as expected. We were treating the mask color as premultiplied here, although it isn't.
2024-08-06 04:30:04 +00:00
'premul-color-nogl',
gl: Interpolate gradient colors as premultiplied Tests included
2024-08-11 15:31:40 +00:00
'radial-gradient-premultiplied-nocairo',
testsuite: Add a radial gradient test All colors are idential so that the test doesn't fail due to rendering differences.
2023-12-27 03:28:04 +00:00
'radial-gradient-with-64-colorstops',
testsuite: Add a repeat node test case
2019-08-10 12:47:02 +00:00
'repeat',
rendernode: Fix Cairo rendering of repeating gradients Cairo and the GL renderer have a different idea of how to handle transitioning of colors outside the defined range. Consider these stops: black 50%, white 50% What color is at 0%? Cairo would transition between the last and first stop, ie it'd do a white-to-black transition and end up at rgb(0.5,0.5,0.5) at 0%. GL would behave as it would for non-repeating gradients and use black for the range [0%..50%] and white for [50%..100%]. The web would rescale the range so the first stop would be at 0% and the last stop would be at 100%, so this gradient would be illegal. Considering that it's possible for code to transition between the different behaviors by adding explicit stops at 0%/100%, I could choose any method. So I chose the simplest one, which is what the GL renderer does and which treats repeating and non-repeating gradients the same. Tests attached.
2023-09-07 14:02:09 +00:00
'repeating-linear-gradient-edge-colors',
'repeating-radial-gradient-edge-colors',
gtk: Fix gtk_snapshot_collect_repeat This creates a new color node that is meant to be identical to an existing one, so we need to use gsk_color_node_new2 to preserve the color state information. Test included.
2024-08-05 10:56:29 +00:00
'repeat-color',
testsuite: Add a repeat test for child bounds Test that if the child is a texture that extends the child bounds, that extension does not get repeated when rendering. This can easily happen when the child is not drawn as an offscreen, but instead the texture cache is consulted and no check for matching size is done.
2023-12-23 13:17:35 +00:00
'repeat-child-bounds',
vulkan: Handle empty child bounds in repeat node Also add test to the testsuite for it.
2023-05-09 22:08:24 +00:00
'repeat-empty-child-bounds',
testsuite: Add yet another repeat node test This one tests that when no offscreen is created for repeating but we drw everything individually, we still respect the clip set via child_bounds.
2023-12-23 19:44:50 +00:00
'repeat-huge-overdraw',
testsuite: Add another repeat node test case
2019-11-26 07:41:23 +00:00
'repeat-negative-coords',
testsuite: Add a repeat test for child bounds Test that if the child is a texture that extends the child bounds, that extension does not get repeated when rendering. This can easily happen when the child is not drawn as an offscreen, but instead the texture cache is consulted and no check for matching size is done.
2023-12-23 13:17:35 +00:00
'repeat-no-repeat',
testsuite: Add tests for the recent repeat node fixes Make sure to test horizontal and vertical versions, because who knows...
2024-01-23 04:40:30 +00:00
'repeat-node-tiling-horizontal',
'repeat-node-tiling-vertical',
testsuite: Add a compare test for non-integer repeat children This encodes the problems from the harmless looking example from https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/ in a form that we can test. Unsurprisingly it doesn't work on GL and Cairo.
2024-02-11 19:02:52 +00:00
'repeat-noninteger-nogl-nocairo',
testsuite: Add a repeat test Ensures that repeating actually causes repeating in the renderer by repeating a 1x1 image a lot.
2023-12-23 17:08:21 +00:00
'repeat-repeats',
testsuite: Disable all failing tests on GL renderer Of all the recently added tests, disable the ones that fail on the GL renderer, so that CI passes.
2023-12-26 03:17:21 +00:00
'repeat-repeats-nested-nogl',
testsuite: Add a test for repeat node offscreen scaling Ensure that the offscreens for repeat nodes pick the right xscale and yscale so that they render pixel-aligned.
2023-06-06 02:13:45 +00:00
'repeat-scaling',
testsuite: Sort gsk compare tests Easier to find things that way.
2021-04-01 21:03:54 +00:00
'repeat-texture',
gpu: Handle tiny offscreens Due to rounding errors, it is possible after intersecting a lot of rectangles to end up with a tiny size for an offscreen. And because we allow an epsilon before ceil()ing to an integer (see commit afc7b46264b for details) it is now possible that we end up with a size of 0. Avoid that by always enforcing a minimum size of 1px. Test included The test uses a different codepath to arrive at the same problem - it specifies the small size instead of triggering it via rounding errors and clipping like the original bug (and most likely the more common case to encounter this problem. Fixes #6656
2024-04-28 04:56:56 +00:00
'repeat-tiny-nogl-nocairo',
testsuite: Add a test for repeating gradients Make sure scaling the image also scales the color stop lookup.
2023-06-08 10:52:33 +00:00
'repeating-gradient-scaled',
gpu: Sort passes correctly In a very particular situation, it could happen that our renderpass reordering did not work out. Consider this nesting of renderpasses (indentation indicates subpasses): pass A subpass of A pass B subpass of B Out reordering code would reorder this as: subpass of B subpass of A pass A pass B Which doesn't sound too bad, the subpasses happen before the passes after all. However, a subpass might be a pass that converts the image for a texture stored in the texture cache and then updates the cached image. If "subpass of A" is such a pass *and* if "subpass of B" then renders with exactly this texture, then "subpass of B" will use the result of "subpass of A" as a source. The fix is to ensure that subpasses stay ordered, too. The new order moves subpasses right before their parent pass, so the order of the example now looks like: subpass of A pass A subpass of B pass B The place where this would happen most common was when drawing thumbnail images in Nautilus, the GTK filechooser or Fractal. Those images are usually PNG files, which are straight alpha. They are then drawn with a drop shadow, which requires an offscreen for drawing as well as those images as premultipled sources, so lots of subpasses happen. If there is then a redraw with a somewhat tricky subregion, then the slicing of the region code could end up generating 2 passes that each draw half of the thumbnail image - the first pass drawing the top half and the second pass drawing the bottom half. And due to the bug the bottom half would then be drawn from the offscreen before the actual contents of the offscreen would be drawn, leading to a corrupt bottom part of the image. Test included. Fixes: #6318
2024-03-16 22:30:22 +00:00
'reuse-of-texture-nested-in-offscreens',
testsuite: Add a testcase for extensive rounded clips The GL renderer can't handle this, so it's excluded.
2023-12-28 06:04:04 +00:00
'rounded-clip-with-huge-bounds-nogl',
testsuite: Add a test for large scale nodes This test fails if we naively create fullscale intermediate offscreens. This was fixed in the previous commits. This tests the fixes in 22ba6b1f33dcbcab8d (for cairo) and 3a0152b65fd75f631b76 (for GL).
2023-02-13 00:44:18 +00:00
'scale-textures-negative-ngl',
'scale-up-down',
'scaled-cairo',
Add a test for scaled textures
2023-02-11 18:43:05 +00:00
'scaled-texture',
testsuite: Add test for scaling texture-scale node Finally figured out a way to test that a texture-scale node using NEAREST that is upscaled using a transform node doesn't use NEAREST but LINEAR.
2023-10-29 19:45:22 +00:00
'scaled-texture-scale',
testsuite: Add a test for scaled texture clipping This tests that the result is suitably clipped for doing linear blending - the rightmost green pixel that is technically offscreen is blending into the red pixel and turning the test yellow. Cairo gets this wrong for some reason I didn't investigate.
2024-02-13 23:18:43 +00:00
'scaled-texture-scale-clip-nocairo',
gpu: Fix a crash in vulkan The node processing wasn't skipping 0-size nodes when using the uber shader, leading to assertions down the road. Since the ngl renderer doesn't use uber shaders, this only affects vulkan. Test included. Fixes: #6370
2024-01-27 15:30:38 +00:00
'scale0-crash',
glrenderer: Shadows without offset do exist Not for opaque contents, but stuff can be semi-transparent. Testcase included.
2023-09-07 21:02:37 +00:00
'shadow-behind',
gsk: Fix clipping error when drawing shadows When shadows were offset - in particular when offset so the original source was out of bounds of the result - the drawing code would create a pattern for it that didn't include enough of it to compose a shadow. Fix that by not creating those patterns anymore, but instead drawing the source (potentially multiple times) at the required offsets. While that does more drawing, it simplifies the shadow node draw code, and that's the primary goal of the Cairo rendering. Test included.
2023-09-18 05:48:10 +00:00
'shadow-clip-contents',
testsuite: Add a test for shadows with large offset This was causing crashes in the GPU renderer. Related: #6425
2024-02-13 12:11:43 +00:00
'shadow-huge-offset',
testsuite: Add a test for large scale nodes This test fails if we naively create fullscale intermediate offscreens. This was fixed in the previous commits. This tests the fixes in 22ba6b1f33dcbcab8d (for cairo) and 3a0152b65fd75f631b76 (for GL).
2023-02-13 00:44:18 +00:00
'shadow-in-opacity',
testsuite: Add a test for shadow offset clipping
2024-02-13 20:25:24 +00:00
'shadow-offset-clip',
testsuite: Add a shadow test This test tests that shadows that are offset to outside the clip region but where the blur goes back into the clip region get correctly drawn and not optimized away. To view what the test actually draws, remove at least the color-matrix - it's only used so the blurring algorithm doesn't cause different results - and maybe also the clip node.
2023-12-25 18:27:03 +00:00
'shadow-offset-to-outside-clip',
rendernode: Shadow nodes need offscreen for opacity Otherwise the shadow will not be properly computed as opaque regions become translucent after applying opacity. Testcase included.
2023-09-07 20:57:57 +00:00
'shadow-opacity',
snapshot: Fix wrong nodes with transformed shadows Test included. The test is disabled for Cairo because the Cairo blurring code can't deal with scaling, which makes things come out wrong for the test that checks that we do the right thing with the blur radius when scaling. Related: !6977
2024-03-06 19:46:06 +00:00
'shadow-replay-nocairo',
gl: Change rounded_rect_shrink() The code now follows gsk_rounded_rect_shrink() and with it the behavior of the Cairo renderer and Webkit. The old code did what the GL renderer and Cairo do, but I consider that wrong. I did not test Chrome. Test attached
2023-09-11 03:17:56 +00:00
'shrink-rounded-border',
Add compare tests for fill and stroke nodes
2023-08-07 11:09:42 +00:00
'stroke',
testsuite: Add clipped overly large paths ... to make sure that renderers clip any masks they generate for paths.
2023-12-29 06:13:49 +00:00
'stroke-clipped-nogl',
testsuite: Add tests for pixel grid accuracy See previous commit for details.
2024-01-09 16:16:05 +00:00
'stroke-fractional-translate-gradient-nogl',
'stroke-fractional-translate-nogl',
testsuite: Add stroke tests Same as the recent fill tests, just with strokes.
2023-12-27 21:29:36 +00:00
'stroke-opacity',
'stroke-with-3d-contents-nogl-nocairo',
testsuite: Add a test for subpixel positioning Draw a grid of 21x21 box glyphs. Each glyph is offset by n/20 pixels in the x and y direction. The background color is carefully selected to be divisible by 16, so that when the box glyph is subpixel positioned by 1/4th of a pixel offset from the pixel grid in either direction, the result will be an edge pixel whose color value can be computed exactly. Cairo still rounds this wrong for color values >= 128 which is why we use a dark gray that guarantees the resulting color values are all <128.
2024-01-22 11:02:28 +00:00
'subpixel-positioning',
testsuite: Disable test on cairo With the --repeat version of this test, Cairo needs to draw partially clipped glyphs. However, there's a bug in Cairo where it doesn't account for the subpixel positioning when clipping, so the glyphs get cut off at the edge. This is filed as https://gitlab.freedesktop.org/cairo/cairo/-/issues/821
2024-01-23 05:41:25 +00:00
'subpixel-positioning-hidpi-nogl-nocairo',
gsk: Add a testcase for underlines and carets The gl renderer has an optimization where it uses the glyph atlas to render color nodes that show up in the middle of text (e.g. for underlines and carets). This adds a simple test for that scenario, which hits this codepath.
2024-01-21 14:29:57 +00:00
'text-color-mix',
Add another font rendering test This one tests that we handle glyphs with lsb correctly wrt. to positioning.
2024-01-13 22:45:34 +00:00
'text-glyph-lsb',
gsk: Add a compare test for mixed color runs This tests the fixes in aa82190da659b5 and dcaa2c4ccb182c74cb40. The test uses a custom font named 'text-mixed-color' which contains six glyphs that are just boxes. Glyphs 1, 2, 3 are just plain glyphs, and glyphs 4, 5, 6 are color glyphs in red, green and blue. The glyphs are mapped to the characters A, B, C, D, E, F. The test is currently disabled for cairo, since it has some issues with transformed color glyphs.
2024-01-10 12:56:52 +00:00
'text-mixed-color-nocairo',
gsk: Add another font text This is similar to text-mixed-color, but it uses the COLRv1 table, to test our support for this font technology.
2024-01-10 23:09:08 +00:00
'text-mixed-color-colrv1',
testsuite: Add render test for texture placement Make sure that texture nodes sample from the texture properly.
2023-11-01 04:44:54 +00:00
'texture-coords',
gpu: Make sure textures used as image are mipmapped When getting a texture as image, we were always returning the texture unconditionally. However, we want to mipmap textures when the scale factor is too large, and this code path did not do that. The same codepath on the GL renderer doesn't do that either, so the test is disabled for it.
2024-07-07 05:19:43 +00:00
'texture-offscreen-mipmap-nogl',
testsuite: Unify renderer exclusion naming Instead of using "-3d" to exclude Cairo rendering, use "-no$renderer" to allow excluding any renderer. And because we use contains() for the check, we can exclude multiple renderers by naming the test sth like "test-nogl-nocairo.node"
2023-12-19 17:04:18 +00:00
'texture-scale-filters-nocairo',
testsuite: Add a test for large scale nodes This test fails if we naively create fullscale intermediate offscreens. This was fixed in the previous commits. This tests the fixes in 22ba6b1f33dcbcab8d (for cairo) and 3a0152b65fd75f631b76 (for GL).
2023-02-13 00:44:18 +00:00
'texture-scale-magnify-10000x',
tests: Add more tests for texture scale nodes
2023-03-13 17:20:02 +00:00
'texture-scale-magnify-rotate',
gpu: ceil() offscreen size before generating offscreen The goal is to generate an offscreen at 1x scale. When not ceil()ing the numbers the offscreen code would do it *and* adjust the scale accordingly, so we'd end up with something like a 1.01x scale. And that would cause the code to reenter this codepath with the goal to generate an offscreen at 1x scale. And indeed, this would lead to infinite recursion. Tests included. Fixes #6553
2024-03-22 15:18:41 +00:00
'texture-scale-nearest-noninteger-scaled-nogl',
testsuite: Add a test for nearest vs linear scales
2023-10-29 18:02:09 +00:00
'texture-scale-nearest-vs-linear',
gsk: Fix texture-scale node Cairo drawing The code was interpreting x/y coordinates wrong sometimes and causing things to not be drawn at the correct offset. Testcase included.
2023-10-27 18:45:12 +00:00
'texture-scale-offset',
testsuite: Add a test for stripes The GL renderer was creating sripes for nodes that were scaled in particular ways, probably due to rounding errors. This testsuite focuses on one of those stripes to make sure they are gone.
2023-03-04 01:50:38 +00:00
'texture-scale-stripes',
testsuite: Add a test for large scale nodes This test fails if we naively create fullscale intermediate offscreens. This was fixed in the previous commits. This tests the fixes in 22ba6b1f33dcbcab8d (for cairo) and 3a0152b65fd75f631b76 (for GL).
2023-02-13 00:44:18 +00:00
'texture-url',
testsuite: Disable all failing tests on GL renderer Of all the recently added tests, disable the ones that fail on the GL renderer, so that CI passes.
2023-12-26 03:17:21 +00:00
'transform-huge-child-nogl',
'transform-huge-child-3d-nocairo-nogl',
testsuite: Add a test for large scale nodes This test fails if we naively create fullscale intermediate offscreens. This was fixed in the previous commits. This tests the fixes in 22ba6b1f33dcbcab8d (for cairo) and 3a0152b65fd75f631b76 (for GL).
2023-02-13 00:44:18 +00:00
'transform-in-transform',
'transform-in-transform-in-transform',
testsuite: Unify renderer exclusion naming Instead of using "-3d" to exclude Cairo rendering, use "-no$renderer" to allow excluding any renderer. And because we use contains() for the check, we can exclude multiple renderers by naming the test sth like "test-nogl-nocairo.node"
2023-12-19 17:04:18 +00:00
'z-transform-clipping-bounds-nocairo',
gsk: Move text-related test out of ci These are too sensitive to rendering differences between renderers to run reliably in ci, but we still want to keep them around. In particular, the big glyph tests are useful to exercise the GL glyph cache.
2019-07-28 13:35:37 +00:00
]
# these are too sensitive to differences in the renderers
# to run in ci, but still useful to keep around
informative_render_tests = [
'big-glyph',
'empty-text',
'huge-glyph',
testsuite: Unify renderer exclusion naming Instead of using "-3d" to exclude Cairo rendering, use "-no$renderer" to allow excluding any renderer. And because we use contains() for the check, we can exclude multiple renderers by naming the test sth like "test-nogl-nocairo.node"
2023-12-19 17:04:18 +00:00
'rounded-clip-in-clip-nocairo', # both cairo and gl fail this one
gsk: Fix handling of hex boxes The pango code that is drawing hex boxes, invisible glyphs, etc, is depending on the width being set in the PangoGlyphInfo. Once we set that, everything falls into place. Testcase included.
2024-03-01 19:38:50 +00:00
'text-missing-glyph', # https://gitlab.gnome.org/GNOME/pango/-/merge_requests/718
Move working tests to new directory These are tests that are working on both GL and Cairo now. Some tests got black boxes over the areas that aren't easy to compare.
2019-03-19 07:16:07 +00:00
]
renderers = [
build: Add known to be failing gsk comparison tests The unaligned-offscreen and upside-down-label-3d tests are failing after upgrading our CI images, seemingly because of some font rendering issue that is hard to track. Let's use the "failing" testsuite mechanism that we also use for the reftests.
2022-12-14 17:31:50 +00:00
{ 'name': 'gl' },
testsuite: Unify renderer exclusion naming Instead of using "-3d" to exclude Cairo rendering, use "-no$renderer" to allow excluding any renderer. And because we use contains() for the check, we can exclude multiple renderers by naming the test sth like "test-nogl-nocairo.node"
2023-12-19 17:04:18 +00:00
{ 'name': 'broadway' },
{ 'name': 'cairo' },
testsuite: Add NGL and Vulkan renderer to compare tests Add a testsuite called gsk-compare-vulkan to run the gsk renderer tests with the Vulkan renderer and gsk-compare-ngl to run them with the NGL renderer. To run the tests locally, you can do: meson test -C_build --suite gsk-compare-vulkan
2023-05-07 11:41:03 +00:00
{ 'name': 'ngl' },
{ 'name': 'vulkan' },
build: Add known to be failing gsk comparison tests The unaligned-offscreen and upside-down-label-3d tests are failing after upgrading our CI images, seemingly because of some font rendering issue that is hard to track. Let's use the "failing" testsuite mechanism that we also use for the reftests.
2022-12-14 17:31:50 +00:00
]
Skip some tests with small textures When textures are too large, we will scale them down to fit the max texture size, which will cause comparisons to fail.
2023-05-01 20:00:24 +00:00
compare_xfails_small_texture = [
'big-checkerboard',
Skip another failing gsk test with small textures
2023-05-04 19:36:57 +00:00
'big-checkerboard-scaled-down',
testsuite: Disable all failing tests on GL renderer Of all the recently added tests, disable the ones that fail on the GL renderer, so that CI passes.
2023-12-26 03:17:21 +00:00
'big-checkerboard-scaled-down2',
'repeat-repeats', # only fails when rotated
Add a glyph scaling test The glyph in this test has extents that will be made smaller by hinting, which poses some challenge for our renderers. The scaled glyph rendering is too big for the 'small texture' text setup, so we allow the test to fail there.
2024-02-29 01:57:44 +00:00
'glyph-scaling',
Skip some tests with small textures When textures are too large, we will scale them down to fit the max texture size, which will cause comparisons to fail.
2023-05-01 20:00:24 +00:00
]
build: Compactify compare test setup Make a loop over the variants we have, rather than duplicating so much code.
2024-02-11 14:27:24 +00:00
variants = {
'plain': '--plain',
'flipped': '--flip',
'rotated': '--rotate',
'repeated': '--repeat',
'masked': '--mask',
'replayed': '--replay',
'clipped': '--clip',
Add tests for uber rendering Add a --colorflip option to the compare-render test. This applies a color matrix to the node, which has the intended side-effect of convincing the Vulkan renderer to use its uber shader, so we get test results comparing the uber output to its non-uber siblings.
2024-03-09 00:34:19 +00:00
'colorflipped': '--colorflip',
build: Compactify compare test setup Make a loop over the variants we have, rather than duplicating so much code.
2024-02-11 14:27:24 +00:00
}
ci: Add xfails for some known issues Add xfails for failing compare tests where we have known issues, and annotate them.
2024-02-11 14:38:12 +00:00
compare_xfails = {
ci: Add another xfail This is reported in https://gitlab.gnome.org/GNOME/gtk/-/issues/6450
2024-02-16 16:13:57 +00:00
'ngl': {
ci: Add more xfails The gradient tests are prone to rounding errors when clipped, so fail them.
2024-03-10 20:53:12 +00:00
# the gradients are prone to rounding errors which become
# more pronounced in small clips, it seems
Exclude some more gradient compare tests These are prone to rounding errors.
2024-06-18 02:28:33 +00:00
'radial-gradient-with-64-colorstops': ['plain','flipped','rotated','repeated','masked','replayed','clipped','colorflipped'],
'conic-gradient-with-64-colorstops': ['plain','flipped','rotated','repeated','masked','replayed','clipped','colorflipped'],
Add glyph antialiasing test This test checks that the antialias font option has the indended effect.
2024-02-29 17:39:17 +00:00
'blur-child-bounds-oversize-nogl': ['clipped'], # 6450
Add an xfail for a rounded-clip test This needs some changes in how we prevent offscreens from getting too big. Filed as #6532.
2024-03-11 21:01:35 +00:00
'rounded-clip-with-huge-bounds-nogl': ['plain','flipped','rotated','repeated','masked','replayed','clipped','colorflipped'], # 6532
Add another xfail for clipped compare tests These just keep happening.
2024-03-17 12:59:45 +00:00
'big-checkerboard': ['clipped'], # 6444
Add glyph antialiasing test This test checks that the antialias font option has the indended effect.
2024-02-29 17:39:17 +00:00
},
gpu: Add an epsilon before ceil()ing for offscreen size Avoids getting the scale wrong when due to a rounding error our pixel-aligned rectangle is 5.000000003px big and we ceil() to 6px and produce blurry output. Fixes #6439
2024-02-14 03:47:18 +00:00
'vulkan': {
ci: Add more xfails The gradient tests are prone to rounding errors when clipped, so fail them.
2024-03-10 20:53:12 +00:00
'radial-gradient-with-64-colorstops': ['clipped', 'colorflipped'],
'conic-gradient-with-64-colorstops': ['clipped', 'colorflipped'],
ci: Update xfails A number of the xfails that were added for the new renderers have been fixed.
2024-03-07 00:03:43 +00:00
'blur-child-bounds-oversize-nogl': ['clipped'], # 6450
Add an xfail This is causing sporadic ci failures, so file an issue and xfail it.
2024-03-09 01:01:41 +00:00
'repeat-repeats-nested-nogl': ['clipped'], # 6522
Add tests for uber rendering Add a --colorflip option to the compare-render test. This applies a color matrix to the node, which has the intended side-effect of convincing the Vulkan renderer to use its uber shader, so we get test results comparing the uber output to its non-uber siblings.
2024-03-09 00:34:19 +00:00
'repeating-radial-gradient-edge-colors': ['colorflipped'],
Add an xfail for a rounded-clip test This needs some changes in how we prevent offscreens from getting too big. Filed as #6532.
2024-03-11 21:01:35 +00:00
'rounded-clip-with-huge-bounds-nogl': ['plain','flipped','rotated','repeated','masked','replayed','clipped','colorflipped'], # 6532
Add another xfail for clipped compare tests These just keep happening.
2024-03-17 12:59:45 +00:00
'big-checkerboard': ['clipped'], # 6444
ci: Add xfails for gl rotation+opacity problems These are the topic of #6525. Lets xfail them for now.
2024-03-09 18:02:56 +00:00
},
'gl': {
# 6525
'container-single-child-offscreen-for-opacity': ['rotated'],
'cross-fade-in-opacity': ['rotated'],
'mask-modes-in-opacity': ['rotated'],
'opacity-overlapping-children': ['rotated'],
'scaled-texture-scale': ['rotated'],
'shadow-opacity': ['rotated'],
'texture-scale-nearest-vs-linear': ['rotated'],
},
ci: Add xfails for some known issues Add xfails for failing compare tests where we have known issues, and annotate them.
2024-02-11 14:38:12 +00:00
}
Move working tests to new directory These are tests that are working on both GL and Cairo now. Some tests got black boxes over the areas that aren't easy to compare.
2019-03-19 07:16:07 +00:00
foreach renderer : renderers
build: Compactify compare test setup Make a loop over the variants we have, rather than duplicating so much code.
2024-02-11 14:27:24 +00:00
renderer_name = renderer.get('name')
ci: Add xfails for some known issues Add xfails for failing compare tests where we have known issues, and annotate them.
2024-02-11 14:38:12 +00:00
renderer_xfails = compare_xfails.get(renderer_name, { })
build: Add known to be failing gsk comparison tests The unaligned-offscreen and upside-down-label-3d tests are failing after upgrading our CI images, seemingly because of some font rendering issue that is hard to track. Let's use the "failing" testsuite mechanism that we also use for the reftests.
2022-12-14 17:31:50 +00:00
build: Compactify compare test setup Make a loop over the variants we have, rather than duplicating so much code.
2024-02-11 14:27:24 +00:00
foreach testname : compare_render_tests
ci: Add xfails for some known issues Add xfails for failing compare tests where we have known issues, and annotate them.
2024-02-11 14:38:12 +00:00
test_xfails = renderer_xfails.get(testname, [])
testsuite: Unify renderer exclusion naming Instead of using "-3d" to exclude Cairo rendering, use "-no$renderer" to allow excluding any renderer. And because we use contains() for the check, we can exclude multiple renderers by naming the test sth like "test-nogl-nocairo.node"
2023-12-19 17:04:18 +00:00
exclude_term = '-no' + renderer_name
build: Add known to be failing gsk comparison tests The unaligned-offscreen and upside-down-label-3d tests are failing after upgrading our CI images, seemingly because of some font rendering issue that is hard to track. Let's use the "failing" testsuite mechanism that we also use for the reftests.
2022-12-14 17:31:50 +00:00
suites = [
'gsk',
'gsk-compare',
'gsk-' + renderer_name,
'gsk-compare-' + renderer_name,
]
Skip some tests with small textures When textures are too large, we will scale them down to fit the max texture size, which will cause comparisons to fail.
2023-05-01 20:00:24 +00:00
if compare_xfails_small_texture.contains(testname)
ci: Reshuffle test setups Add a wayland_gl setup that explicitly uses desktop GL, and rename wayland_gles to wayland_gles2 (since that is what it does). In ci, make the fedora-x86_64 runner run tests with wayland_gl and wayland_gles2, and make the fedora-release runner run test with wayland and x11.
2023-11-18 14:30:56 +00:00
suites += 'wayland_gles2_failing'
Skip some tests with small textures When textures are too large, we will scale them down to fit the max texture size, which will cause comparisons to fail.
2023-05-01 20:00:24 +00:00
endif
testsuite: Add render node replay tests This takes a render node tree and "replays" it by using the GtkSnapshot machinery. We don't necesserily expect to get back an exactly equal render node tree back, since GtkSnapshot applies various small optimizations where possible, but the original and the replayed nodes should render to identical textures. Signed-off-by: Sergey Bugaev <bugaevc@gmail.com>
2023-08-16 15:46:20 +00:00
test_env = [
'GSK_RENDERER=' + renderer_name,
'GTK_A11Y=test',
'G_TEST_SRCDIR=@0@'.format(meson.current_source_dir()),
gsk: Allow custom fonts in tests The commit adds a custom fontconfig configuration in testsuite/gsk/fonts/fonts.conf and sets the FONTCONFIG_FILE environment variable for the gsk compare tests to point at it. To use a custom font in tests, just drop it into the testsuite/gsk/fonts/ directory. The font configuration includes the system configuration, so existing tests should not be affected.
2024-01-10 12:56:11 +00:00
'G_TEST_BUILDDIR=@0@'.format(meson.current_build_dir()),
tests: Change the way custom fonts are handled Instead of setting FONTCONFIG_FILE to a custom font configuration, pass the directory containing the fonts as TEST_FONTS and use FcConfigAppFontAddDir to add them to the default font configuration.
2024-01-11 03:15:14 +00:00
'TEST_FONT_DIR=@0@/fonts'.format(meson.current_source_dir())
testsuite: Add render node replay tests This takes a render node tree and "replays" it by using the GtkSnapshot machinery. We don't necesserily expect to get back an exactly equal render node tree back, since GtkSnapshot applies various small optimizations where possible, but the original and the replayed nodes should render to identical textures. Signed-off-by: Sergey Bugaev <bugaevc@gmail.com>
2023-08-16 15:46:20 +00:00
]
testsuite: Unify renderer exclusion naming Instead of using "-3d" to exclude Cairo rendering, use "-no$renderer" to allow excluding any renderer. And because we use contains() for the check, we can exclude multiple renderers by naming the test sth like "test-nogl-nocairo.node"
2023-12-19 17:04:18 +00:00
if ((not testname.contains(exclude_term)) and
testsuite: Add NGL and Vulkan renderer to compare tests Add a testsuite called gsk-compare-vulkan to run the gsk renderer tests with the Vulkan renderer and gsk-compare-ngl to run them with the NGL renderer. To run the tests locally, you can do: meson test -C_build --suite gsk-compare-vulkan
2023-05-07 11:41:03 +00:00
(renderer_name != 'broadway' or broadway_enabled) and
(renderer_name != 'vulkan' or have_vulkan))
build: Compactify compare test setup Make a loop over the variants we have, rather than duplicating so much code.
2024-02-11 14:27:24 +00:00
foreach variant : variants.keys()
ci: Add xfails for some known issues Add xfails for failing compare tests where we have known issues, and annotate them.
2024-02-11 14:38:12 +00:00
extra_suites = [ 'gsk-compare-' + variant + '-' + renderer_name ]
testsuite: Give up on cairo for clipping tests Cairo has a number of problems with clipping, such as https://gitlab.freedesktop.org/cairo/cairo/-/issues/821 https://gitlab.gnome.org/GNOME/gtk/-/issues/6426 https://gitlab.gnome.org/GNOME/gtk/-/issues/6427 These require cairo fixes that are hard to come by, given the maintainership situation. And since these the clipping tests are randomized, such failures will pop up randomly, making it very frustrating to deal with ci. So lets focus these tests on the places where it is easier to get fixes, and run the clipping tests only for the other renderers.
2024-02-11 16:57:55 +00:00
if test_xfails.contains(variant) or (renderer_name == 'cairo' and variant == 'clipped')
ci: Add xfails for some known issues Add xfails for failing compare tests where we have known issues, and annotate them.
2024-02-11 14:38:12 +00:00
extra_suites += ['failing']
endif
build: Compactify compare test setup Make a loop over the variants we have, rather than duplicating so much code.
2024-02-11 14:27:24 +00:00
test('compare ' + renderer_name + ' ' + testname + ' ' + variant, compare_render,
args: [
variants.get(variant),
'--output', join_paths(meson.current_build_dir(), 'compare', renderer_name),
join_paths(meson.current_source_dir(), 'compare', testname + '.node'),
join_paths(meson.current_source_dir(), 'compare', testname + '.png'),
],
env: test_env,
ci: Add xfails for some known issues Add xfails for failing compare tests where we have known issues, and annotate them.
2024-02-11 14:38:12 +00:00
suite: suites + extra_suites
build: Compactify compare test setup Make a loop over the variants we have, rather than duplicating so much code.
2024-02-11 14:27:24 +00:00
)
endforeach
testsuite: Add a broken test This also adds some build magic so all tests that contain "-3d" in them won't be added to the Cairo renderer. Of course, this new test is such a test.
2019-03-21 05:47:36 +00:00
endif
Move working tests to new directory These are tests that are working on both GL and Cairo now. Some tests got black boxes over the areas that aren't easy to compare.
2019-03-19 07:16:07 +00:00
endforeach
endforeach
testsuite: Add tests for the new node parsing code This adds a test tool gsk/node-parser that takes node files and parses them. A few of these node files have been added, for crashes I encountered while developing the new parsing code.
2019-03-19 04:29:20 +00:00
node_parser_tests = [
nodeparser: Add support for cicp color states Allow defining cicp color states with an @-rule: @cicp "jpeg" { primaries: 1; transfer: 13; matrix: 6; range: full; } And allow using them in color() like this: color("jpeg" 50% 0.5 1 / 75%) Note that custom color states use a string, unlike default color states which use an ident. Test included.
2024-08-04 22:16:44 +00:00
'at-rule.node',
testsuite: Remove serialize-deserialize test The serialize-deserialize test is completely handled via the new nodeparser tests. So move those tests over and delete the old test binary.
2019-05-20 01:38:45 +00:00
'blend.node',
testsuite: Add tests for the unknown enums See commit 40e7a265a7ccb1385a3af0931c591201b0ce063a
2023-02-13 07:39:54 +00:00
'blend-unknown-mode.errors',
'blend-unknown-mode.node',
'blend-unknown-mode.ref.node',
testsuite: Remove serialize-deserialize test The serialize-deserialize test is completely handled via the new nodeparser tests. So move those tests over and delete the old test binary.
2019-05-20 01:38:45 +00:00
'border.node',
nodeparser: Support color states for box shadows Just switch from parse_color to parse_color2, and apply the corresponding changes to serialization too. Test included.
2024-08-02 13:46:21 +00:00
'box-shadow.node',
testsuite: Remove serialize-deserialize test The serialize-deserialize test is completely handled via the new nodeparser tests. So move those tests over and delete the old test binary.
2019-05-20 01:38:45 +00:00
'color.node',
nodeparser: Add support for cicp color states Allow defining cicp color states with an @-rule: @cicp "jpeg" { primaries: 1; transfer: 13; matrix: 6; range: full; } And allow using them in color() like this: color("jpeg" 50% 0.5 1 / 75%) Note that custom color states use a string, unlike default color states which use an ident. Test included.
2024-08-04 22:16:44 +00:00
'color2.node',
'color3.node',
nodeparser: Rewrite the color parsing Use gtk_css_parser_consume_function, for better error handling. We are now getting the expected error for color(srgb 1 2 3 4 5 6) Test included.
2024-08-06 04:23:07 +00:00
'color4.node',
gsk: Improve test coverage
2022-07-15 13:42:45 +00:00
'conic-gradient.node',
'conic-gradient.ref.node',
testsuite: Redo node-parser Base the rewrite on testsuite/css/parser/test-css-parser - we now require the node file to match a reference node and track the errors it triggers. We also no longer use gtester.
2019-05-14 01:20:09 +00:00
'crash1.errors',
'crash1.node',
'crash1.ref.node',
'crash2.errors',
'crash2.node',
'crash2.ref.node',
'crash3.node',
'crash3.ref.node',
'crash4.errors',
'crash4.node',
'crash4.ref.node',
testsuite: Remove serialize-deserialize test The serialize-deserialize test is completely handled via the new nodeparser tests. So move those tests over and delete the old test binary.
2019-05-20 01:38:45 +00:00
'debug.node',
gsk: Improve test coverage
2022-07-15 13:42:45 +00:00
'debug-fail.node',
'debug-fail.ref.node',
'debug-fail.errors',
testsuite: Add empty node tests For every node type, add a test that creates it empty and ensure that it prints the reference output.
2019-05-19 19:34:13 +00:00
'empty-blend.node',
'empty-blend.ref.node',
'empty-blur.node',
'empty-blur.ref.node',
'empty-border.node',
'empty-border.ref.node',
rendernodeparser: Parse Cairo nodes We also print the script, but we don't parse it yet.
2019-05-25 22:50:13 +00:00
'empty-cairo.node',
'empty-cairo.ref.node',
testsuite: Add empty node tests For every node type, add a test that creates it empty and ensure that it prints the reference output.
2019-05-19 19:34:13 +00:00
'empty-clip.node',
'empty-clip.ref.node',
'empty-color.node',
'empty-color.ref.node',
'empty-color-matrix.node',
'empty-color-matrix.ref.node',
'empty-container.node',
'empty-container.ref.node',
'empty-cross-fade.node',
'empty-cross-fade.ref.node',
'empty-debug.node',
'empty-debug.ref.node',
Add nodeparser tests for fill and stroke nodes
2023-08-07 04:03:17 +00:00
'empty-fill.node',
'empty-fill.ref.node',
testsuite: Add empty node tests For every node type, add a test that creates it empty and ensure that it prints the reference output.
2019-05-19 19:34:13 +00:00
'empty-inset-shadow.node',
'empty-inset-shadow.ref.node',
'empty-linear-gradient.node',
'empty-linear-gradient.ref.node',
Add more mask node tests
2023-02-15 00:04:34 +00:00
'empty-mask.node',
'empty-mask.ref.node',
testsuite: Add empty node tests For every node type, add a test that creates it empty and ensure that it prints the reference output.
2019-05-19 19:34:13 +00:00
'empty-opacity.node',
'empty-opacity.ref.node',
'empty-outset-shadow.node',
'empty-outset-shadow.ref.node',
'empty-repeat.node',
'empty-repeat.ref.node',
'empty-rounded-clip.node',
'empty-rounded-clip.ref.node',
'empty-shadow.node',
'empty-shadow.ref.node',
Add nodeparser tests for fill and stroke nodes
2023-08-07 04:03:17 +00:00
'empty-stroke.node',
'empty-stroke.ref.node',
nodeparser: Print subsurface nodes properly The nodes actually end. Tests included.
2024-03-11 00:12:28 +00:00
'empty-subsurface.node',
'empty-subsurface.ref.node',
testsuite: Add empty node tests For every node type, add a test that creates it empty and ensure that it prints the reference output.
2019-05-19 19:34:13 +00:00
'empty-text.node',
'empty-text.ref.node',
'empty-texture.node',
'empty-texture.ref.node',
testsuite: Add empty test for new node
2023-02-13 06:59:15 +00:00
'empty-texture-scale.node',
'empty-texture-scale.ref.node',
testsuite: Add empty node tests For every node type, add a test that creates it empty and ensure that it prints the reference output.
2019-05-19 19:34:13 +00:00
'empty-transform.node',
'empty-transform.ref.node',
Add nodeparser tests for fill and stroke nodes
2023-08-07 04:03:17 +00:00
'fill.node',
'fill.ref.node',
Add more fill and stroke node tests
2023-08-26 03:10:04 +00:00
'fill2.node',
'fill2.ref.node',
gsk: Improve test coverage
2022-07-15 13:42:45 +00:00
'glshader.node',
'glshader.ref.node',
'glshader.errors',
'gradient-fail.node',
'gradient-fail.ref.node',
'gradient-fail.errors',
gsk: Add a node parser test for mask modes
2023-02-15 01:28:02 +00:00
'mask-modes.node',
'mask-modes.ref.node',
testsuite: Add parsing tests for node and texture naming
2023-03-28 22:12:59 +00:00
'node-names.node',
'node-names-everywhere.errors',
'node-names-everywhere.node',
'node-names-everywhere.ref.node',
gpu: Fix wrong rect check in occlusion fallback path We need to check that the clip is inside the opaque region, not that the opaque region is inside the clip. Test included, using the only not that hits the fallback path with an opaque region smaller than its bounds.
2024-07-08 20:22:49 +00:00
'occlusion-wrong-rect-contains',
gsk: Improve test coverage
2022-07-15 13:42:45 +00:00
'radial-gradient.node',
'radial-gradient.ref.node',
nodeparser: Handle disallowed values for radial gradients Make sure the radii are strictly positive. Also handle the case where start >= end. We can't really underline that error, because we don't track the locations of the start/end properties until we know that there's an error. So just underline the whole radial gradient declaration. Test included
2024-08-11 15:44:19 +00:00
'radial-gradient-start-end.errors',
'radial-gradient-start-end.node',
'radial-gradient-start-end.ref.node',
gsk: Improve test coverage
2022-07-15 13:42:45 +00:00
'repeating-linear-gradient.node',
'repeating-linear-gradient.ref.node',
'repeating-radial-gradient.node',
'repeating-radial-gradient.ref.node',
testsuite: Remove serialize-deserialize test The serialize-deserialize test is completely handled via the new nodeparser tests. So move those tests over and delete the old test binary.
2019-05-20 01:38:45 +00:00
'rounded-rect.node',
'shadow.node',
gsk: Improve test coverage
2022-07-15 13:42:45 +00:00
'shadow-fail.node',
'shadow-fail.ref.node',
'shadow-fail.errors',
rendernodeparser: Failing to parse a string is an error Testcase included.
2023-03-28 19:09:01 +00:00
'string-error.errors',
'string-error.node',
'string-error.ref.node',
Add nodeparser tests for fill and stroke nodes
2023-08-07 04:03:17 +00:00
'stroke.node',
'stroke.ref.node',
testsuite: Remove serialize-deserialize test The serialize-deserialize test is completely handled via the new nodeparser tests. So move those tests over and delete the old test binary.
2019-05-20 01:38:45 +00:00
'testswitch.node',
testsuite: Add a forgotten test
2024-03-01 14:20:14 +00:00
'text.node',
rendernode: Fix handling of color glyphs The rendernode parser was mixing up its flags. Test included. Related: #6075
2023-09-13 17:33:07 +00:00
'text-color.node',
gsk: Improve test coverage
2022-07-15 13:42:45 +00:00
'text-fail.node',
'text-fail.ref.node',
'text-fail.errors',
Add a test for new text node syntax Add a test that checks that font: properties can be parsed without error, both with and without the optional url.
2024-01-15 04:17:58 +00:00
'text-font-blob.node',
'text-font-blob.ref.node',
Add a test for font-related node parser errors This tests the behaviors implemented in the previous commit.
2024-01-15 16:38:49 +00:00
'text-font-errors.node',
'text-font-errors.ref.node',
'text-font-errors.errors',
gsk: Accept font options in node files The goal is to fix all the context that influences the rendering of text nodes in the node file. This will help with better font testing. The newly accepted properties are hint-style: none/slight/full antialias: none/gray We are omitting font options and values that aren't supported in GSK or have no influence on the rendering. Note that these settings will get incorporated in the PangoFont that gets set on the resulting text node. Parser tests included.
2024-01-29 02:36:47 +00:00
'text-font-options.node',
'text-font-options.ref.node',
'text-font-options-error.node',
'text-font-options-error.ref.node',
'text-font-options-error.ref.errors',
testsuite: Add another test his is the opposite of the test in 1502c21e9767dd6a1888937cd284fa3f7d66b376. Also change the numbers in that test so it doesn't need a ref file. Related: #6075
2023-09-13 17:29:27 +00:00
'text-no-color.node',
gsk: Improve test coverage
2022-07-15 13:42:45 +00:00
'texture-fail.node',
'texture-fail.ref.node',
Add a test for font-related node parser errors This tests the behaviors implemented in the previous commit.
2024-01-15 16:38:49 +00:00
'texture-fail.errors',
testsuite: Add parsing tests for node and texture naming
2023-03-28 22:12:59 +00:00
'texture-names.node',
tests: Add more tests for texture scale nodes
2023-03-13 17:20:02 +00:00
'texture-scale-filters.node',
'texture-scale-filters.ref.node',
testsuite: Add tests for the unknown enums See commit 40e7a265a7ccb1385a3af0931c591201b0ce063a
2023-02-13 07:39:54 +00:00
'texture-scale-unknown-filter.errors',
'texture-scale-unknown-filter.node',
'texture-scale-unknown-filter.ref.node',
gsk: Improve test coverage
2022-07-15 13:42:45 +00:00
'transform-fail.node',
'transform-fail.ref.node',
'transform-fail.errors',
gsk: Temporarily disable a test This test fails on my system currently, since rawhide libpng appears to have changed the encoding of pngs so that the texture nodes no longer match the reference. This will be a problem as long as our ci systems have an older libpng, so disable this test for now.
2023-12-28 16:21:30 +00:00
# this fails in f40 since libpng changes the pngs while reencoding
#'widgetfactory.node',
testsuite: Add tests for the new node parsing code This adds a test tool gsk/node-parser that takes node files and parses them. A few of these node files have been added, for crashes I encountered while developing the new parsing code.
2019-03-19 04:29:20 +00:00
]
foreach test : node_parser_tests
testsuite: Redo node-parser Base the rewrite on testsuite/css/parser/test-css-parser - we now require the node file to match a reference node and track the errors it triggers. We also no longer use gtester.
2019-05-14 01:20:09 +00:00
if test.endswith('.node') and not test.endswith('.ref.node')
test('parser ' + test, node_parser,
build: Use a consistent style for Meson files
2020-12-15 12:31:38 +00:00
args: [
join_paths(meson.current_source_dir(), 'nodeparser', test)
],
env: [
'GSK_RENDERER=opengl',
'GTK_A11Y=test',
'G_TEST_SRCDIR=@0@'.format(meson.current_source_dir()),
Isolate our nodeparser tests better Add a custom fontconfig setup and ship Cantarell as part of it. This should hopefully make it so that the tests always see the same default font, as long as you have FONTCONFIG_FILE set up correctly. Update all affected tests.
2024-06-18 14:36:33 +00:00
'G_TEST_BUILDDIR=@0@'.format(meson.current_build_dir()),
'FONTCONFIG_FILE=@0@/fonts/fonts.conf'.format(meson.current_source_dir()),
build: Use a consistent style for Meson files
2020-12-15 12:31:38 +00:00
],
testsuite: Add offload tests These tests come in two variants. The first takes .node and .offload file, parses the node file, and compares the resulting subsurface attachments to expected results. The second variant takes two .node/.offload file pairs and a .diff file, parses the node files, compares the resulting subsurface attachments, and then diffs the nodes, comparing the resulting area to the region in the .diff file.
2023-11-10 20:34:30 +00:00
protocol: 'exitcode',
Add a testsuite for nodeparser tests This helps when changing the node parser.
2024-02-27 01:49:21 +00:00
suite: [ 'gsk', 'gsk-nodeparser' ]
build: Use a consistent style for Meson files
2020-12-15 12:31:38 +00:00
)
testsuite: Redo node-parser Base the rewrite on testsuite/css/parser/test-css-parser - we now require the node file to match a reference node and track the errors it triggers. We also no longer use gtester.
2019-05-14 01:20:09 +00:00
endif
testsuite: Add tests for the new node parsing code This adds a test tool gsk/node-parser that takes node files and parses them. A few of these node files have been added, for crashes I encountered while developing the new parsing code.
2019-03-19 04:29:20 +00:00
endforeach
Move transform tests to the gsk suite That is where they belong.
2019-06-03 16:10:09 +00:00
testsuite: Add offload tests These tests come in two variants. The first takes .node and .offload file, parses the node file, and compares the resulting subsurface attachments to expected results. The second variant takes two .node/.offload file pairs and a .diff file, parses the node files, compares the resulting subsurface attachments, and then diffs the nodes, comparing the resulting area to the region in the .diff file.
2023-11-10 20:34:30 +00:00
# offload does not work outside of linux
if os_linux
offload = executable('offload', 'offload.c', 'gskrendernodeattach.c',
dependencies : libgtk_static_dep,
testsuite: build fix The statically linked tests need to have -DGTK_COMPILATION=1 in their cflags.
2024-08-12 23:17:56 +00:00
c_args: common_cflags + [ '-DGTK_COMPILATION=1' ],
testsuite: Add offload tests These tests come in two variants. The first takes .node and .offload file, parses the node file, and compares the resulting subsurface attachments to expected results. The second variant takes two .node/.offload file pairs and a .diff file, parses the node files, compares the resulting subsurface attachments, and then diffs the nodes, comparing the resulting area to the region in the .diff file.
2023-11-10 20:34:30 +00:00
)
offload_tests = [
'simple.node',
'transforms.node',
'deep.node',
'move.node',
'start_offloading.node',
'stop_offloading.node',
offload: Find and use source rectangle Look for nodes like subsurface { clip { texture {} } }, and use the clip to provide a source rectangle for subsetting the texture. Update affected tests, and add a new one.
2024-01-31 02:48:26 +00:00
'source.node',
'nested.node',
Add more offload tests These test various clip scenarios.
2024-03-11 02:08:44 +00:00
'clipped.node',
'not-clipped.node',
'complex-clip.node',
offload: Add more tests Include background in offload tests.
2024-04-15 00:53:57 +00:00
'background.node',
'background2.node',
offload: Don't assert things that might fail We can in fact meet complex transforms here. Asserting that they are simple doesn't make it so. Instead, simply bail out if a transform is too complex; in this case we can't offload anyway, so no need to walk the tree further. Test included. Fixes: #6824
2024-07-02 03:57:38 +00:00
'bad-transform.node',
testsuite: Add offload tests These tests come in two variants. The first takes .node and .offload file, parses the node file, and compares the resulting subsurface attachments to expected results. The second variant takes two .node/.offload file pairs and a .diff file, parses the node files, compares the resulting subsurface attachments, and then diffs the nodes, comparing the resulting area to the region in the .diff file.
2023-11-10 20:34:30 +00:00
]
foreach test : offload_tests
if test.endswith('.node') and not test.endswith('.out')
ci: Fix test names Don't call the offload test 'parser ...'.
2024-01-07 11:07:27 +00:00
test('offload ' + test, offload,
testsuite: Add offload tests These tests come in two variants. The first takes .node and .offload file, parses the node file, and compares the resulting subsurface attachments to expected results. The second variant takes two .node/.offload file pairs and a .diff file, parses the node files, compares the resulting subsurface attachments, and then diffs the nodes, comparing the resulting area to the region in the .diff file.
2023-11-10 20:34:30 +00:00
args: [
join_paths(meson.current_source_dir(), 'offload', test)
],
env: [
'GTK_A11Y=test',
'G_TEST_SRCDIR=@0@'.format(meson.current_source_dir()),
offload: Add more tests Include background in offload tests.
2024-04-15 00:53:57 +00:00
'G_TEST_BUILDDIR=@0@'.format(meson.current_build_dir()),
'GDK_DEBUG=force-offload',
testsuite: Add offload tests These tests come in two variants. The first takes .node and .offload file, parses the node file, and compares the resulting subsurface attachments to expected results. The second variant takes two .node/.offload file pairs and a .diff file, parses the node files, compares the resulting subsurface attachments, and then diffs the nodes, comparing the resulting area to the region in the .diff file.
2023-11-10 20:34:30 +00:00
],
protocol: 'exitcode',
testsuite: Add a suite for offload tests
2024-02-07 17:37:57 +00:00
suite: ['gsk', 'offload'],
testsuite: Add offload tests These tests come in two variants. The first takes .node and .offload file, parses the node file, and compares the resulting subsurface attachments to expected results. The second variant takes two .node/.offload file pairs and a .diff file, parses the node files, compares the resulting subsurface attachments, and then diffs the nodes, comparing the resulting area to the region in the .diff file.
2023-11-10 20:34:30 +00:00
)
endif
endforeach
endif
Move transform tests to the gsk suite That is where they belong.
2019-06-03 16:10:09 +00:00
tests = [
Add a test for node bounds normalization This tests the fixes in the previous commits for some node types.
2024-02-14 01:02:47 +00:00
[ 'normalize', [ 'normalize.c', '../reftests/reftest-compare.c' ] ],
testsuite: Add a test to check scaling behavior Various GL texture formats do not support linear scaling or mipmap generation. Add a test that checks this.
2023-12-08 23:39:54 +00:00
[ 'transform' ],
[ 'shader' ],
testsuite: Add test runner for opacity tests Tests are node files dumped into testsuite/gsk/opaque They are named "name-X-Y-W-H.node" with X Y W H being the expected opaque rectangle or "name.node" if there is no opacity. A simple example is included here.
2024-07-08 08:09:47 +00:00
[ 'opaque' ],
testsuite: Mark the randomized path tests as flaky They are, and having them run in ci is counterproductive for now.
2024-02-16 15:24:58 +00:00
[ 'path', [ 'path-utils.c' ], [ 'flaky'] ],
testsuite: Add a test to check scaling behavior Various GL texture formats do not support linear scaling or mipmap generation. Add a test that checks this.
2023-12-08 23:39:54 +00:00
[ 'path-special-cases' ],
[ 'scaling' ],
Move transform tests to the gsk suite That is where they belong.
2019-06-03 16:10:09 +00:00
]
test_cargs = []
foreach t : tests
test_name = t.get(0)
test_srcs = ['@0@.c'.format(test_name)] + t.get(1, [])
testsuite: Mark the randomized path tests as flaky They are, and having them run in ci is counterproductive for now.
2024-02-16 15:24:58 +00:00
test_extra_suites = t.get(2, [])
Move transform tests to the gsk suite That is where they belong.
2019-06-03 16:10:09 +00:00
test_exe = executable(test_name, test_srcs,
build: Drop the install-tests option We no longer use installed tests in CI, so lets reap the benefit and simplify our build setup for tests.
2022-12-20 04:11:20 +00:00
dependencies : libgtk_dep,
testsuite: Mark the randomized path tests as flaky They are, and having them run in ci is counterproductive for now.
2024-02-16 15:24:58 +00:00
c_args : test_cargs + common_cflags,
build: Use a consistent style for Meson files
2020-12-15 12:31:38 +00:00
)
Move transform tests to the gsk suite That is where they belong.
2019-06-03 16:10:09 +00:00
test(test_name, test_exe,
build: Use a consistent style for Meson files
2020-12-15 12:31:38 +00:00
args: [ '--tap', '-k' ],
protocol: 'tap',
env: [
'GSK_RENDERER=cairo',
'GTK_A11Y=test',
'G_TEST_SRCDIR=@0@'.format(meson.current_source_dir()),
'G_TEST_BUILDDIR=@0@'.format(meson.current_build_dir())
],
testsuite: Mark the randomized path tests as flaky They are, and having them run in ci is counterproductive for now.
2024-02-16 15:24:58 +00:00
suite: [ 'gsk' ] + test_extra_suites,
build: Use a consistent style for Meson files
2020-12-15 12:31:38 +00:00
)
Move transform tests to the gsk suite That is where they belong.
2019-06-03 16:10:09 +00:00
endforeach
Add some tests for node diffing Nothing deep yet, but more can be added.
2021-03-28 14:21:18 +00:00
internal_tests = [
build: Sort alphabetically
2023-12-08 23:36:42 +00:00
[ 'boundingbox'],
testsuite: Mark the randomized path tests as flaky They are, and having them run in ci is counterproductive for now.
2024-02-16 15:24:58 +00:00
[ 'curve', [ ], [ 'flaky' ]],
gsk: Add tests for GskCurve
2023-07-08 15:31:29 +00:00
[ 'curve-special-cases' ],
tests: Add some fp16 tests
2021-07-13 13:02:16 +00:00
[ 'diff' ],
[ 'half-float' ],
build: Sort alphabetically
2023-12-08 23:36:42 +00:00
[ 'misc'],
[ 'path-private' ],
[ 'rounded-rect'],
Add some tests for node diffing Nothing deep yet, but more can be added.
2021-03-28 14:21:18 +00:00
]
foreach t : internal_tests
test_name = t.get(0)
test_srcs = ['@0@.c'.format(test_name)] + t.get(1, [])
testsuite: Mark the randomized path tests as flaky They are, and having them run in ci is counterproductive for now.
2024-02-16 15:24:58 +00:00
test_extra_suites = t.get(2, [])
Add some tests for node diffing Nothing deep yet, but more can be added.
2021-03-28 14:21:18 +00:00
build: Drop the install-tests option We no longer use installed tests in CI, so lets reap the benefit and simplify our build setup for tests.
2022-12-20 04:11:20 +00:00
test_exe = executable(test_name,
sources: test_srcs,
dependencies : libgtk_static_dep,
testsuite: Mark the randomized path tests as flaky They are, and having them run in ci is counterproductive for now.
2024-02-16 15:24:58 +00:00
c_args : test_cargs + common_cflags + ['-DGTK_COMPILATION'],
Add some tests for node diffing Nothing deep yet, but more can be added.
2021-03-28 14:21:18 +00:00
)
test(test_name, test_exe,
args: [ '--tap', '-k' ],
protocol: 'tap',
env: [
'GSK_RENDERER=cairo',
'GTK_A11Y=test',
'G_TEST_SRCDIR=@0@'.format(meson.current_source_dir()),
'G_TEST_BUILDDIR=@0@'.format(meson.current_build_dir())
],
testsuite: Mark the randomized path tests as flaky They are, and having them run in ci is counterproductive for now.
2024-02-16 15:24:58 +00:00
suite: [ 'gsk' ] + test_extra_suites,
Add some tests for node diffing Nothing deep yet, but more can be added.
2021-03-28 14:21:18 +00:00
)
endforeach
Reference in New Issue Copy Permalink