summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohn Hua <john.hua@citrix.com>2016-04-14 19:05:48 +0800
committerBob Ball <bob.ball@citrix.com>2016-05-16 09:12:35 +0100
commitd202d64d8777f86fbfa7b9fb918e5f7b9ac0e4c0 (patch)
treee6c41a848036a7f9dd059df89ac6e644feafd853
parent6e81e37b1555486203546eea361caf534e7704e5 (diff)
Rewrite test plan in RST
Notes
Notes (review): Code-Review+2: Bob Ball <bob.ball@citrix.com> Workflow+1: Bob Ball <bob.ball@citrix.com> Verified+2: Jenkins Submitted-by: Jenkins Submitted-at: Mon, 16 May 2016 08:17:46 +0000 Reviewed-on: https://review.openstack.org/316626 Project: openstack/fuel-plugin-xenserver Branch: refs/heads/8.0
-rw-r--r--doc/Makefile2
-rw-r--r--doc/TestPlanforXenServerFuelPluginver3.0.0.pdfbin252005 -> 0 bytes
-rw-r--r--doc/TestReportfortheXenServerFuelPluginver3.0.0.pdfbin155225 -> 0 bytes
-rw-r--r--doc/source/conf.py8
-rw-r--r--doc/source/test-plan.rst448
-rw-r--r--doc/source/test-report.rst202
-rw-r--r--doc/test-plan.pdfbin0 -> 130741 bytes
-rw-r--r--doc/test-report.pdfbin0 -> 65873 bytes
8 files changed, 659 insertions, 1 deletions
diff --git a/doc/Makefile b/doc/Makefile
index 6c59b2a..da6e8bb 100644
--- a/doc/Makefile
+++ b/doc/Makefile
@@ -125,6 +125,8 @@ latexpdf:
125 @echo "Running LaTeX files through pdflatex..." 125 @echo "Running LaTeX files through pdflatex..."
126 $(MAKE) -C $(BUILDDIR)/latex all-pdf 126 $(MAKE) -C $(BUILDDIR)/latex all-pdf
127 @echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex." 127 @echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
128 mv $(BUILDDIR)/latex/test-plan.pdf .
129 mv $(BUILDDIR)/latex/test-report.pdf .
128 130
129latexpdfja: 131latexpdfja:
130 $(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex 132 $(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
diff --git a/doc/TestPlanforXenServerFuelPluginver3.0.0.pdf b/doc/TestPlanforXenServerFuelPluginver3.0.0.pdf
deleted file mode 100644
index 482aa46..0000000
--- a/doc/TestPlanforXenServerFuelPluginver3.0.0.pdf
+++ /dev/null
Binary files differ
diff --git a/doc/TestReportfortheXenServerFuelPluginver3.0.0.pdf b/doc/TestReportfortheXenServerFuelPluginver3.0.0.pdf
deleted file mode 100644
index 45a4828..0000000
--- a/doc/TestReportfortheXenServerFuelPluginver3.0.0.pdf
+++ /dev/null
Binary files differ
diff --git a/doc/source/conf.py b/doc/source/conf.py
index 0de450f..c907045 100644
--- a/doc/source/conf.py
+++ b/doc/source/conf.py
@@ -44,6 +44,8 @@ source_suffix = '.rst'
44 44
45# The master toctree document. 45# The master toctree document.
46master_doc = 'index' 46master_doc = 'index'
47test_plan = 'test-plan'
48test_report = 'test-report'
47 49
48# General information about the project. 50# General information about the project.
49project = u'fuel-plugin-xenserver' 51project = u'fuel-plugin-xenserver'
@@ -225,7 +227,11 @@ latex_elements = {
225# author, documentclass [howto, manual, or own class]). 227# author, documentclass [howto, manual, or own class]).
226latex_documents = [ 228latex_documents = [
227 (master_doc, 'fuel-plugin-xenserver.tex', u'fuel-plugin-xenserver Documentation', 229 (master_doc, 'fuel-plugin-xenserver.tex', u'fuel-plugin-xenserver Documentation',
228 u'John Hua (john.hua@citrix.com)', 'manual'), 230 author, 'manual'),
231 (test_plan, 'test-plan.tex', u'Test Plan for XenServer Fuel Plugin',
232 author, 'howto'),
233 (test_report, 'test-report.tex', u'Test Report for XenServer Fuel Plugin',
234 author, 'howto'),
229] 235]
230 236
231# The name of an image file (relative to this directory) to place at the top of 237# The name of an image file (relative to this directory) to place at the top of
diff --git a/doc/source/test-plan.rst b/doc/source/test-plan.rst
new file mode 100644
index 0000000..cf146a0
--- /dev/null
+++ b/doc/source/test-plan.rst
@@ -0,0 +1,448 @@
1Test Plan for XenServer Fuel Plugin
2===================================
3
4XenServer Fuel Plugin
5=====================
6
7XenServer Fuel Plugin will help to deploy Mirantis OpenStack using the
8XenServer hypervisor to host virtual machines, making all the necessary
9changes to the Mirantis OpenStack to use the xenapi Nova compute driver.
10
11
12Developer’s Specification
13=========================
14
15See developers specification in the source code repository at
16https://git.openstack.org/openstack/fuel-plugin-xenserver
17
18Limitations
19-----------
20
21This version of XenServer Fuel Plugin has not been certified to work with the
22Ceilometer, MongoDB or Murano additional services. Future versions of the
23plugin will relax these restrictions.
24
25
26Test strategy
27=============
28
29Acceptance criteria
30-------------------
31
32All tests that do not depend on additional services must pass.
33
34Test environment, infrastructure and tools
35------------------------------------------
36
37All tests need to be run under a cluster of at least 4 XenServer machines
38with 3 physical NICs. As HA and multihost are enabled, a topology of 3
39Controller Nodes + 3 Compute Nodes + 1 Storage Node will be recommended to be
40created as VMs on XenServer machines. Easy setup and management of those
41XenServers and VM Nodes can be achieved using XenCenter and a plugin,
42described below, to add an internal management network to VMs.
43
44To simplify setup, the fuel master is also installed on the XenServer hosts
45(so XenServer hosts can fully control the network setup), but this is not
46required.
47
48While many networking setups are expected to work, the following setup is
49used by this test plan:
50
51* eth0 / “Access network”: Used to access the XenServer hosts and the Fuel
52Master’s web interface
53* eth1 / “Control network”: OpenStack control plane (management and storage),
54the PXE network and the public network; all separated by VLAN tags. The
55public network is also on this network, and if a VLAN is required this is
56applied by the switch for untagged traffic.
57* eth2 / “VLAN network”: This version of the plugin only supports VLAN
58segmentation for Neutron networking. This device carries all of the VLANs to
59be used by Neutron for VM traffic.
60
61 .. image:: _static/topology00.png
62 :width: 80%
63
64Product compatibility matrix
65----------------------------
66
67The plugin is compatible with MOS 8.0 and XenServer 6.5 SP1, with all
68hotfixes applied (Especially hotfix XS65ESP1013).
69
70
71Prerequirements
72===============
73
74Prepare XenServers
75------------------
76
77#. Install and start XenCenter on your Windows PC
78#. Add new servers with a common root password in XenCenter
79#. Plug three physical NIC to each of all XenServer machines, make sure the
80 cabling of all NIC 0 are attached to the ‘access’ network, all NIC 1 to the
81 ‘public’ network and NIC 2 are attached to the isolated, ‘VLAN network’.
82 It is recommended to rename these networks using XenCenter to make the
83 network topology clear.
84#. Add a further network, with a vlan tag that will be used for PXE.
85
86Prepare Fuel Master
87-------------------
88
89#. Upload Fuel ISO to a NFS/Samba server and make it accessible to your
90 XenServer hosts.
91#. Select a XenServer and click “New Storage” button, in the popup window
92 check on CIFS/NFS ISO library and input NFS/Samba server path.
93#. Create a new VM in XenCenter using the “Other Install Media” template (to
94 ensure a HVM domain is created) with and PXE network as eth0 and ‘access’
95 network as eth1. In the Console Tab, insert Fuel ISO and install.
96#. In fuel menu, enable eth1 with DHCP so the fuel master can be accessed
97 over the ‘access’ network.
98#. Select Fuel Master in XenCenter and switch to Console tab, login with
99 prompted user and password
100#. Visit http://ip_of_fuel_master:8000 in browser.
101
102
103Type of testing
104===============
105
106Install XenServer Fuel Plugin
107-----------------------------
108
109.. tabularcolumns:: |p{3cm}|p{13cm}|
110
111.. list-table::
112 :header-rows: 0
113
114 * - Test Case ID
115 - insall_xfp
116 * - Description
117 - Verify that XenServer Fuel Plugin can be installed into Fuel Master,
118 and the new OpenStack release is registered.
119 * - Steps
120 -
121 | ``[root@fuel-master ~]# fuel plugins``
122 | ``id | name | version | package_version``
123 | ``9 | fuel-plugin-xenserver | 3.0.0 | 3.0.0``
124 * - Expected Result
125 -
126 | ``fuel plugins``
127 | ``id | name | version | package_version``
128 | ``2 | fuel-plugin-xenserver | 3.0.0 | 3.0.0``
129 | ``fuel rel``
130 | ``id | name | state | operating_system | version``
131 | ``2 | Liberty on Ubuntu 14.04 | available | Ubuntu | liberty-8.0``
132 | ``3 | Liberty+Citrix XenServer on Ubuntu 14.04 | available | Ubuntu | liberty-8.0``
133 | ``1 | Liberty on CentOS 6.5 | unavailable | CentOS | liberty-8.0``
134
135Prepare Nodes
136-------------
137
138.. tabularcolumns:: |p{3cm}|p{13cm}|
139
140.. list-table::
141 :header-rows: 0
142
143 * - Test Case ID
144 - prepare_nodes
145 * - Description
146 - Verify all controller/compute/storage nodes are ready for PXE install.
147 * - Steps
148 -
149 #. Create 3 new VMs in XenCenter in different XenServers and name them
150 Controller1, Controller2, Controller3
151 #. Create 3 new VMs in XenCenter in different XenServers and name them
152 Compute1, Compute2, Compute3
153 #. Create 1 new VM in XenCenter and name it Storage1
154 #. Add ‘PXE’ network as eth0, Public/Management/Storage network as
155 eth1 and ‘VLAN network’ as eth2 to each of new VMs created above.
156
157 * - Expected Result
158 - All nodes are shown in XenCenter with ‘PXE network’ as eth0 and ‘VLAN
159 network’ as eth1.
160
161Install XenCenter HIMN plugin
162-----------------------------
163
164.. tabularcolumns:: |p{3cm}|p{13cm}|
165
166.. list-table::
167 :header-rows: 0
168
169 * - Test Case ID
170 - install_xcp
171 * - Description
172 - Verify XenCenter HIMN plugin is installed to Windows.
173 * - Steps
174 -
175 #. Download SetupHIMN from http://ca.downloads.xensource.com/OpenStack/Plugins/
176 #. Install MSI to your XenCenter
177 #. Restart XenCenter
178 * - Expected Result
179 - Right click on any selected VMs, there will be a menu item “Manage
180 internal management network”.
181
182Add Host Internal Management Network to Compute Nodes
183-----------------------------------------------------
184
185.. tabularcolumns:: |p{3cm}|p{13cm}|
186
187.. list-table::
188 :header-rows: 0
189
190 * - Test Case ID
191 - add_himn
192 * - Description
193 - Verify (or add) Host Internal Management Network is added to all
194 Compute Nodes.
195 * - Steps
196 -
197 #. Select Compute1, Compute2, Compute3 in XenCenter
198 #. Right click on above nodes and select “Manage internal management
199 network” menu.
200 #. In the popup window, after status detection, make sure all selected
201 Compute nodes are checked on. Click on “Manage internal management
202 network” button.
203 #. After processing, the status column should be shown as management
204 network is added with new generated MAC address
205 #. Close the management network window
206 * - Expected Result
207 - The wizard will report success, however the networks may not be
208 visible in XenCenter.
209
210Create an OpenStack environment with XenServer Fuel Plugin
211----------------------------------------------------------
212
213.. tabularcolumns:: |p{3cm}|p{13cm}|
214
215.. list-table::
216 :header-rows: 0
217
218 * - Test Case ID
219 - create_env
220 * - Description
221 - Verify that an OpenStack environment created with XenServer Fuel
222 Plugin can have XenServer options and options of
223 hypervisor/network/storage/additional services are disabled.
224 * - Steps
225 -
226 #. Create new OpenStack environment Fuel Web UI and select
227 “Liberty+Citrix XenServer on Ubuntu 14.04” in the OpenStack release
228 dropdown list
229 #. Hypervisor is default to QEMU, Network is default to “Neutron with
230 VLAN segmentation” and Storage is default to Cinder. Other options
231 are disabled.
232 #. In Nodes Tab, add all 3 Controller Nodes, 3 Compute Nodes and 1
233 Storage Node.
234 #. Select all Compute Nodes and click “Configure Interfaces”, drag
235 Storage/Management network from default eth0 to eth1, Private
236 network to eth2. Leave PXE on eth0. No networks should be
237 assigned to the final interface.
238 #. Select all Controller and Storage Nodes and click “Configure
239 Interfaces”, drag Storage/Management network from default eth0 to
240 eth1, Private network to eth2. Leave PXE on eth0.
241 #. In Networks Tab, set the vlan tags according to your network
242 interfaces previous set and make sure network range will not be
243 conflicting with other systems in the same lab. Then click “Verify
244 Networks” button.
245 #. In the Settings Tab under the side tab “Others”, input the
246 credential applied to all your XenServer hosts.
247 #. Click “Deploy Changes” button
248 * - Expected Result
249 - Deploy of nodes all succeed
250
251Verify hypervisor type
252----------------------
253
254.. tabularcolumns:: |p{3cm}|p{13cm}|
255
256.. list-table::
257 :header-rows: 0
258
259 * - Test Case ID
260 - verify_hypervisor
261 * - Description
262 - Verify that all hypervisors are identified by OpenStack as ‘xen’.
263 * - Steps
264 -
265 #. Login to Horizon with admin user when OpenStack deployment is
266 finished.
267 #. Enter into Admin->Hypervisors
268 * - Expected Result
269 - The Type column should show xen for all hypervisors.
270
271Create guest instances
272----------------------
273
274.. tabularcolumns:: |p{3cm}|p{13cm}|
275
276.. list-table::
277 :header-rows: 0
278
279 * - Test Case ID
280 - create_instances
281 * - Description
282 - Verify that new environment can create guest instances.
283 * - Steps
284 -
285 #. Create an instance with image of TestVM and flavor of m1.tiny in
286 either of Horizon or Controller Node.
287 #. Find the instance in XenCenter and switch to Console Tab.
288 #. Login with the username and password that prompted in the terminal
289 screen.
290 #. Ping out to 8.8.8.8
291 * - Expected Result
292 - Guest instances can ping out.
293
294Verify Fuel Health Checks
295-------------------------
296
297.. tabularcolumns:: |p{3cm}|p{13cm}|
298
299.. list-table::
300 :header-rows: 0
301
302 * - Test Case ID
303 - verify_health_checks
304 * - Description
305 - Ensure that all applicable health checks pass
306 * - Steps
307 -
308 #. Within the Fuel Master, select the appropriate environment
309 #. Run all health checks and wait for completion
310 * - Expected Result
311 - All health checks, except those requiring additional services
312 (e.g. Ceilometer) and those where the configuration has not been
313 changed from the defaults, pass
314
315Mandatory Tests
316===============
317
318Install plugin and deploy environment
319-------------------------------------
320
321Covered above.
322
323Modifying env with enabled plugin (removing/adding compute nodes)
324-----------------------------------------------------------------
325
326.. tabularcolumns:: |p{3cm}|p{13cm}|
327
328.. list-table::
329 :header-rows: 0
330
331 * - Test Case ID
332 - modify_env_compute_nodes
333 * - Description
334 - Adding/removing compute nodes to an existing environment
335 * - Steps
336 -
337 #. Create one more compute following the procedure in step
338 prepare_nodes
339 #. Add compute node to an existing environment
340 #. Redeploy cluster
341 #. Run Health Check
342 #. Remove a compute node
343 #. Redeploy cluster
344 #. Run Health Check
345 * - Expected Result
346 - Removing a compute node will cause “Sanity tests-Check that required
347 services are running” fail. “Some nova services have not been
348 started.. Please refer to OpenStack logs for more details.”
349
350Modifying env with enabled plugin (removing/adding controller nodes)
351--------------------------------------------------------------------
352
353.. tabularcolumns:: |p{3cm}|p{13cm}|
354
355.. list-table::
356 :header-rows: 0
357
358 * - Test Case ID
359 - modify_env_controller_nodes
360 * - Description
361 - Adding/removing controller nodes to an existing environment
362 * - Steps
363 -
364 #. Create one more controller following the procedure in step
365 prepare_nodes
366 #. Add controller node to an existing environment
367 #. Redeploy cluster
368 #. Run Health Check
369 #. Remove a compute node (not the primary controller node)
370 #. Redeploy cluster
371 #. Run Health Check
372 * - Expected Result
373 - (Probably caused by previous test modify_env_compute_nodes)Removing a
374 compute node will cause “Sanity tests-Check that required services are
375 running” fail. “Some nova services have not been started.. Please
376 refer to OpenStack logs for more details.”
377
378Uninstall of plugin with deployed environment
379---------------------------------------------
380
381.. tabularcolumns:: |p{3cm}|p{13cm}|
382
383.. list-table::
384 :header-rows: 0
385
386 * - Test Case ID
387 - uninstall_plugin_with_deployed_env
388 * - Description
389 - Verify XenServer Fuel Plugin cannot be uninstalled before all
390 dependant environments are removed.
391 * - Steps
392 - ``fuel plugins --remove fuel-plugin-xenserver==3.0.0``
393 * - Expected Result
394 - 400 Client Error: Bad Request (Can't delete plugin which is enabled
395 for some environment.)
396
397Uninstall of plugin
398-------------------
399
400.. tabularcolumns:: |p{3cm}|p{13cm}|
401
402.. list-table::
403 :header-rows: 0
404
405 * - Test Case ID
406 - uninstall_plugin
407 * - Description
408 - Verify XenServer Fuel Plugin can be uninstalled as well as XenServer
409 OpenStack release after all dependant environments are removed.
410 * - Steps
411 - | ``fuel plugins --remove fuel-plugin-xenserver==3.0.0``
412 | ``fuel rel``
413 | ``id | name | state | operating_system | version``
414 | ``2 | Liberty on Ubuntu 14.04 | available | Ubuntu | liberty-8.0``
415 | ``3 | Liberty+Citrix XenServer on Ubuntu 14.04 | available | Ubuntu | liberty-8.0``
416 | ``1 | Liberty on CentOS 6.5 | unavailable | CentOS | liberty-8.0``
417 * - Expected Result
418 - Both of plugin and release are removed.
419
420Appendix
421========
422
423* XenServer Fuel Plugin GitHub: https://git.openstack.org/openstack/fuel-plugin-xenserver
424* XenCenter HIMN Plugin GitHub: https://github.com/citrix-openstack/xencenter-himn-plugin
425* Plugin download server: http://ca.downloads.xensource.com/OpenStack/Plugins/
426
427Revision history
428================
429
430.. list-table::
431 :header-rows: 1
432
433 * - Version
434 - Revision Date
435 - Editor
436 - Comment
437 * - 1.0
438 - 18.09.2015
439 - John Hua (john.hua@citrix.com)
440 - First draft.
441 * - 2.0
442 - 18.11.2015
443 - John Hua (john.hua@citrix.com)
444 - Revised for Fuel 7.0
445 * - 3.0
446 - 22.03.2016
447 - John Hua (john.hua@citrix.com)
448 - Revised for Fuel 8.0 \ No newline at end of file
diff --git a/doc/source/test-report.rst b/doc/source/test-report.rst
new file mode 100644
index 0000000..1979ede
--- /dev/null
+++ b/doc/source/test-report.rst
@@ -0,0 +1,202 @@
1Test Report for XenServer Fuel Plugin
2=====================================
3
4Revision history
5================
6
7.. tabularcolumns:: |p{1.5cm}|p{2.5cm}|p{7cm}|p{4.5cm}|
8
9.. list-table::
10 :header-rows: 1
11
12 * - Version
13 - Revision Date
14 - Editor
15 - Comment
16 * - 1.0
17 - 25.09.2015
18 - John Hua(john.hua@citrix.com)
19 - First draft.
20 * - 2.0
21 - 8.11.2015
22 - John Hua(john.hua@citrix.com)
23 - Revised for Mirantis Fuel 7.0
24 * - 3.0
25 - 13.04.2016
26 - John_Hua(john.hua@citrix.com)
27 Jianghua_Wang(jianghua.wang@citrix.com)
28 - Revised for Mirantis Fuel 8.0
29 * - 3.1
30 - 19.04.2016
31 - John Hua(john.hua@citrix.com)
32 - Rewrite in RST
33
34Document purpose
35================
36
37This document provides test run results for the XenServer Fuel Plugin version
383.0.0 on Mirantis OpenStack 8.0.
39
40Test environment
41================
42
43The following is the hardware configuration for target nodes used for
44verification. For other configuration settings, please see the test plan.
45
46.. list-table::
47 :header-rows: 1
48
49 * - Node Type
50 - vCPU
51 - Memory
52 - Disk
53 * - Controller
54 - 4
55 - 6GB
56 - 80GB
57 * - Compute
58 - 4
59 - 4GB
60 - 60GB
61 * - Storage
62 - 4
63 - 4GB
64 - 60GB
65
66Test coverage and metrics
67-------------------------
68
69* Test Coverage – 100%
70* Tests Passed – 100%
71* Tests Failed – 0%
72
73Test results summary
74====================
75
76Type of testing
77===============
78
79System Testing
80--------------
81
82.. list-table::
83 :header-rows: 1
84
85 * - Parameter
86 - Value
87 * - Total quantity of executed test cases
88 - 12
89 * - Total quantity of not executed test cases
90 - 0
91 * - Quantity of automated test cases
92 - 0
93 * - Quantity of not automated test cases
94 - 0
95
96Detailed test run results
97-------------------------
98
99.. tabularcolumns:: |p{1cm}|p{4cm}|p{1.2cm}|p{1.2cm}|p{1.2cm}|p{7cm}|
100
101.. list-table::
102 :header-rows: 1
103
104 * - #
105 - Test case ID
106 - Passed
107 - Failed
108 - Skipped
109 - Comment
110 * - 1
111 - Install XenServer Fuel Plugin
112 - Yes
113 -
114 -
115 -
116 * - 2
117 - Prepare Nodes
118 - Yes
119 -
120 -
121 -
122 * - 3
123 - Install XenCenter HIMN plugin
124 - Yes
125 -
126 -
127 -
128 * - 4
129 - Add Host Internal Management Network to Compute Nodes
130 - Yes
131 -
132 -
133 -
134 * - 5
135 - Create an OpenStack environment with XenServer Fuel Plugin
136 - Yes
137 -
138 -
139 -
140 * - 6
141 - Verify hypervisor type
142 - Yes
143 -
144 -
145 -
146 * - 7
147 - Create guest instances
148 - Yes
149 -
150 -
151 -
152 * - 8
153 - Verify Fuel Health Checks
154 - Yes
155 -
156 -
157 -
158 * - 9
159 - Add/Remove compute node
160 - Yes
161 -
162 -
163 - Removing a compute node will cause “Sanity tests-Check that required
164 services are running” fail. “Some nova services have not been
165 started.. Please refer to OpenStack logs for more details.”
166 * - 10
167 - Add/Remove controller node
168 - Yes
169 -
170 -
171 - Removing a controller node will cause “Sanity tests-Check that
172 required services are running” fail. “Some nova services have not been
173 started.. Please refer to OpenStack logs for more details.”
174 * - 11
175 - Uninstall of plugin with deployed environment
176 - Yes
177 -
178 -
179 -
180 * - 12
181 - Uninstall of plugin
182 - Yes
183 -
184 -
185 -
186 * - Total
187 -
188 - 12
189 - 0
190 - 0
191 -
192 * - Total,%
193 -
194 - 100
195 - 0
196 - 0
197 -
198
199Known issues
200============
201
202No issues were found during the testing
diff --git a/doc/test-plan.pdf b/doc/test-plan.pdf
new file mode 100644
index 0000000..6ba9312
--- /dev/null
+++ b/doc/test-plan.pdf
Binary files differ
diff --git a/doc/test-report.pdf b/doc/test-report.pdf
new file mode 100644
index 0000000..58228ab
--- /dev/null
+++ b/doc/test-report.pdf
Binary files differ