gtk2/testsuite/tools/settings.in

#! /bin/bash

GTK_QUERY_SETTINGS=${GTK_QUERY_SETTINGS:-gtk4-query-settings}
TEST_RESULT_DIR=${TEST_RESULT_DIR:-/tmp}

shopt -s nullglob

echo "1..1"

name=gtk-query-settings
result=$TEST_RESULT_DIR/$name.out
$GTK_QUERY_SETTINGS 2>/dev/null >$result
if [ $(wc -l $result | cut -f1 -d' ') -eq 882 ]; then
  echo "ok 1 $name"
else
  echo "not ok 1 $name"
fi
Add a test that dumps settings This is not much of a test, tbh. But it will give us a convenient dump of all GTK+ settings in continuous, which helps with tracking down test failures that might depend on settings. 2016-03-05 18:41:47 +00:00			`#! /bin/bash`

Update the test scripts All tools got renamed to have a gtk4 prefix. 2019-11-29 14:51:35 +00:00			`GTK_QUERY_SETTINGS=${GTK_QUERY_SETTINGS:-gtk4-query-settings}`
Add a test that dumps settings This is not much of a test, tbh. But it will give us a convenient dump of all GTK+ settings in continuous, which helps with tracking down test failures that might depend on settings. 2016-03-05 18:41:47 +00:00			`TEST_RESULT_DIR=${TEST_RESULT_DIR:-/tmp}`

			`shopt -s nullglob`

			`echo "1..1"`

			`name=gtk-query-settings`
			`result=$TEST_RESULT_DIR/$name.out`
			`$GTK_QUERY_SETTINGS 2>/dev/null >$result`
Make the settings test fail Small thinko: We only get to see the test artifacts in continuous if the test fails. So make it fail, temporarily. 2016-03-05 20:48:40 +00:00			`if [ $(wc -l $result \| cut -f1 -d' ') -eq 882 ]; then`
Add a test that dumps settings This is not much of a test, tbh. But it will give us a convenient dump of all GTK+ settings in continuous, which helps with tracking down test failures that might depend on settings. 2016-03-05 18:41:47 +00:00			`echo "ok 1 $name"`
			`else`
			`echo "not ok 1 $name"`
			`fi`