Adding upstream version 1.2.2.upstream/1.2.2upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 26 insertions, 0 deletions

diff --git a/testfiles/rendering_tests/README b/testfiles/rendering_tests/README
new file mode 100644
index 0000000..6ebcb4c
--- /dev/null
+++ b/testfiles/rendering_tests/README
@@ -0,0 +1,26 @@
+HOWTO
+
+# Add a rendering test:
+  - create the svg file
+  - 0.92:
+  	- inkscape <yourfile>.svg -d 96  -e expected_rendering/<yourfile>.png
+  	- inkscape <yourfile>.svg -d 384 -e expected_rendering/<yourfile>-large.png
+  - 1.0:
+	- inkscape -d  96 --export-filename=expected_rendering/<yourfile>.png <yourfile>.svg
+	- inkscape -d 384 --export-filename=expected_rendering/<yourfile>-large.png <yourfile>.svg
+  - add the test in CMakeLists.txt
+  - use stable if possible to generate the reference png files
+  - git add <yourfile>.svg expected_rendering/<yourfile>-large.png expected_rendering/<yourfile>.png
+
+# Fix a failing test (due to a change in code):
+  - DO *NOT* MODIFY the expected rendering (or the svg) before getting advice from inkscape-devel@
+  - fix your code if possible
+  - IF you change introduces a greater compatibility with css or browsers
+    - AND you cannot reasonably "update" files from older versions to match the appearance
+      - AND inkscape-devel@ has a consensus that it's the only way
+        -> do as you must
+  - manually double check the changes
+
+# Fix a failing test (due to a change in pixman or cairo):
+  - update renderings. Use a *stable* version to generate the renderings, NOT TRUNK
+  - manually check appearances