zope.testbrowser
¶
Contents:
Using zope.testbrowser
¶
Different Browsers¶
HTTP Browser¶
The zope.testbrowser.browser
module exposes a Browser
class that
simulates a web browser similar to Mozilla Firefox or IE.
>>> from zope.testbrowser.browser import Browser
>>> browser = Browser()
This version of the browser object can be used to access any web site just as you would do using a normal web browser.
WSGI Test Browser¶
General usage¶
There is also a special version of the Browser
class which uses
WebTest and can be used to do functional testing of WSGI
applications. It can be imported from zope.testbrowser.wsgi
:
>>> from zope.testbrowser.wsgi import Browser
>>> from zope.testbrowser.testing import demo_app
>>> browser = Browser('http://localhost/', wsgi_app=demo_app)
>>> print(browser.contents)
Hello world!
...
You can also use it with zope layers if you
write a subclass of
zope.testbrowser.wsgi.Layer
and override themake_wsgi_app
method, thenuse an instance of the class as the test layer of your test.
Example:
>>> import zope.testbrowser.wsgi
>>> class SimpleLayer(zope.testbrowser.wsgi.Layer):
... def make_wsgi_app(self):
... return simple_app
Where simple_app
is the callable of your WSGI application.
Testing a Zope 2/Zope 3/Bluebream WSGI application¶
When testing a Zope 2/Zope 3/Bluebream WSGI application you should wrap your
WSGI application under test into
zope.testbrowser.wsgi.AuthorizationMiddleware
as all these application
servers expect basic authentication headers to be base64 encoded. This
middleware handles this for you.
Example when using the layer:
>>> import zope.testbrowser.wsgi
>>> class ZopeSimpleLayer(zope.testbrowser.wsgi.Layer):
... def make_wsgi_app(self):
... return zope.testbrowser.wsgi.AuthorizationMiddleware(simple_app)
There is also a BrowserLayer
in zope.app.wsgi.testlayer which does this
for you and includes a TransactionMiddleware
, too, which could be handy
when testing a ZODB based application.
However, since the BrowserLayer
in zope.app.wsgi.testlayer re-creates
the ZODB in testSetUp
, we need to re-create the WSGI App during
testSetUp
, too. Therefore use TestBrowserLayer
of
zope.testbrowser.wsgi
instead of the simpler Layer
to combine it with
the BrowserLayer
in zope.app.wsgi.testlayer:
>>> import zope.testbrowser.wsgi
>>> import zope.app.wsgi.testlayer
>>> class Layer(zope.testbrowser.wsgi.TestBrowserLayer,
... zope.app.wsgi.testlayer.BrowserLayer):
... pass
Browser Usage¶
We will test this browser against a WSGI test application:
>>> from zope.testbrowser.ftests.wsgitestapp import WSGITestApplication
>>> wsgi_app = WSGITestApplication()
An initial page to load can be passed to the Browser
constructor:
>>> browser = Browser('http://localhost/@@/testbrowser/simple.html', wsgi_app=wsgi_app)
>>> browser.url
'http://localhost/@@/testbrowser/simple.html'
The browser can send arbitrary headers; this is helpful for setting the “Authorization” header or a language value, so that your tests format values the way you expect in your tests, if you rely on zope.i18n locale-based formatting or a similar approach.
>>> browser.addHeader('Authorization', 'Basic mgr:mgrpw')
>>> browser.addHeader('Accept-Language', 'en-US')
An existing browser instance can also open web pages:
>>> browser.open('http://localhost/@@/testbrowser/simple.html')
>>> browser.url
'http://localhost/@@/testbrowser/simple.html'
Once you have opened a web page initially, best practice for writing testbrowser doctests suggests using ‘click’ to navigate further (as discussed below), except in unusual circumstances.
The test browser complies with the IBrowser interface; see
zope.testbrowser.interfaces
for full details on the interface.
>>> from zope.testbrowser import interfaces
>>> from zope.interface.verify import verifyObject
>>> verifyObject(interfaces.IBrowser, browser)
True
Page Contents¶
The contents of the current page are available:
>>> print(browser.contents)
<html>
<head>
<title>Simple Page</title>
</head>
<body>
<h1>Simple Page</h1>
</body>
</html>
Making assertions about page contents is easy.
>>> '<h1>Simple Page</h1>' in browser.contents
True
Utilizing the doctest facilities, it also possible to do:
>>> browser.contents
'...<h1>Simple Page</h1>...'
Note: Unfortunately, ellipsis (…) cannot be used at the beginning of the output (this is a limitation of doctest).
Checking for HTML¶
Not all URLs return HTML. Of course our simple page does:
>>> browser.open('http://localhost/@@/testbrowser/simple.html')
>>> browser.isHtml
True
But if we load an image (or other binary file), we do not get HTML:
>>> browser.open('http://localhost/@@/testbrowser/zope3logo.gif')
>>> browser.isHtml
False
HTML Page Title¶
Another useful helper property is the title:
>>> browser.open('http://localhost/@@/testbrowser/simple.html')
>>> browser.title
'Simple Page'
If a page does not provide a title, it is simply None
:
>>> browser.open('http://localhost/@@/testbrowser/notitle.html')
>>> browser.title
However, if the output is not HTML, then an error will occur trying to access the title:
>>> browser.open('http://localhost/@@/testbrowser/zope3logo.gif')
>>> browser.title
Traceback (most recent call last):
...
BrowserStateError: not viewing HTML
Headers¶
As you can see, the contents of the browser does not return any HTTP
headers. The headers are accessible via a separate attribute, which is an
http.client.HTTPMessage
instance (from the Python’s standard
library):
>>> from six.moves import http_client
>>> browser.open('http://localhost/@@/testbrowser/simple.html')
>>> isinstance(browser.headers, http_client.HTTPMessage)
True
The headers can be accessed as a string:
>>> print(browser.headers)
...
Status: 200 OK
Content-Length: 109
Content-Type: text/html; charset=UTF-8
Or as a mapping:
>>> browser.headers['content-type']
'text/html; charset=UTF-8'
Controls¶
One of the most important features of the browser is the ability to inspect and fill in values for the controls of input forms. To do so, let’s first open a page that has a bunch of controls:
>>> browser.open('http://localhost/@@/testbrowser/controls.html')
Obtaining a Control¶
You look up browser controls with the ‘getControl’ method. The default first argument is ‘label’, and looks up the form on the basis of any associated label.
>>> control = browser.getControl('Text Control')
>>> control
<Control name='text-value' type='text'>
>>> browser.getControl(label='Text Control') # equivalent
<Control name='text-value' type='text'>
If you request a control that doesn’t exist, the code raises a LookupError:
>>> browser.getControl('Does Not Exist')
Traceback (most recent call last):
...
LookupError: label 'Does Not Exist'
available items:
<TextControl(text-value=Some Text)>
<PasswordControl(password-value=Password)>
<HiddenControl(hidden-value=Hidden) (readonly)>
...
If you request a control with an ambiguous lookup, the code raises an AmbiguityError.
>>> browser.getControl('Ambiguous Control')
Traceback (most recent call last):
...
AmbiguityError: label 'Ambiguous Control' matches:
<TextControl(ambiguous-control-name=First)>
<TextControl(ambiguous-control-name=Second)>
This is also true if an option in a control is ambiguous in relation to the control itself.
>>> browser.getControl('Sub-control Ambiguity')
Traceback (most recent call last):
...
AmbiguityError: label 'Sub-control Ambiguity' matches:
<SelectControl(ambiguous-subcontrol=[*, ambiguous])>
<Item name='ambiguous' id=None contents='Sub-control Ambiguity Exemplified' value='ambiguous' label='Sub-control Ambiguity Exemplified'>
Ambiguous controls may be specified using an index value. We use the control’s value attribute to show the two controls; this attribute is properly introduced below.
>>> browser.getControl('Ambiguous Control', index=0)
<Control name='ambiguous-control-name' type='text'>
>>> browser.getControl('Ambiguous Control', index=0).value
'First'
>>> browser.getControl('Ambiguous Control', index=1).value
'Second'
>>> browser.getControl('Sub-control Ambiguity', index=0)
<ListControl name='ambiguous-subcontrol' type='select'>
>>> browser.getControl('Sub-control Ambiguity', index=1).optionValue
'ambiguous'
>>> browser.getControl('Sub-control Ambiguity', index=2)
Traceback (most recent call last):
...
LookupError: label 'Sub-control Ambiguity'
Index 2 out of range, available choices are 0...1
0: <SelectControl(ambiguous-subcontrol=[*, ambiguous])>
1: <Item name='ambiguous' id=None contents='Sub-control Ambiguity Exemplified' value='ambiguous' label='Sub-control Ambiguity Exemplified'>
Label searches are against stripped, whitespace-normalized, no-tag versions of the text. Text applied to searches is also stripped and whitespace normalized. The search finds results if the text search finds the whole words of your text in a label. Thus, for instance, a search for ‘Add’ will match the label ‘Add a Client’ but not ‘Address’. Case is honored.
>>> browser.getControl('Label Needs Whitespace Normalization')
<Control name='label-needs-normalization' type='text'>
>>> browser.getControl('label needs whitespace normalization')
Traceback (most recent call last):
...
LookupError: label 'label needs whitespace normalization'
...
>>> browser.getControl(' Label Needs Whitespace ')
<Control name='label-needs-normalization' type='text'>
>>> browser.getControl('Whitespace')
<Control name='label-needs-normalization' type='text'>
>>> browser.getControl('hitespace')
Traceback (most recent call last):
...
LookupError: label 'hitespace'
...
>>> browser.getControl('[non word characters should not confuse]')
<Control name='non-word-characters' type='text'>
Multiple labels can refer to the same control (simply because that is possible in the HTML 4.0 spec).
>>> browser.getControl('Multiple labels really')
<Control name='two-labels' type='text'>
>>> browser.getControl('really are possible')
<Control name='two-labels' type='text'>
>>> browser.getControl('really') # OK: ambiguous labels, but not ambiguous control
<Control name='two-labels' type='text'>
A label can be connected with a control using the ‘for’ attribute and also by containing a control.
>>> browser.getControl(
... 'Labels can be connected by containing their respective fields')
<Control name='contained-in-label' type='text'>
Get also accepts one other search argument, ‘name’. Only one of ‘label’ and ‘name’ may be used at a time. The ‘name’ keyword searches form field names.
>>> browser.getControl(name='text-value')
<Control name='text-value' type='text'>
>>> browser.getControl(name='ambiguous-control-name')
Traceback (most recent call last):
...
AmbiguityError: name 'ambiguous-control-name' matches:
<TextControl(ambiguous-control-name=First)>
<TextControl(ambiguous-control-name=Second)>
>>> browser.getControl(name='does-not-exist')
Traceback (most recent call last):
...
LookupError: name 'does-not-exist'
available items:
<TextControl(text-value=Some Text)>
...
>>> browser.getControl(name='ambiguous-control-name', index=1).value
'Second'
Combining ‘label’ and ‘name’ raises a ValueError, as does supplying neither of them.
>>> browser.getControl(label='Ambiguous Control', name='ambiguous-control-name')
Traceback (most recent call last):
...
ValueError: Supply one and only one of "label" and "name" as arguments
>>> browser.getControl()
Traceback (most recent call last):
...
ValueError: Supply one and only one of "label" and "name" as arguments
Radio and checkbox fields are unusual in that their labels and names may point to different objects: names point to logical collections of radio buttons or checkboxes, but labels may only be used for individual choices within the logical collection. This means that obtaining a radio button by label gets a different object than obtaining the radio collection by name. Select options may also be searched by label.
>>> browser.getControl(name='radio-value')
<ListControl name='radio-value' type='radio'>
>>> browser.getControl('Zwei')
<ItemControl name='radio-value' type='radio' optionValue='2' selected=True>
>>> browser.getControl('One')
<ItemControl name='multi-checkbox-value' type='checkbox' optionValue='1' selected=True>
>>> browser.getControl('Tres')
<ItemControl name='single-select-value' type='select' optionValue='3' selected=False>
Radio fields can even have the same name and value and only be distinguished by the id.
>>> browser.getControl(name='radio-value-a')
<ListControl name='radio-value-a' type='radio'>
>>> browser.getControl(name='radio-value-a').getControl(value='true', index=0)
<ItemControl name='radio-value-a' type='radio' optionValue='true' selected=False>
>>> browser.getControl(name='radio-value-a').getControl(value='true', index=1)
<ItemControl name='radio-value-a' type='radio' optionValue='true' selected=False>
>>> browser.getControl(name='radio-value-a').getControl(value='true', index=1).selected = True
>>> browser.getControl(name='radio-value-a').getControl(value='true', index=0)
<ItemControl name='radio-value-a' type='radio' optionValue='true' selected=False>
>>> browser.getControl(name='radio-value-a').getControl(value='true', index=1)
<ItemControl name='radio-value-a' type='radio' optionValue='true' selected=True>
Characteristics of controls and subcontrols are discussed below.
Control Objects¶
Controls provide IControl.
>>> ctrl = browser.getControl('Text Control')
>>> ctrl
<Control name='text-value' type='text'>
>>> verifyObject(interfaces.IControl, ctrl)
True
They have several useful attributes:
the name as which the control is known to the form:
>>> ctrl.name
'text-value'
the value of the control, which may also be set:
>>> ctrl.value
'Some Text'
>>> ctrl.value = 'More Text'
>>> ctrl.value
'More Text'
the type of the control:
>>> ctrl.type
'text'
a flag describing whether the control is disabled:
>>> ctrl.disabled
False
and a flag to tell us whether the control can have multiple values:
>>> ctrl.multiple
False
Additionally, controllers for select, radio, and checkbox provide IListControl. These fields have four other attributes and an additional method:
>>> ctrl = browser.getControl('Multiple Select Control')
>>> ctrl
<ListControl name='multi-select-value' type='select'>
>>> ctrl.disabled
False
>>> ctrl.multiple
True
>>> verifyObject(interfaces.IListControl, ctrl)
True
‘options’ lists all available value options.
>>> ctrl.options
['1', '2', '3']
‘displayOptions’ lists all available options by label. The ‘label’ attribute on an option has precedence over its contents, which is why our last option is ‘Third’ in the display.
>>> ctrl.displayOptions
['Un', 'Deux', 'Third']
‘displayValue’ lets you get and set the displayed values of the control of the select box, rather than the actual values.
>>> ctrl.value
[]
>>> ctrl.displayValue
[]
>>> ctrl.displayValue = ['Un', 'Deux']
>>> ctrl.displayValue
['Un', 'Deux']
>>> ctrl.value
['1', '2']
>>> ctrl.displayValue = ['Quatre']
Traceback (most recent call last):
...
ItemNotFoundError: Quatre
‘controls’ gives you a list of the subcontrol objects in the control (subcontrols are discussed below).
>>> ctrl.controls
[<ItemControl name='multi-select-value' type='select' optionValue='1' selected=True>,
<ItemControl name='multi-select-value' type='select' optionValue='2' selected=True>,
<ItemControl name='multi-select-value' type='select' optionValue='3' selected=False>]
The ‘getControl’ method lets you get subcontrols by their label or their value.
>>> ctrl.getControl('Un')
<ItemControl name='multi-select-value' type='select' optionValue='1' selected=True>
>>> ctrl.getControl('Deux')
<ItemControl name='multi-select-value' type='select' optionValue='2' selected=True>
>>> ctrl.getControl('Trois') # label attribute
<ItemControl name='multi-select-value' type='select' optionValue='3' selected=False>
>>> ctrl.getControl('Third') # contents
<ItemControl name='multi-select-value' type='select' optionValue='3' selected=False>
>>> browser.getControl('Third') # ambiguous in the browser, so useful
Traceback (most recent call last):
...
AmbiguityError: label 'Third' matches:
<Item name='3' id=None contents='Tres' value='3' label='Third'>
<Item name='3' id=None contents='Trois' value='3' label='Third'>
<Item name='3' id='multi-checkbox-value-3' __label={'__text': 'Three\n '} checked='checked' name='multi-checkbox-value' type='checkbox' id='multi-checkbox-value-3' value='3'>
<Item name='3' id='radio-value-3' __label={'__text': ' Drei'} type='radio' name='radio-value' value='3' id='radio-value-3'>
Finally, submit controls provide ISubmitControl
, and image controls
provide IImageSubmitControl
, which extents ISubmitControl
. These
both simply add a ‘click’ method. For image submit controls, you may also
provide a coordinates argument, which is a tuple of (x, y). These submit
the forms, and are demonstrated below as we examine each control
individually.
ItemControl Objects¶
As introduced briefly above, using labels to obtain elements of a logical radio button or checkbox collection returns item controls, which are parents. Manipulating the value of these controls affects the parent control.
>>> browser.getControl(name='radio-value').value
['2']
>>> browser.getControl('Zwei').optionValue # read-only.
'2'
>>> browser.getControl('Zwei').selected
True
>>> verifyObject(interfaces.IItemControl, browser.getControl('Zwei'))
True
>>> browser.getControl('Ein').selected = True
>>> browser.getControl('Ein').selected
True
>>> browser.getControl('Zwei').selected
False
>>> browser.getControl(name='radio-value').value
['1']
>>> browser.getControl('Ein').selected = False
>>> browser.getControl(name='radio-value').value
[]
>>> browser.getControl('Zwei').selected = True
Checkbox collections behave similarly, as shown below.
Various Controls¶
The various types of controls are demonstrated here.
Text Control¶
The text control we already introduced above.
Password Control¶
>>> ctrl = browser.getControl('Password Control')
>>> ctrl
<Control name='password-value' type='password'>
>>> verifyObject(interfaces.IControl, ctrl)
True
>>> ctrl.value
'Password'
>>> ctrl.value = 'pass now'
>>> ctrl.value
'pass now'
>>> ctrl.disabled
False
>>> ctrl.multiple
False
Read Only Control¶
>>> ctrl = browser.getControl(name='readonly-value')
>>> ctrl
<Control name='readonly-value' type='text'>
>>> verifyObject(interfaces.IControl, ctrl)
True
>>> ctrl.value
'Read Only Text'
>>> ctrl.value = 'Overwrite'
Traceback (most recent call last):
...
AttributeError: Trying to set value of readonly control
>>> ctrl.readonly
True
>>> ctrl.multiple
False
Text Area Control¶
>>> ctrl = browser.getControl('Text Area Control')
>>> ctrl
<Control name='textarea-value' type='textarea'>
>>> verifyObject(interfaces.IControl, ctrl)
True
>>> ctrl.value
' Text inside\n area!\n '
>>> ctrl.value = 'A lot of\n text.'
>>> ctrl.disabled
False
>>> ctrl.multiple
False
File Control¶
File controls are used when a form has a file-upload field. To specify data, call the add_file method, passing:
A file-like object
a content type, and
a file name
>>> ctrl = browser.getControl('File Control')
>>> ctrl
<Control name='file-value' type='file'>
>>> verifyObject(interfaces.IControl, ctrl)
True
>>> ctrl.value is None
True
>>> import io
>>> ctrl.add_file(io.BytesIO(b'File contents'),
... 'text/plain', 'test.txt')
The file control (like the other controls) also knows if it is disabled
or if it can have multiple values.
>>> ctrl.disabled
False
>>> ctrl.multiple
False
Selection Control (Single-Valued)¶
>>> ctrl = browser.getControl('Single Select Control')
>>> ctrl
<ListControl name='single-select-value' type='select'>
>>> verifyObject(interfaces.IListControl, ctrl)
True
>>> ctrl.value
['1']
>>> ctrl.value = ['2']
>>> ctrl.disabled
False
>>> ctrl.multiple
False
>>> ctrl.options
['1', '2', '3']
>>> ctrl.displayOptions
['Uno', 'Dos', 'Third']
>>> ctrl.displayValue
['Dos']
>>> ctrl.displayValue = ['Tres']
>>> ctrl.displayValue
['Third']
>>> ctrl.displayValue = ['Dos']
>>> ctrl.displayValue
['Dos']
>>> ctrl.displayValue = ['Third']
>>> ctrl.displayValue
['Third']
>>> ctrl.value
['3']
>>> ctrl.displayValue = ['Quatre']
Traceback (most recent call last):
...
ItemNotFoundError: Quatre
>>> ctrl.displayValue = ['Uno', 'Dos']
Traceback (most recent call last):
...
ItemCountError: single selection list, must set sequence of length 0 or 1
Selection Control (Multi-Valued)¶
This was already demonstrated in the introduction to control objects above.
Checkbox Control (Single-Valued; Unvalued)¶
>>> ctrl = browser.getControl(name='single-unvalued-checkbox-value')
>>> ctrl
<ListControl name='single-unvalued-checkbox-value' type='checkbox'>
>>> verifyObject(interfaces.IListControl, ctrl)
True
>>> ctrl.value
True
>>> ctrl.value = False
>>> ctrl.disabled
False
>>> ctrl.multiple
True
>>> ctrl.options
[True]
>>> ctrl.displayOptions
['Single Unvalued Checkbox']
>>> ctrl.displayValue
[]
>>> verifyObject(
... interfaces.IItemControl,
... browser.getControl('Single Unvalued Checkbox'))
True
>>> browser.getControl('Single Unvalued Checkbox').optionValue
'on'
>>> browser.getControl('Single Unvalued Checkbox').selected
False
>>> ctrl.displayValue = ['Single Unvalued Checkbox']
>>> ctrl.displayValue
['Single Unvalued Checkbox']
>>> browser.getControl('Single Unvalued Checkbox').selected
True
>>> browser.getControl('Single Unvalued Checkbox').selected = False
>>> browser.getControl('Single Unvalued Checkbox').selected
False
>>> ctrl.displayValue
[]
>>> browser.getControl(
... name='single-disabled-unvalued-checkbox-value').disabled
True
>>> ctrl.displayValue = ['Nonsense']
Traceback (most recent call last):
...
ItemNotFoundError: Nonsense
Checkbox Control (Single-Valued, Valued)¶
>>> ctrl = browser.getControl(name='single-valued-checkbox-value')
>>> ctrl
<ListControl name='single-valued-checkbox-value' type='checkbox'>
>>> verifyObject(interfaces.IListControl, ctrl)
True
>>> ctrl.value
['1']
>>> ctrl.value = []
>>> ctrl.disabled
False
>>> ctrl.multiple
True
>>> ctrl.options
['1']
>>> ctrl.displayOptions
['Single Valued Checkbox']
>>> ctrl.displayValue
[]
>>> verifyObject(
... interfaces.IItemControl,
... browser.getControl('Single Valued Checkbox'))
True
>>> browser.getControl('Single Valued Checkbox').selected
False
>>> browser.getControl('Single Valued Checkbox').optionValue
'1'
>>> ctrl.displayValue = ['Single Valued Checkbox']
>>> ctrl.displayValue
['Single Valued Checkbox']
>>> browser.getControl('Single Valued Checkbox').selected
True
>>> browser.getControl('Single Valued Checkbox').selected = False
>>> browser.getControl('Single Valued Checkbox').selected
False
>>> ctrl.displayValue
[]
>>> ctrl.displayValue = ['Nonsense']
Traceback (most recent call last):
...
ItemNotFoundError: Nonsense
- Checkbox Control (Multi-Valued)
>>> ctrl = browser.getControl(name='multi-checkbox-value')
>>> ctrl
<ListControl name='multi-checkbox-value' type='checkbox'>
>>> verifyObject(interfaces.IListControl, ctrl)
True
>>> ctrl.value
['1', '3']
>>> ctrl.value = ['1', '2']
>>> ctrl.disabled
False
>>> ctrl.multiple
True
>>> ctrl.options
['1', '2', '3']
>>> ctrl.displayOptions
['One', 'Two', 'Three']
>>> ctrl.displayValue
['One', 'Two']
>>> ctrl.displayValue = ['Two']
>>> ctrl.value
['2']
>>> browser.getControl('Two').optionValue
'2'
>>> browser.getControl('Two').selected
True
>>> verifyObject(interfaces.IItemControl, browser.getControl('Two'))
True
>>> browser.getControl('Three').selected = True
>>> browser.getControl('Three').selected
True
>>> browser.getControl('Two').selected
True
>>> ctrl.value
['2', '3']
>>> browser.getControl('Two').selected = False
>>> ctrl.value
['3']
>>> browser.getControl('Three').selected = False
>>> ctrl.value
[]
>>> ctrl.displayValue = ['Four']
Traceback (most recent call last):
...
ItemNotFoundError: Four
Radio Control¶
This is how you get a radio button based control:
>>> ctrl = browser.getControl(name='radio-value')
This shows the existing value of the control, as it was in the HTML received from the server:
>>> ctrl.value
['2']
We can then unselect it:
>>> ctrl.value = []
>>> ctrl.value
[]
We can also reselect it:
>>> ctrl.value = ['2']
>>> ctrl.value
['2']
displayValue shows the text the user would see next to the control:
>>> ctrl.displayValue
['Zwei']
This is just unit testing:
>>> ctrl
<ListControl name='radio-value' type='radio'>
>>> verifyObject(interfaces.IListControl, ctrl)
True
>>> ctrl.disabled
False
>>> ctrl.multiple
False
>>> ctrl.options
['1', '2', '3']
>>> ctrl.displayOptions
['Ein', 'Zwei', 'Drei']
>>> ctrl.displayValue = ['Ein']
>>> ctrl.value
['1']
>>> ctrl.displayValue
['Ein']
>>> ctrl.displayValue = ['Vier']
Traceback (most recent call last):
...
ItemNotFoundError: Vier
>>> ctrl.displayValue = ['Ein', 'Zwei']
Traceback (most recent call last):
...
ItemCountError: single selection list, must set sequence of length 0 or 1
The radio control subcontrols were illustrated above.
Image Control¶
>>> ctrl = browser.getControl(name='image-value')
>>> ctrl
<ImageControl name='image-value' type='image'>
>>> verifyObject(interfaces.IImageSubmitControl, ctrl)
True
>>> ctrl.value
''
>>> ctrl.disabled
False
>>> ctrl.multiple
False
Submit Control¶
>>> ctrl = browser.getControl(name='submit-value')
>>> ctrl
<SubmitControl name='submit-value' type='submit'>
>>> browser.getControl('Submit This') # value of submit button is a label
<SubmitControl name='submit-value' type='submit'>
>>> browser.getControl('Standard Submit Control') # label tag is legal
<SubmitControl name='submit-value' type='submit'>
>>> browser.getControl('Submit') # multiple labels, but same control
<SubmitControl name='submit-value' type='submit'>
>>> verifyObject(interfaces.ISubmitControl, ctrl)
True
>>> ctrl.value
'Submit This'
>>> ctrl.disabled
False
>>> ctrl.multiple
False
Using Submitting Controls¶
Both the submit and image type should be clickable and submit the form:
>>> browser.getControl('Text Control').value = 'Other Text'
>>> browser.getControl('Submit').click()
>>> print(browser.contents)
<html>
...
<em>Other Text</em>
<input type="text" name="text-value" id="text-value" value="Some Text" />
...
<em>Submit This</em>
<input type="submit" name="submit-value" id="submit-value" value="Submit This" />
...
</html>
Note that if you click a submit object after the associated page has expired, you will get an error.
>>> browser.open('http://localhost/@@/testbrowser/controls.html')
>>> ctrl = browser.getControl('Submit')
>>> ctrl.click()
>>> ctrl.click()
Traceback (most recent call last):
...
ExpiredError
All the above also holds true for the image control:
>>> browser.open('http://localhost/@@/testbrowser/controls.html')
>>> browser.getControl('Text Control').value = 'Other Text'
>>> browser.getControl(name='image-value').click()
>>> print(browser.contents)
<html>
...
<em>Other Text</em>
<input type="text" name="text-value" id="text-value" value="Some Text" />
...
<em>1</em>
<em>1</em>
<input type="image" name="image-value" id="image-value"
src="zope3logo.gif" />
...
</html>
>>> browser.open('http://localhost/@@/testbrowser/controls.html')
>>> ctrl = browser.getControl(name='image-value')
>>> ctrl.click()
>>> ctrl.click()
Traceback (most recent call last):
...
ExpiredError
But when sending an image, you can also specify the coordinate you clicked:
>>> browser.open('http://localhost/@@/testbrowser/controls.html')
>>> browser.getControl(name='image-value').click((50,25))
>>> print(browser.contents)
<html>
...
<em>50</em>
<em>25</em>
<input type="image" name="image-value" id="image-value"
src="zope3logo.gif" />
...
</html>
Pages Without Controls¶
What would happen if we tried to look up a control on a page that has none?
>>> browser.open('http://localhost/@@/testbrowser/simple.html')
>>> browser.getControl('anything')
Traceback (most recent call last):
...
LookupError: label 'anything'
(there are no form items in the HTML)
Forms¶
Because pages can have multiple forms with like-named controls, it is sometimes necessary to access forms by name or id. The browser’s forms attribute can be used to do so. The key value is the form’s name or id. If more than one form has the same name or id, the first one will be returned.
>>> browser.open('http://localhost/@@/testbrowser/forms.html')
>>> form = browser.getForm(name='one')
Form instances conform to the IForm interface.
>>> verifyObject(interfaces.IForm, form)
True
The form exposes several attributes related to forms:
The name of the form:
>>> form.name
'one'
The id of the form:
>>> form.id
'1'
The action (target URL) when the form is submitted:
>>> form.action
'http://localhost/@@/testbrowser/forms.html'
The method (HTTP verb) used to transmit the form data:
>>> form.method
'GET'
Besides those attributes, you have also a couple of methods. Like for the browser, you can get control objects, but limited to the current form…
>>> form.getControl(name='text-value')
<Control name='text-value' type='text'>
…and submit the form.
>>> form.submit('Submit')
>>> print(browser.contents)
<html>
...
<em>First Text</em>
...
</html>
Submitting also works without specifying a control, as shown below, which is it’s primary reason for existing in competition with the control submission discussed above.
Now let me show you briefly that looking up forms is sometimes important. In the forms.html template, we have four forms all having a text control named text-value. Now, if I use the browser’s get method,
>>> browser.getControl(name='text-value')
Traceback (most recent call last):
...
AmbiguityError: name 'text-value' matches:
<TextControl(text-value=First Text)>
<TextControl(text-value=Second Text)>
<TextControl(text-value=Third Text)>
<TextControl(text-value=Fourth Text)>
>>> browser.getControl('Text Control')
Traceback (most recent call last):
...
AmbiguityError: label 'Text Control' matches:
<TextControl(text-value=Third Text)>
<TextControl(text-value=Fourth Text)>
I’ll always get an ambiguous form field. I can use the index argument, or with the getForm method I can disambiguate by searching only within a given form:
>>> form = browser.getForm('2')
>>> form.getControl(name='text-value').value
'Second Text'
>>> form.submit('Submit')
>>> browser.contents
'...<em>Second Text</em>...'
>>> form = browser.getForm('2')
>>> form.getControl('Submit').click()
>>> browser.contents
'...<em>Second Text</em>...'
>>> browser.getForm('3').getControl('Text Control').value
'Third Text'
The last form on the page does not have a name, an id, or a submit button. Working with it is still easy, thanks to a index attribute that guarantees order. (Forms without submit buttons are sometimes useful for JavaScript.)
>>> form = browser.getForm(index=3)
>>> form.submit()
>>> browser.contents
'...<em>Fourth Text</em>...<em>Submitted without the submit button.</em>...'
If a form is requested that does not exists, an exception will be raised.
>>> form = browser.getForm('does-not-exist')
Traceback (most recent call last):
LookupError
If the HTML page contains only one form, no arguments to getForm are needed:
>>> oneform = Browser(wsgi_app=wsgi_app)
>>> oneform.open('http://localhost/@@/testbrowser/oneform.html')
>>> form = oneform.getForm()
If the HTML page contains more than one form, index is needed to disambiguate if no other arguments are provided:
>>> browser.getForm()
Traceback (most recent call last):
ValueError: if no other arguments are given, index is required.
Submitting a posts body directly¶
In addition to the open method, Browser has a post
method that allows a request body to be supplied. This method is particularly
helpful when testing AJAX methods.
Let’s visit a page that echos some interesting values from it’s request:
>>> browser.open('http://localhost/echo.html')
>>> print(browser.contents)
HTTP_ACCEPT_LANGUAGE: en-US
HTTP_CONNECTION: close
HTTP_HOST: localhost
HTTP_USER_AGENT: Python-urllib/2.4
PATH_INFO: /echo.html
REQUEST_METHOD: GET
Body: ''
Now, we’ll try a post. The post method takes a URL, a data string, and an optional content type. If we just pass a string, then a URL-encoded query string is assumed:
>>> browser.post('http://localhost/echo.html', 'x=1&y=2')
>>> print(browser.contents)
CONTENT_LENGTH: 7
CONTENT_TYPE: application/x-www-form-urlencoded
HTTP_ACCEPT_LANGUAGE: en-US
HTTP_CONNECTION: close
HTTP_HOST: localhost
HTTP_USER_AGENT: Python-urllib/2.4
PATH_INFO: /echo.html
REQUEST_METHOD: POST
x: 1
y: 2
Body: ''
The body is empty because it is consumed to get form data.
We can pass a content-type explicitly:
>>> browser.post('http://localhost/echo.html',
... '{"x":1,"y":2}', 'application/x-javascript')
>>> print(browser.contents)
CONTENT_LENGTH: 13
CONTENT_TYPE: application/x-javascript
HTTP_ACCEPT_LANGUAGE: en-US
HTTP_CONNECTION: close
HTTP_HOST: localhost
HTTP_USER_AGENT: Python-urllib/2.4
PATH_INFO: /echo.html
REQUEST_METHOD: POST
Body: '{"x":1,"y":2}'
Here, the body is left in place because it isn’t form data.
Performance Testing¶
Browser objects keep up with how much time each request takes. This can be used to ensure a particular request’s performance is within a tolerable range. Be very careful using raw seconds, cross-machine differences can be huge.
>>> browser.open('http://localhost/@@/testbrowser/simple.html')
>>> browser.lastRequestSeconds < 10 # really big number for safety
True
Handling Errors¶
Often WSGI middleware or the application itself gracefully handle application errors, such as invalid URLs:
Caution: Because of https://github.com/python/cpython/issues/90113 we currently are not able to demonstrate this feature here as it breaks on Python 3.11.
>>> # Work around https://github.com/python/cpython/issues/90113
>>> browser.raiseHttpErrors = False
>>> # Without the workaround we would see a traceback for the next call:
>>> browser.open('http://localhost/invalid')
>>> browser.headers['status']
'404 Not Found'
>>> # Reset work around:
>>> browser.raiseHttpErrors = True
Note that the above error was thrown by mechanize
and not by the
application. For debugging purposes, however, it can be very useful to see the
original exception caused by the application. In those cases you can set the
handleErrors
property of the browser to False
. It is defaulted to
True
:
>>> browser.handleErrors
True
So when we tell the application not to handle the errors,
>>> browser.handleErrors = False
we get a different, internal error from the application:
>>> browser.open('http://localhost/invalid')
Traceback (most recent call last):
...
NotFound: /invalid
Note
Setting the handleErrors
attribute to False will only change
anything if the WSGI application obeys the wsgi.handleErrors
or
paste.throw_errors
WSGI environment variables. i.e. it does not
catch and handle the original exception when these are set appropriately.
When the testbrowser is raising HttpErrors, the errors still hit the test. Sometimes we don’t want that to happen, in situations where there are edge cases that will cause the error to be predictably but infrequently raised. Time is a primary cause of this.
To get around this, one can set the raiseHttpErrors to False.
>>> browser.handleErrors = True
>>> browser.raiseHttpErrors = False
This will cause HttpErrors not to propagate.
>>> browser.open('http://localhost/invalid')
The headers are still there, though.
>>> '404 Not Found' in str(browser.headers)
True
If we don’t handle the errors, and allow internal ones to propagate, however, this flag doesn’t affect things.
>>> browser.handleErrors = False
>>> browser.open('http://localhost/invalid')
Traceback (most recent call last):
...
NotFound: /invalid
>>> browser.raiseHttpErrors = True
Hand-Holding¶
Instances of the various objects ensure that users don’t set incorrect instance attributes accidentally.
>>> browser.nonexistant = None
Traceback (most recent call last):
...
AttributeError: 'Browser' object has no attribute 'nonexistant'
>>> form.nonexistant = None
Traceback (most recent call last):
...
AttributeError: 'Form' object has no attribute 'nonexistant'
>>> control.nonexistant = None
Traceback (most recent call last):
...
AttributeError: 'Control' object has no attribute 'nonexistant'
>>> link.nonexistant = None
Traceback (most recent call last):
...
AttributeError: 'Link' object has no attribute 'nonexistant'
HTTPS support¶
Depending on the scheme of the request the variable wsgi.url_scheme will be set correctly on the request:
>>> browser.open('http://localhost/echo_one.html?var=wsgi.url_scheme')
>>> print(browser.contents)
'http'
>>> browser.open('https://localhost/echo_one.html?var=wsgi.url_scheme')
>>> print(browser.contents)
'https'
see http://www.python.org/dev/peps/pep-3333/ for details.
zope.testbrowser
API¶
zope.testbrowser.interfaces
¶
Browser-like functional doctest interfaces
Interfaces¶
- interface zope.testbrowser.interfaces.ICookies[source]¶
Extends:
zope.interface.common.mapping.IExtendedReadMapping
,zope.interface.common.mapping.IExtendedWriteMapping
,zope.interface.common.mapping.IMapping
A mapping of cookies for a given url
- change(name, value=None, domain=None, expires=None, path=None, secure=None, comment=None, commenturl=None, port=None)¶
Change an attribute of an existing cookie.
If cookie does not exist, raises a KeyError.
- clearAll()¶
Clear all cookies for the associated browser, irrespective of URL
- clearAllSession()¶
Clear session cookies for associated browser, irrespective of URL
- create(name, value, domain=None, expires=None, path=None, secure=None, comment=None, commenturl=None, port=None)¶
Create a new cookie with the given values.
If cookie of the same name, domain, and path exists, raises a ValueError.
Expires is a string or a datetime.datetime. timezone-naive datetimes are interpreted as in UTC. If expires is before now, raises AlreadyExpiredError.
If the domain or path do not generally match the current URL, raises ValueError.
- forURL(url)¶
Returns another ICookies instance for the given URL.
- getinfo(name)¶
returns dict of settings for the given cookie name.
This includes only the following cookie values:
name (str)
value (str),
port (int or None),
domain (str),
path (str or None),
secure (bool), and
expires (datetime.datetime with pytz.UTC timezone or None),
comment (str or None),
commenturl (str or None).
(Method name is not camelCase because it is intended to feel like an extension to the mapping interface, which uses all lower case, e.g. iterkeys.)
- header¶
Header
The current value for the Cookie header for the URL
- Implementation
zope.schema.TextLine
- Read Only
False
- Required
True
- Default Value
None
- Allowed Type
- iterinfo(name=None)¶
iterate over the information about all the cookies for the URL.
Each result is a dictionary as described for
getinfo
.If name is given, iterates over all cookies for given name.
(Method name is not camelCase because it is intended to feel like an extension to the mapping interface, which uses all lower case, e.g. iterkeys.)
- interface zope.testbrowser.interfaces.IBrowser[source]¶
A Programmatic Web Browser.
- addHeader(key, value)¶
Adds a header to each HTTP request.
Adding additional headers can be useful in many ways, from setting the credentials token to specifying the browser identification string.
- contents¶
Contents
The complete response body of the HTTP request.
- Implementation
zope.schema.Text
- Read Only
False
- Required
True
- Default Value
None
- Allowed Type
- cookies¶
Cookies
An ICookies mapping for the browser’s current URL.
- Implementation
zope.schema.Field
- Read Only
False
- Required
True
- Default Value
None
- followRedirects¶
Follow Redirects
Describes whether the browser follows redirects. If set to
True
, it will automatically issueGET
requests for redirect responses; if set toFalse
, it will return redirect responses directly, allowing the caller to make assertions about them.
- Implementation
zope.schema.Bool
- Read Only
False
- Required
True
- Default Value
True
- Allowed Type
- getControl(label=None, name=None, index=None)¶
Get a control from the page.
Only one of
label
andname
may be provided.label
searches form labels (including submit button values, per the HTML 4.0 spec), andname
searches form field names.Label value is searched as case-sensitive whole words within the labels for each control–that is, a search for ‘Add’ will match ‘Add a contact’ but not ‘Address’. A word is defined as one or more alphanumeric characters or the underline.
If no values are found, the code raises a LookupError.
If
index
is None (the default) and more than one field matches the search, the code raises an AmbiguityError. If an index is provided, it is used to choose the index from the ambiguous choices. If the index does not exist, the code raises a LookupError.
- getForm(id=None, name=None, action=None, index=None)¶
Get a form from the page.
Zero or one of
id
,name
, andaction
may be provided. If none are provided the index alone is used to determine the return value.If no values are found, the code raises a LookupError.
If
index
is None (the default) and more than one form matches the search, the code raises an AmbiguityError. If an index is provided, it is used to choose the index from the ambiguous choices. If the index does not exist, the code raises a LookupError.
- getLink(text=None, url=None, id=None, index=0)¶
Return an ILink from the page.
The link is found by the arguments of the method. One or more may be used together.
- o
text
– A regular expression trying to match the link’s text,in other words everything between <a> and </a> or the value of the submit button.
- o
url
– The URL the link is going to. This is either the
href
attribute of an anchor tag or the action of a form.o
id
– The id attribute of the anchor tag submit button.
- o
index
– When there’s more than one link that matches thetext/URL, you can specify which one you want.
- goBack(count=1)¶
Go back in history by a certain amount of visisted pages.
The
count
argument specifies how far to go back. It is set to 1 by default.
- handleErrors¶
Handle Errors
Describes whether server-side errors will be handled by the publisher. If set to
False
, the error will progress all the way to the test, which is good for debugging.
- Implementation
zope.schema.Bool
- Read Only
False
- Required
True
- Default Value
True
- Allowed Type
- headers¶
Headers
Headers of the HTTP response; a
httplib.HTTPMessage
.
- Implementation
zope.schema.Field
- Read Only
False
- Required
True
- Default Value
None
- isHtml¶
Is HTML
Tells whether the output is HTML or not.
- Implementation
zope.schema.Bool
- Read Only
False
- Required
True
- Default Value
None
- Allowed Type
- lastRequestSeconds¶
Seconds to Process Last Request
Return how many seconds (or fractions) the last request took.
The values returned have the same resolution as the results from
time.clock
.
- Implementation
zope.schema.Field
- Read Only
True
- Required
True
- Default Value
None
- open(url, data=None)¶
Open a URL in the browser.
The URL must be fully qualified. However, note that the server name and port is arbitrary for Zope 3 functional tests, since the request is sent to the publisher directly.
The
data
argument describes the data that will be sent as the body of the request.
- reload()¶
Reload the current page.
Like a browser reload, if the past request included a form submission, the form data will be resubmitted.
- title¶
Title
Title of the displayed page
- Implementation
zope.schema.TextLine
- Read Only
False
- Required
False
- Default Value
None
- Allowed Type
- interface zope.testbrowser.interfaces.ILink[source]¶
- attrs¶
Attributes
The attributes of the link tag
- Implementation
zope.schema.Dict
- Read Only
False
- Required
False
- Default Value
None
- Allowed Type
- click()¶
click the link, going to the URL referenced
- tag¶
Tag
The tag name of the link (a or area, typically)
- Implementation
zope.schema.TextLine
- Read Only
False
- Required
True
- Default Value
None
- Allowed Type
- text¶
Text
The contained text of the link
- Implementation
zope.schema.TextLine
- Read Only
False
- Required
False
- Default Value
None
- Allowed Type
- interface zope.testbrowser.interfaces.IForm[source]¶
An HTML form of the page.
- action¶
Action
The action (or URI) that is opened upon submittance.
- Implementation
zope.schema.TextLine
- Read Only
False
- Required
True
- Default Value
None
- Allowed Type
- enctype¶
Encoding Type
The type of encoding used to encode the form data.
- Implementation
zope.schema.TextLine
- Read Only
False
- Required
True
- Default Value
None
- Allowed Type
- getControl(label=None, name=None, index=None)¶
Get a control in the page.
Only one of
label
andname
may be provided.label
searches form labels (including submit button values, per the HTML 4.0 spec), andname
searches form field names.Label value is searched as case-sensitive whole words within the labels for each control–that is, a search for ‘Add’ will match ‘Add a contact’ but not ‘Address’. A word is defined as one or more alphanumeric characters or the underline.
If no values are found, the code raises a LookupError.
If
index
is None (the default) and more than one field matches the search, the code raises an AmbiguityError. If an index is provided, it is used to choose the index from the ambiguous choices. If the index does not exist, the code raises a LookupError.
- id¶
Id
The value of the id attribute in the form tag, if specified.
- Implementation
zope.schema.TextLine
- Read Only
False
- Required
True
- Default Value
None
- Allowed Type
- method¶
Method
The method used to submit the form.
- Implementation
zope.schema.Choice
- Read Only
False
- Required
True
- Default Value
None
- name¶
Name
The value of the name attribute in the form tag, if specified.
- Implementation
zope.schema.TextLine
- Read Only
False
- Required
True
- Default Value
None
- Allowed Type
- submit(label=None, name=None, index=None, coord=(1, 1))¶
Submit this form.
The label, name, and index arguments select the submit button to use to submit the form. You may label or name, with index to disambiguate.
Label value is searched as case-sensitive whole words within the labels for each control–that is, a search for ‘Add’ will match ‘Add a contact’ but not ‘Address’. A word is defined as one or more alphanumeric characters or the underline.
The control code works identically to ‘get’ except that searches are filtered to find only submit and image controls.
- interface zope.testbrowser.interfaces.IControl[source]¶
A control (input field) of a page.
- clear()¶
Clear the value of the control.
- disabled¶
Disabled
Describes whether a control is disabled.
- Implementation
zope.schema.Bool
- Read Only
False
- Required
False
- Default Value
False
- Allowed Type
- multiple¶
Multiple
Describes whether this control can hold multiple values.
- Implementation
zope.schema.Bool
- Read Only
False
- Required
False
- Default Value
False
- Allowed Type
- name¶
Name
The name of the control.
- Implementation
zope.schema.TextLine
- Read Only
False
- Required
True
- Default Value
None
- Allowed Type
- type¶
Type
The type of the control
- Implementation
zope.schema.Choice
- Read Only
False
- Required
True
- Default Value
None
- value¶
Value
The value of the control
- Implementation
zope.schema.Field
- Read Only
False
- Required
True
- Default Value
None
- interface zope.testbrowser.interfaces.IListControl[source]¶
Extends:
zope.testbrowser.interfaces.IControl
A radio button, checkbox, or select control
- controls¶
a list of subcontrols for the control. mutating list has no effect on control (although subcontrols may be changed as usual).
- displayOptions¶
Options
A list of possible display values for the control.
- Implementation
zope.schema.List
- Read Only
False
- Required
True
- Default Value
None
- Allowed Type
- displayValue¶
Value
The value of the control, as rendered by the display
- Implementation
zope.schema.Field
- Read Only
False
- Required
True
- Default Value
None
- getControl(label=None, value=None, index=None)¶
return subcontrol for given label or value, disambiguated by index if given. Label value is searched as case-sensitive whole words within the labels for each item–that is, a search for ‘Add’ will match ‘Add a contact’ but not ‘Address’. A word is defined as one or more alphanumeric characters or the underline.
- interface zope.testbrowser.interfaces.ISubmitControl[source]¶
Extends:
zope.testbrowser.interfaces.IControl
- click()¶
click the submit button
- interface zope.testbrowser.interfaces.IImageSubmitControl[source]¶
Extends:
zope.testbrowser.interfaces.ISubmitControl
- click(coord=(1, 1))¶
click the submit button with optional coordinates
- interface zope.testbrowser.interfaces.IItemControl[source]¶
a radio button or checkbox within a larger multiple-choice control
- control¶
Control
The parent control element.
- Implementation
zope.schema.Object
- Read Only
False
- Required
True
- Default Value
None
- Must Provide
- disabled¶
Disabled
Describes whether a subcontrol is disabled.
- Implementation
zope.schema.Bool
- Read Only
False
- Required
False
- Default Value
False
- Allowed Type
- optionValue¶
Value
The value of the subcontrol
- Implementation
zope.schema.TextLine
- Read Only
False
- Required
False
- Default Value
None
- Allowed Type
Exceptions¶
zope.testbrowser.browser
¶
Webtest-based Functional Doctest interfaces
Classes¶
- class zope.testbrowser.browser.Browser(url=None, wsgi_app=None)[source]¶
A web user agent.
- property contents¶
See zope.testbrowser.interfaces.IBrowser
- getForm(id=None, name=None, action=None, index=None)[source]¶
See zope.testbrowser.interfaces.IBrowser
- property headers¶
See zope.testbrowser.interfaces.IBrowser
- property isHtml¶
See zope.testbrowser.interfaces.IBrowser
- property lastRequestSeconds¶
See zope.testbrowser.interfaces.IBrowser
- property title¶
See zope.testbrowser.interfaces.IBrowser
- property url¶
See zope.testbrowser.interfaces.IBrowser