forked from hexsprite/roadrunner
-
Notifications
You must be signed in to change notification settings - Fork 1
/
README.txt
156 lines (100 loc) · 4.6 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
Waiting for stuff sucks.
roadrunner is a looping testrunner with environment preloading for test-driven
development. It makes integration testing with Plone much faster.
Currently it is focused around preloading a Plone environment but it could
also work for other frameworks as well.
It works by pre-loading Python code, setup of test layers and a default Plone
site. This is called the resident test environment.
Your tests are run in a child process which gets a copy-on-write memory space.
Other than that it pretty much works like the regular Zope testrunner.
How much faster is it?
======================
Here's an example. You are writing integration or functional tests for a Plone
application.
On this fairly current laptop it takes 25s to load Zope, Plone and setup a
sample Plone site.
Add 5 seconds for the application load and test run for a total of 30 seconds.
If you are iterating on a functional test and want to quickly check your
changes that is too long to wait.
Using roadrunner you load the environment the first time. Subsequent times
you run your test your total time will be only 5 seconds.
Yes, you can save 25 seconds every time you run your test.
How to use it?
==============
Roadrunner only currently works as part of a zc.buildout environment.
The easiest way to try it is to add it to an existing Plone 3 buildout.
Now for a sample part.
This will create a new directory in parts named by the part containing a copy
of your Zope instance environment but with the packages-under-test excluded
from being loaded via ZCML by default.
::
[roadrunner]
recipe = roadrunner:plone
packages-under-test = my.package
You can also match several packages using simple globbing, eg: my.packages.*
The parameter 'zope2-instance' allows you to specify the name of the part
which corresponds to the zope instance roadrunner will work against. The
default is 'instance'.
By default resident Plone site will be created. This should work in most
situations where you are installing add-on products that use install methods
or GenericSetup profiles.
setup-plone=0 allows you to disable the Plone site setup optimization. You
might need to do this in certain situations where you are using the profile_id
parameter.
Then you can run roadrunner::
$ bin/roadrunner -s my.package
It will preload Zope & Plone, then fork off the first testrunner. Once the
first testrunner is complete you will receive the roadrunner prompt where
you launch additional tests.
Recipe Options
==============
zope2-instance:
The zope2 instance to use for basing the installation on. Defaults
to 'instance'.
Gotchas
=======
- roadrunner is still a bit experimental. If in doubt, check it with the
regular testrunner. If you find a difference please send some details
including traceback, product versions, buildout.cfg and your tests.
- It may require you to change your test setup slightly if you haven't yet
already.
You'll be fine as long as you follow the standard sequence of importing your
product, loading its ZCML and then calling ztc.installProduct within an
@onsetup deferred method.
This allows the loading of your product to occur in the child testrunner
process which critical that roadrunner does what its supposed to do.
For more details see an example here:
http://plone.org/documentation/tutorial/testing/writing-a-plonetestcase-unit-integration-test
- Because it preloads the Plone environment you won't be able to see changes
to the Core Plone components. However, it should see all changes in your
application code which is what you will most likely be changing anyways.
Other options to speed up Plone testing
=======================================
plone.reload is excellent to do exploratory testing and development.
Known Issues
============
- ZCML registrations lost. This can occur if you run unit tests which employ
PlacelessSetup. A simple workaround is to avoid running unit tests and
integration tests together with roadrunner. You can run them separately
without issue.
Source & Bug Tracker
====================
Source Code:
http://github.com/hexsprite/roadrunner
Tracker:
http://hexsprite.lighthouseapp.com/projects/21973-roadrunner
Tested With
===========
Plone 3.1.x Let me know if you get it working on anything else.
Have also had reports of success with Plone 2.5.x
Also there are reports of success with Zope 2.9.8 and Plone 2.5.5.
Windows is untested and probably does not work currently. Feedback and patches
accepted.
Author
======
Send questions, comments & bug reports to:
Jordan Baker <jbb@no_spam_plz_scryent.com>
License
=======
Licensed under ZPL 2.1
see doc/LICENSE.txt