tests: Use Regress GIR for doctool

This makes us test a lot more functionality in the doc tool, and
removes the need to have a lot of different test libraries, and
different test infrastructure.

1 files changed, 0 insertions, 44 deletions

diff --git a/tests/doctool/DocExamples-1.0-Python-expected/DocExamples.Obj-signal-example.page b/tests/doctool/DocExamples-1.0-Python-expected/DocExamples.Obj-signal-example.page
deleted file mode 100644
index 1dc5d60d..00000000
--- a/tests/doctool/DocExamples-1.0-Python-expected/DocExamples.Obj-signal-example.page
+++ /dev/null
@@ -1,44 +0,0 @@
-<?xml version="1.0"?>
-<page id="DocExamples.Obj-signal-example"
-      type="topic"
-      style="signal"
-      xmlns="http://projectmallard.org/1.0/"
-      xmlns:api="http://projectmallard.org/experimental/api/"
-      xmlns:ui="http://projectmallard.org/1.0/ui/">
-  <info>
-    
-    <link type="guide" xref="DocExamples.Obj" group="signal"/>
-    <title type="link" role="topic">signal-example</title>
-
-  </info>
-  <title>DocExamples.Obj::signal-example</title>
-  
-<synopsis><code mime="text/x-python">
-def callback(obj, int_param, float_param, pointer_param, user_param1, ...)
-</code></synopsis>
-
-  
-    <p>This is an example of how to document a signal.</p>
-  
-  
-    <p>Since 0.99</p>
-  
-  
-<dl>
-<dt><p>obj :</p></dt>
-<dd><p>instance of DocExamples.Obj that is emitting the signal</p></dd>
-<dt><p>int_param :</p></dt>
-<dd><p>a parameter of type int</p></dd>
-<dt><p>float_param :</p></dt>
-<dd><p>a parameter of type float</p></dd>
-<dt><p>pointer_param :</p></dt>
-<dd><p>A pointer to @obj's thingy -- pass <code>int_param</code> if you really want to.</p></dd>
-<dt><p>user_param1 :</p></dt>
-<dd><p>first user parameter (if any) specified with the connect() method</p></dd>
-<dt><p>... :</p></dt>
-<dd><p>additional user parameters (if any)</p></dd>
-</dl>
-
-  
-  
-</page>