/usr/lib/python3/dist-packages/pytest_bdd-2.18.2.egg-info/PKG-INFO is in python3-pytest-bdd 2.18.2-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 | Metadata-Version: 1.1
Name: pytest-bdd
Version: 2.18.2
Summary: BDD for pytest
Home-page: https://github.com/pytest-dev/pytest-bdd
Author: Oleg Pidsadnyi, Anatoly Bubenkov and others
Author-email: oleg.pidsadnyi@gmail.com
License: MIT license
Description: BDD library for the py.test runner
==================================
.. image:: http://img.shields.io/pypi/v/pytest-bdd.svg
:target: https://pypi.python.org/pypi/pytest-bdd
.. image:: http://img.shields.io/coveralls/pytest-dev/pytest-bdd/master.svg
:target: https://coveralls.io/r/pytest-dev/pytest-bdd
.. image:: https://travis-ci.org/pytest-dev/pytest-bdd.svg?branch=master
:target: https://travis-ci.org/pytest-dev/pytest-bdd
.. image:: https://readthedocs.org/projects/pytest-bdd/badge/?version=latest
:target: https://readthedocs.org/projects/pytest-bdd/?badge=latest
:alt: Documentation Status
pytest-bdd implements a subset of Gherkin language for the automation of the project
requirements testing and easier behavioral driven development.
Unlike many other BDD tools it doesn't require a separate runner and benefits from
the power and flexibility of the pytest. It allows to unify your unit and functional
tests, easier continuous integration server configuration and maximal reuse of the
tests setup.
Pytest fixtures written for the unit tests can be reused for the setup and actions
mentioned in the feature steps with dependency injection, which allows a true BDD
just-enough specification of the requirements without maintaining any context object
containing the side effects of the Gherkin imperative declarations.
.. _behave: https://pypi.python.org/pypi/behave
.. _pytest-splinter: https://github.com/pytest-dev/pytest-splinter
Install pytest-bdd
------------------
::
pip install pytest-bdd
Example
-------
An example test for a blog hosting software could look like this.
Note that pytest-splinter_ is used to get the browser fixture.
publish_article.feature:
.. code-block:: gherkin
Feature: Blog
A site where you can publish your articles.
Scenario: Publishing the article
Given I'm an author user
And I have an article
When I go to the article page
And I press the publish button
Then I should not see the error message
And the article should be published # Note: will query the database
Note that only one feature is allowed per feature file.
test_publish_article.py:
.. code-block:: python
from pytest_bdd import scenario, given, when, then
@scenario('publish_article.feature', 'Publishing the article')
def test_publish():
pass
@given("I'm an author user")
def author_user(auth, author):
auth['user'] = author.user
@given('I have an article')
def article(author):
return create_test_article(author=author)
@when('I go to the article page')
def go_to_article(article, browser):
browser.visit(urljoin(browser.url, '/manage/articles/{0}/'.format(article.id)))
@when('I press the publish button')
def publish_article(browser):
browser.find_by_css('button[name=publish]').first.click()
@then('I should not see the error message')
def no_error_message(browser):
with pytest.raises(ElementDoesNotExist):
browser.find_by_css('.message.error').first
@then('the article should be published')
def article_is_published(article):
article.refresh() # Refresh the object in the SQLAlchemy session
assert article.is_published
Scenario decorator
------------------
Scenario decorator can accept such optional keyword arguments:
* ``encoding`` - decode content of feature file in specific encoding. UTF-8 is default.
* ``example_converters`` - mapping to pass functions to convert example values provided in feature files.
Function decorated with `scenario` decorator behaves like a normal test function,
which will be executed after all scenario steps.
You can consider it as a normal pytest test function, e.g. order fixtures there,
call other functions and make assertions:
.. code-block:: python
from pytest_bdd import scenario, given, when, then
@scenario('publish_article.feature', 'Publishing the article')
def test_publish(browser):
assert article.title in browser.html
Step aliases
------------
Sometimes it is needed to declare the same fixtures or steps with the
different names for better readability. In order to use the same step
function with multiple step names simply decorate it multiple times:
.. code-block:: python
@given('I have an article')
@given('there\'s an article')
def article(author):
return create_test_article(author=author)
Note that the given step aliases are independent and will be executed
when mentioned.
For example if you associate your resource to some owner or not. Admin
user can’t be an author of the article, but articles should have a
default author.
.. code-block:: gherkin
Scenario: I'm the author
Given I'm an author
And I have an article
Scenario: I'm the admin
Given I'm the admin
And there is an article
Given step scope
----------------
If you need your given step to be executed less than once per scenario (for example: once for module, session), you can
pass optional ``scope`` argument:
.. code-block:: python
@given('I have an article', scope='session')
def article(author):
return create_test_article(author=author)
.. code-block:: gherkin
Scenario: I'm the author
Given I'm an author
And I have an article
Scenario: I'm the admin
Given I'm the admin
And there is an article
For this example, step function for 'I have an article' given step will be executed once even though there are 2
scenarios using it.
Note that for other step types, it makes no sense to have scope larger than 'function' (the default) as they represent
an action (when step), and assertion (then step).
Step arguments
--------------
Often it's possible to reuse steps giving them a parameter(s).
This allows to have single implementation and multiple use, so less code.
Also opens the possibility to use same step twice in single scenario and with different arguments!
And even more, there are several types of step parameter parsers at your disposal
(idea taken from behave_ implementation):
.. _pypi_parse: http://pypi.python.org/pypi/parse
.. _pypi_parse_type: http://pypi.python.org/pypi/parse_type
**string** (the default)
This is the default and can be considered as a `null` or `exact` parser. It parses no parameters
and matches the step name by equality of strings.
**parse** (based on: pypi_parse_)
Provides a simple parser that replaces regular expressions for
step parameters with a readable syntax like ``{param:Type}``.
The syntax is inspired by the Python builtin ``string.format()``
function.
Step parameters must use the named fields syntax of pypi_parse_
in step definitions. The named fields are extracted,
optionally type converted and then used as step function arguments.
Supports type conversions by using type converters passed via `extra_types`
**cfparse** (extends: pypi_parse_, based on: pypi_parse_type_)
Provides an extended parser with "Cardinality Field" (CF) support.
Automatically creates missing type converters for related cardinality
as long as a type converter for cardinality=1 is provided.
Supports parse expressions like:
* ``{values:Type+}`` (cardinality=1..N, many)
* ``{values:Type*}`` (cardinality=0..N, many0)
* ``{value:Type?}`` (cardinality=0..1, optional)
Supports type conversions (as above).
**re**
This uses full regular expressions to parse the clause text. You will
need to use named groups "(?P<name>...)" to define the variables pulled
from the text and passed to your ``step()`` function.
Type conversion can only be done via `converters` step decorator argument (see example below).
The default parser is `string`, so just plain one-to-one match to the keyword definition.
Parsers except `string`, as well as their optional arguments are specified like:
for `cfparse` parser
.. code-block:: python
from pytest_bdd import parsers
@given(parsers.cfparse('there are {start:Number} cucumbers', extra_types=dict(Number=int)))
def start_cucumbers(start):
return dict(start=start, eat=0)
for `re` parser
.. code-block:: python
from pytest_bdd import parsers
@given(parsers.re(r'there are (?P<start>\d+) cucumbers'), converters=dict(start=int))
def start_cucumbers(start):
return dict(start=start, eat=0)
Example:
.. code-block:: gherkin
Scenario: Arguments for given, when, thens
Given there are 5 cucumbers
When I eat 3 cucumbers
And I eat 2 cucumbers
Then I should have 0 cucumbers
The code will look like:
.. code-block:: python
import re
from pytest_bdd import scenario, given, when, then, parsers
@scenario('arguments.feature', 'Arguments for given, when, thens')
def test_arguments():
pass
@given(parsers.parse('there are {start:d} cucumbers'))
def start_cucumbers(start):
return dict(start=start, eat=0)
@when(parsers.parse('I eat {eat:d} cucumbers'))
def eat_cucumbers(start_cucumbers, eat):
start_cucumbers['eat'] += eat
@then(parsers.parse('I should have {left:d} cucumbers'))
def should_have_left_cucumbers(start_cucumbers, start, left):
assert start_cucumbers['start'] == start
assert start - start_cucumbers['eat'] == left
Example code also shows possibility to pass argument converters which may be useful if you need to postprocess step
arguments after the parser.
You can implement your own step parser. It's interface is quite simple. The code can looks like:
.. code-block:: python
import re
from pytest_bdd import given, parsers
class MyParser(parsers.StepParser):
"""Custom parser."""
def __init__(self, name, **kwargs):
"""Compile regex."""
super(re, self).__init__(name)
self.regex = re.compile(re.sub('%(.+)%', '(?P<\1>.+)', self.name), **kwargs)
def parse_arguments(self, name):
"""Get step arguments.
:return: `dict` of step arguments
"""
return self.regex.match(name).groupdict()
def is_matching(self, name):
"""Match given name with the step name."""
return bool(self.regex.match(name))
@given(parsers.parse('there are %start% cucumbers'))
def start_cucumbers(start):
return dict(start=start, eat=0)
Step arguments are fixtures as well!
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Step arguments are injected into pytest `request` context as normal fixtures with the names equal to the names of the
arguments. This opens a number of possibilies:
* you can access step's argument as a fixture in other step function just by mentioning it as an argument (just like any othe pytest fixture)
* if the name of the step argument clashes with existing fixture, it will be overridden by step's argument value; this way you can set/override the value for some fixture deeply inside of the fixture tree in a ad-hoc way by just choosing the proper name for the step argument.
Override fixtures via given steps
---------------------------------
Dependency injection is not a panacea if you have complex structure of your test setup data. Sometimes there's a need
such a given step which would imperatively change the fixture only for certain test (scenario), while for other tests
it will stay untouched. To allow this, special parameter `target_fixture` exists in the `given` decorator:
.. code-block:: python
from pytest_bdd import given
@pytest.fixture
def foo():
return "foo"
@given("I have injecting given", target_fixture="foo")
def injecting_given():
return "injected foo"
@then('foo should be "injected foo"')
def foo_is_foo(foo):
assert foo == 'injected foo'
.. code-block:: gherkin
Scenario: Test given fixture injection
Given I have injecting given
Then foo should be "injected foo"
In this example existing fixture `foo` will be overridden by given step `I have injecting given` only for scenario it's
used in.
Multiline steps
---------------
As Gherkin, pytest-bdd supports multiline steps
(aka `PyStrings <http://docs.behat.org/guides/1.gherkin.html#pystrings>`_).
But in much cleaner and powerful way:
.. code-block:: gherkin
Scenario: Multiline step using sub indentation
Given I have a step with:
Some
Extra
Lines
Then the text should be parsed with correct indentation
Step is considered as multiline one, if the **next** line(s) after it's first line, is indented relatively
to the first line. The step name is then simply extended by adding futher lines with newlines.
In the example above, the Given step name will be:
.. code-block:: python
'I have a step with:\nSome\nExtra\nLines'
You can of course register step using full name (including the newlines), but it seems more practical to use
step arguments and capture lines after first line (or some subset of them) into the argument:
.. code-block:: python
import re
from pytest_bdd import given, then, scenario
@scenario(
'multiline.feature',
'Multiline step using sub indentation',
)
def test_multiline():
pass
@given(parsers.parse('I have a step with:\n{text}'))
def i_have_text(text):
return text
@then('the text should be parsed with correct indentation')
def text_should_be_correct(i_have_text, text):
assert i_have_text == text == 'Some\nExtra\nLines'
Note that `then` step definition (`text_should_be_correct`) in this example uses `text` fixture which is provided
by a a `given` step (`i_have_text`) argument with the same name (`text`). This possibility is described in
the `Step arguments are fixtures as well!`_ section.
Scenarios shortcut
------------------
If you have relatively large set of feature files, it's boring to manually bind scenarios to the tests using the
scenario decorator. Of course with the manual approach you get all the power to be able to additionally parametrize
the test, give the test function a nice name, document it, etc, but in the majority of the cases you don't need that.
Instead you want to bind `all` scenarios found in the `feature` folder(s) recursively automatically.
For this - there's a `scenarios` helper.
.. code-block:: python
from pytest_bdd import scenarios
# assume 'features' subfolder is in this file's directory
scenarios('features')
That's all you need to do to bind all scenarios found in the `features` folder!
Note that you can pass multiple paths, and those paths can be either feature files or feature folders.
.. code-block:: python
from pytest_bdd import scenarios
# pass multiple paths/files
scenarios('features', 'other_features/some.feature', 'some_other_features')
But what if you need to manually bind certain scenario, leaving others to be automatically bound?
Just write your scenario in a `normal` way, but ensure you do it `BEFORE` the call of `scenarios` helper.
.. code-block:: python
from pytest_bdd import scenario, scenarios
@scenario('features/some.feature', 'Test something')
def test_something():
pass
# assume 'features' subfolder is in this file's directory
scenarios('features')
In the example above `test_something` scenario binding will be kept manual, other scenarios found in the `features`
folder will be bound automatically.
Scenario outlines
-----------------
Scenarios can be parametrized to cover few cases. In Gherkin the variable
templates are written using corner braces as <somevalue>.
`Gherkin scenario outlines <http://docs.behat.org/guides/1.gherkin.html#scenario-outlines>`_ are supported by pytest-bdd
exactly as it's described in be behave_ docs.
Example:
.. code-block:: gherkin
Scenario Outline: Outlined given, when, thens
Given there are <start> cucumbers
When I eat <eat> cucumbers
Then I should have <left> cucumbers
Examples:
| start | eat | left |
| 12 | 5 | 7 |
pytest-bdd feature file format also supports example tables in different way:
.. code-block:: gherkin
Scenario Outline: Outlined given, when, thens
Given there are <start> cucumbers
When I eat <eat> cucumbers
Then I should have <left> cucumbers
Examples: Vertical
| start | 12 | 2 |
| eat | 5 | 1 |
| left | 7 | 1 |
This form allows to have tables with lots of columns keeping the maximum text width predictable without significant
readability change.
The code will look like:
.. code-block:: python
from pytest_bdd import given, when, then, scenario
@scenario(
'outline.feature',
'Outlined given, when, thens',
example_converters=dict(start=int, eat=float, left=str)
)
def test_outlined():
pass
@given('there are <start> cucumbers')
def start_cucumbers(start):
assert isinstance(start, int)
return dict(start=start)
@when('I eat <eat> cucumbers')
def eat_cucumbers(start_cucumbers, eat):
assert isinstance(eat, float)
start_cucumbers['eat'] = eat
@then('I should have <left> cucumbers')
def should_have_left_cucumbers(start_cucumbers, start, eat, left):
assert isinstance(left, str)
assert start - eat == int(left)
assert start_cucumbers['start'] == start
assert start_cucumbers['eat'] == eat
Example code also shows possibility to pass example converters which may be useful if you need parameter types
different than strings.
Feature examples
^^^^^^^^^^^^^^^^
It's possible to declare example table once for the whole feature, and it will be shared
among all the scenarios of that feature:
.. code-block:: gherkin
Feature: Outline
Examples:
| start | eat | left |
| 12 | 5 | 7 |
| 5 | 4 | 1 |
Scenario Outline: Eat cucumbers
Given there are <start> cucumbers
When I eat <eat> cucumbers
Then I should have <left> cucumbers
Scenario Outline: Eat apples
Given there are <start> apples
When I eat <eat> apples
Then I should have <left> apples
For some more complex case, you might want to parametrize on both levels: feature and scenario.
This is allowed as long as parameter names do not clash:
.. code-block:: gherkin
Feature: Outline
Examples:
| start | eat | left |
| 12 | 5 | 7 |
| 5 | 4 | 1 |
Scenario Outline: Eat fruits
Given there are <start> <fruits>
When I eat <eat> <fruits>
Then I should have <left> <fruits>
Examples:
| fruits |
| oranges |
| apples |
Scenario Outline: Eat vegetables
Given there are <start> <vegetables>
When I eat <eat> <vegetables>
Then I should have <left> <vegetables>
Examples:
| vegetables |
| carrots |
| tomatoes |
Combine scenario outline and pytest parametrization
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It's also possible to parametrize the scenario on the python side.
The reason for this is that it is sometimes not needed to mention example table for every scenario.
The code will look like:
.. code-block:: python
import pytest
from pytest_bdd import scenario, given, when, then
# Here we use pytest to parametrize the test with the parameters table
@pytest.mark.parametrize(
['start', 'eat', 'left'],
[(12, 5, 7)])
@scenario(
'parametrized.feature',
'Parametrized given, when, thens',
)
# Note that we should take the same arguments in the test function that we use
# for the test parametrization either directly or indirectly (fixtures depend on them).
def test_parametrized(start, eat, left):
"""We don't need to do anything here, everything will be managed by the scenario decorator."""
@given('there are <start> cucumbers')
def start_cucumbers(start):
return dict(start=start)
@when('I eat <eat> cucumbers')
def eat_cucumbers(start_cucumbers, start, eat):
start_cucumbers['eat'] = eat
@then('I should have <left> cucumbers')
def should_have_left_cucumbers(start_cucumbers, start, eat, left):
assert start - eat == left
assert start_cucumbers['start'] == start
assert start_cucumbers['eat'] == eat
With a parametrized.feature file:
.. code-block:: gherkin
Feature: parametrized
Scenario: Parametrized given, when, thens
Given there are <start> cucumbers
When I eat <eat> cucumbers
Then I should have <left> cucumbers
The significant downside of this approach is inability to see the test table from the feature file.
Organizing your scenarios
-------------------------
The more features and scenarios you have, the more important becomes the question about their organization.
The things you can do (and that is also a recommended way):
* organize your feature files in the folders by semantic groups:
::
features
│
├──frontend
│ │
│ └──auth
│ │
│ └──login.feature
└──backend
│
└──auth
│
└──login.feature
This looks fine, but how do you run tests only for certain feature?
As pytest-bdd uses pytest, and bdd scenarios are actually normal tests. But test files
are separate from the feature files, the mapping is up to developers, so the test files structure can look
completely different:
::
tests
│
└──functional
│
└──test_auth.py
│
└ """Authentication tests."""
from pytest_bdd import scenario
@scenario('frontend/auth/login.feature')
def test_logging_in_frontend():
pass
@scenario('backend/auth/login.feature')
def test_logging_in_backend():
pass
For picking up tests to run we can use
`tests selection <http://pytest.org/latest/usage.html#specifying-tests-selecting-tests>`_ technique. The problem is that
you have to know how your tests are organized, knowing ony the feature files organization is not enough.
`cucumber tags <https://github.com/cucumber/cucumber/wiki/Tags>`_ introduce standard way of categorizing your features
and scenarios, which pytest-bdd supports. For example, we could have:
.. code-block:: gherkin
@login @backend
Feature: Login
@successful
Scenario: Successful login
pytest-bdd uses `pytest markers <http://pytest.org/latest/mark.html#mark>`_ as a `storage` of the tags for the given
scenario test, so we can use standard test selection:
.. code-block:: bash
py.test -k "backend and login and successful"
The feature and scenario markers are not different from standard pytest markers, and the `@` symbol is stripped out
automatically to allow test selector expressions. If you want to have bdd-related tags to be distinguishable from the
other test markers, use prefix like `bdd`.
Note that if you use pytest `--strict` option, all bdd tags mentioned in the feature files should be also in the
`markers` setting of the `pytest.ini` config. Also for tags please use names which are python-compartible variable
names, eg starts with a non-number, underscore alphanumberic, etc. That way you can safely use tags for tests filtering.
You can customize how hooks are converted to pytest marks by implementing the
``pytest_bdd_apply_tag`` hook and returning ``True`` from it:
.. code-block:: python
def pytest_bdd_apply_tag(tag, function):
if tag == 'todo':
marker = pytest.mark.skip(reason="Not implemented yet")
marker(function)
return True
else:
# Fall back to pytest-bdd's default behavior
return None
Test setup
----------
Test setup is implemented within the Given section. Even though these steps
are executed imperatively to apply possible side-effects, pytest-bdd is trying
to benefit of the PyTest fixtures which is based on the dependency injection
and makes the setup more declarative style.
.. code-block:: python
@given('I have a beautiful article')
def article():
return Article(is_beautiful=True)
This also declares a PyTest fixture "article" and any other step can depend on it.
.. code-block:: gherkin
Given I have a beautiful article
When I publish this article
When step is referring the article to publish it.
.. code-block:: python
@when('I publish this article')
def publish_article(article):
article.publish()
Many other BDD toolkits operate a global context and put the side effects there.
This makes it very difficult to implement the steps, because the dependencies
appear only as the side-effects in the run-time and not declared in the code.
The publish article step has to trust that the article is already in the context,
has to know the name of the attribute it is stored there, the type etc.
In pytest-bdd you just declare an argument of the step function that it depends on
and the PyTest will make sure to provide it.
Still side effects can be applied in the imperative style by design of the BDD.
.. code-block:: gherkin
Given I have a beautiful article
And my article is published
Functional tests can reuse your fixture libraries created for the unit-tests and upgrade
them by applying the side effects.
.. code-block:: python
given('I have a beautiful article', fixture='article')
@given('my article is published')
def published_article(article):
article.publish()
return article
This way side-effects were applied to our article and PyTest makes sure that all
steps that require the "article" fixture will receive the same object. The value
of the "published_article" and the "article" fixtures is the same object.
Fixtures are evaluated only once within the PyTest scope and their values are cached.
In case of Given steps and the step arguments mentioning the same given step makes
no sense. It won't be executed second time.
.. code-block:: gherkin
Given I have a beautiful article
And some other thing
And I have a beautiful article # Won't be executed, exception is raised
pytest-bdd will raise an exception even in the case of the steps that use regular expression
patterns to get arguments.
.. code-block:: gherkin
Given I have 1 cucumbers
And I have 2 cucumbers # Exception is raised
Will raise an exception if the step is using the regular expression pattern.
.. code-block:: python
@given(re.compile('I have (?P<n>\d+) cucumbers'))
def cucumbers(n):
return create_cucumbers(n)
Backgrounds
-----------
It's often the case that to cover certain feature, you'll need multiple scenarios. And it's logical that the
setup for those scenarios will have some common parts (if not equal). For this, there are `backgrounds`.
pytest-bdd implements `Gherkin backgrounds <http://docs.behat.org/en/v2.5/guides/1.gherkin.html#backgrounds>`_ for
features.
.. code-block:: gherkin
Feature: Multiple site support
Background:
Given a global administrator named "Greg"
And a blog named "Greg's anti-tax rants"
And a customer named "Wilson"
And a blog named "Expensive Therapy" owned by "Wilson"
Scenario: Wilson posts to his own blog
Given I am logged in as Wilson
When I try to post to "Expensive Therapy"
Then I should see "Your article was published."
Scenario: Greg posts to a client's blog
Given I am logged in as Greg
When I try to post to "Expensive Therapy"
Then I should see "Your article was published."
In this example, all steps from the background will be executed before all the scenario's own given
steps, adding possibility to prepare some common setup for multiple scenarios in a single feature.
About background best practices, please read
`here <https://github.com/cucumber/cucumber/wiki/Background#good-practices-for-using-background>`_.
.. NOTE:: There is only step "Given" should be used in "Background" section,
steps "When" and "Then" are prohibited, because their purpose are
related to actions and consuming outcomes, that is conflict with
"Background" aim - prepare system for tests or "put the system
in a known state" as "Given" does it.
The statement above is applied for strict Gherkin mode, which is
enabled by default.
Reusing fixtures
----------------
Sometimes scenarios define new names for the existing fixture that can be
inherited (reused). For example, if we have pytest fixture:
.. code-block:: python
@pytest.fixture
def article():
"""Test article."""
return Article()
Then this fixture can be reused with other names using given():
.. code-block:: python
given('I have beautiful article', fixture='article')
This will be equivalent to:
.. code-block:: python
@given('I have beautiful article')
def i_have_an_article(article):
"""I have an article."""
return article
Reusing steps
-------------
It is possible to define some common steps in the parent conftest.py and
simply expect them in the child test file.
common_steps.feature:
.. code-block:: gherkin
Scenario: All steps are declared in the conftest
Given I have a bar
Then bar should have value "bar"
conftest.py:
.. code-block:: python
from pytest_bdd import given, then
@given('I have a bar')
def bar():
return 'bar'
@then('bar should have value "bar"')
def bar_is_bar(bar):
assert bar == 'bar'
test_common.py:
.. code-block:: python
@scenario('common_steps.feature', 'All steps are declared in the conftest')
def test_conftest():
pass
There are no definitions of the steps in the test file. They were
collected from the parent conftests.
Using unicode in the feature files
----------------------------------
As mentioned above, by default, utf-8 encoding is used for parsing feature files.
For steps definition, you can both use unicode- and bytestrings equally.
However, for argumented steps, if you need to use unicode symbols in it's regular expression, use `u` sign with regex:
.. code-block:: python
@given(re.compile(u"у мене є рядок який містить '{0}'".format('(?P<content>.+)')))
def there_is_a_string_with_content(content, string):
"""Create string with unicode content."""
string['content'] = content
Default steps
-------------
Here is the list of steps that are implemented inside of the pytest-bdd:
given
* trace - enters the `pdb` debugger via `pytest.set_trace()`
when
* trace - enters the `pdb` debugger via `pytest.set_trace()`
then
* trace - enters the `pdb` debugger via `pytest.set_trace()`
Feature file paths
------------------
By default, pytest-bdd will use current module's path as base path for
finding feature files, but this behaviour can be changed by having
fixture named ``pytestbdd_feature_base_dir`` which should return the
new base path.
test_publish_article.py:
.. code-block:: python
import pytest
from pytest_bdd import scenario
@pytest.fixture
def pytestbdd_feature_base_dir():
return '/home/user/projects/foo.bar/features'
@scenario('publish_article.feature', 'Publishing the article')
def test_publish():
pass
Avoid retyping the feature file name
------------------------------------
If you want to avoid retyping the feature file name when defining your scenarios in a test file, use functools.partial.
This will make your life much easier when defining multiple scenarios in a test file.
For example:
test_publish_article.py:
.. code-block:: python
from functools import partial
import pytest_bdd
scenario = partial(pytest_bdd.scenario, '/path/to/publish_article.feature')
@scenario('Publishing the article')
def test_publish():
pass
@scenario('Publishing the article as unprivileged user')
def test_publish_unprivileged():
pass
You can learn more about `functools.partial <http://docs.python.org/2/library/functools.html#functools.partial>`_
in the Python docs.
Relax strict Gherkin language validation
----------------------------------------
If your scenarios are not written in `proper` Gherkin language, e.g. they are more like textual scripts, then
you might find it hard to use `pytest-bdd` as by default it validates the order of step types (given-when-then).
To relax that validation, just override a fixture `pytestbdd_strict_gherkin` to return `False`:
test_publish_article.py:
.. code-block:: python
import pytest
from pytest_bdd import scenario
@pytest.fixture
def pytestbdd_strict_gherkin():
return False
@scenario('publish_article.feature', 'Publishing the article in a wierd way')
def test_publish():
pass
Hooks
-----
pytest-bdd exposes several `pytest hooks <http://pytest.org/latest/plugins.html#well-specified-hooks>`_
which might be helpful building useful reporting, visualization, etc on top of it:
* pytest_bdd_before_scenario(request, feature, scenario) - Called before scenario is executed
* pytest_bdd_after_scenario(request, feature, scenario) - Called after scenario is executed
(even if one of steps has failed)
* pytest_bdd_before_step(request, feature, scenario, step, step_func) - Called before step function
is executed and it's arguments evaluated
* pytest_bdd_before_step_call(request, feature, scenario, step, step_func, step_func_args) - Called before step
* function is executed with evaluated arguments
* pytest_bdd_after_step(request, feature, scenario, step, step_func, step_func_args) - Called after step function
is successfully executed
* pytest_bdd_step_error(request, feature, scenario, step, step_func, step_func_args, exception) - Called when step
function failed to execute
* pytest_bdd_step_validation_error(request, feature, scenario, step, step_func, step_func_args, exception) - Called
when step failed to validate
* pytest_bdd_step_func_lookup_error(request, feature, scenario, step, exception) - Called when step lookup failed
Browser testing
---------------
Tools recommended to use for browser testing:
* pytest-splinter_ - pytest `splinter <http://splinter.cobrateam.info/>`_ integration for the real browser testing
Reporting
---------
It's important to have nice reporting out of your bdd tests. Cucumber introduced some kind of standard for
`json format <https://www.relishapp.com/cucumber/cucumber/docs/json-output-formatter>`_
which can be used for `this <https://wiki.jenkins-ci.org/display/JENKINS/Cucumber+Test+Result+Plugin>`_ jenkins
plugin
To have an output in json format:
::
py.test --cucumberjson=<path to json report>
To enable gherkin-formatted output on terminal, use
::
py.test --gherkin-terminal-reporter
Test code generation helpers
----------------------------
For newcomers it's sometimes hard to write all needed test code without being frustrated.
To simplify their life, simple code generator was implemented. It allows to create fully functional
but of course empty tests and step definitions for given a feature file.
It's done as a separate console script provided by pytest-bdd package:
::
pytest-bdd generate <feature file name> .. <feature file nameN>
It will print the generated code to the standard output so you can easily redirect it to the file:
::
pytest-bdd generate features/some.feature > tests/functional/test_some.py
Advanced code generation
------------------------
For more experienced users, there's smart code generation/suggestion feature. It will only generate the
test code which is not yet there, checking existing tests and step definitions the same way it's done during the
test execution. The code suggestion tool is called via passing additional pytest arguments:
::
py.test --generate-missing --feature features tests/functional
The output will be like:
::
============================= test session starts ==============================
platform linux2 -- Python 2.7.6 -- py-1.4.24 -- pytest-2.6.2
plugins: xdist, pep8, cov, cache, bdd, bdd, bdd
collected 2 items
Scenario is not bound to any test: "Code is generated for scenarios which are not bound to any tests" in feature "Missing code generation" in /tmp/pytest-552/testdir/test_generate_missing0/tests/generation.feature
--------------------------------------------------------------------------------
Step is not defined: "I have a custom bar" in scenario: "Code is generated for scenario steps which are not yet defined(implemented)" in feature "Missing code generation" in /tmp/pytest-552/testdir/test_generate_missing0/tests/generation.feature
--------------------------------------------------------------------------------
Please place the code above to the test file(s):
@scenario('tests/generation.feature', 'Code is generated for scenarios which are not bound to any tests')
def test_Code_is_generated_for_scenarios_which_are_not_bound_to_any_tests():
"""Code is generated for scenarios which are not bound to any tests."""
@given('I have a custom bar')
def I_have_a_custom_bar():
"""I have a custom bar."""
As as side effect, the tool will validate the files for format errors, also some of the logic bugs, for example the
ordering of the types of the steps.
Migration of your tests from versions 0.x.x-1.x.x
-------------------------------------------------
In version 2.0.0, the backwards-incompartible change was introduced: scenario function can now only be used as a
decorator. Reasons for that:
* test code readability is much higher using normal python function syntax;
* pytest-bdd internals are much cleaner and shorter when using single approach instead of supporting two;
* after moving to parsing-on-import-time approach for feature files, it's not possible to detect whether it's a
decorator more or not, so to support it along with functional approach there needed to be special parameter
for that, which is also a backwards-incompartible change.
To help users migrate to newer version, there's migration subcommand of the `pytest-bdd` console script:
::
# run migration script
pytest-bdd migrate <your test folder>
Under the hood the script does the replacement from this:
.. code-block:: python
test_function = scenario('publish_article.feature', 'Publishing the article')
to this:
.. code-block:: python
@scenario('publish_article.feature', 'Publishing the article')
def test_function():
pass
License
-------
This software is licensed under the `MIT license <http://en.wikipedia.org/wiki/MIT_License>`_.
© 2013-2014 Oleg Pidsadnyi, Anatoly Bubenkov and others
Authors
=======
`Oleg Pidsadnyi <oleg.pidsadnyi@gmail.com>`_
original idea, initial implementation and further improvements
`Anatoly Bubenkov <bubenkoff@gmail.com>`_
key implementation idea and realization, many new features and improvements
These people have contributed to `pytest-bdd`, in alphabetical order:
* `Adam Coddington <me@adamcoddington.net>`_
* `Albert-Jan Nijburg <albertjan@curit.com>`_
* `Andrey Makhnach <andrey.makhnach@gmail.com>`_
* `Aron Curzon <curzona@gmail.com>`_
* `Dmitrijs Milajevs <dimazest@gmail.com>`_
* `Florian Bruhin <me@the-compiler.org>`_
* `Floris Bruynooghe <flub@devork.be>`_
* `Harro van der Klauw <hvdklauw@gmail.com>`_
* `Laurence Rowe <l@lrowe.co.uk>`_
* `Leonardo Santagada <santagada@github.com>`_
* `Robin Pedersen <ropez@github.com>`_
* `Sergey Kraynev <sergejyit@gmail.com>`_
Changelog
=========
2.18.2
------
- Fix check for out section steps definitions for no strict gherkin feature
2.18.1
------
- Relay fixture results to recursive call of 'get_features' (coddingtonbear)
2.18.0
------
- Add gherkin terminal reporter (spinus + thedrow)
2.17.2
------
- Fix scenario lines containing an ``@`` being parsed as a tag. (The-Compiler)
2.17.1
------
- Add support for pytest 3.0
2.17.0
------
- Fix FixtureDef signature for newer pytest versions (The-Compiler)
- Better error explanation for the steps defined outside of scenarios (olegpidsadnyi)
- Add a ``pytest_bdd_apply_tag`` hook to customize handling of tags (The-Compiler)
- Allow spaces in tag names. This can be useful when using the
``pytest_bdd_apply_tag`` hook with tags like ``@xfail: Some reason``.
2.16.1
------
- Cleaned up hooks of the plugin (olegpidsadnyi)
- Fixed report serialization (olegpidsadnyi)
2.16.0
------
- Fixed deprecation warnings with pytest 2.8 (The-Compiler)
- Fixed deprecation warnings with Python 3.5 (The-Compiler)
2.15.0
------
- Add examples data in the scenario report (bubenkoff)
2.14.5
------
- Properly parse feature description (bubenkoff)
2.14.3
------
- Avoid potentially random collection order for xdist compartibility (bubenkoff)
2.14.1
------
- Pass additional arguments to parsers (bubenkoff)
2.14.0
------
- Add validation check which prevents having multiple features in a single feature file (bubenkoff)
2.13.1
------
- Allow mixing feature example table with scenario example table (bubenkoff, olegpidsadnyi)
2.13.0
------
- Feature example table (bubenkoff, sureshvv)
2.12.2
------
- Make it possible to relax strict Gherkin scenario validation (bubenkoff)
2.11.3
------
- Fix minimal `six` version (bubenkoff, dustinfarris)
2.11.1
------
- Mention step type on step definition not found errors and in code generation (bubenkoff, lrowe)
2.11.0
------
- Prefix step definition fixture names to avoid name collisions (bubenkoff, lrowe)
2.10.0
------
- Make feature and scenario tags to be fully compartible with pytest markers (bubenkoff, kevinastone)
2.9.1
-----
- Fixed FeatureError string representation to correctly support python3 (bubenkoff, lrowe)
2.9.0
-----
- Added possibility to inject fixtures from given keywords (bubenkoff)
2.8.0
-----
- Added hook before the step is executed with evaluated parameters (olegpidsadnyi)
2.7.2
-----
- Correct base feature path lookup for python3 (bubenkoff)
2.7.1
-----
- Allow to pass ``scope`` for ``given`` steps (bubenkoff, sureshvv)
2.7.0
-----
- Implemented `scenarios` shortcut to automatically bind scenarios to tests (bubenkoff)
2.6.2
-----
- Parse comments only in the begining of words (santagada)
2.6.1
-----
- Correctly handle `pytest-bdd` command called without the subcommand under python3 (bubenkoff, spinus)
- Pluggable parsers for step definitions (bubenkoff, spinus)
2.5.3
-----
- Add after scenario hook, document both before and after scenario hooks (bubenkoff)
2.5.2
-----
- Fix code generation steps ordering (bubenkoff)
2.5.1
-----
- Fix error report serialization (olegpidsadnyi)
2.5.0
-----
- Fix multiline steps in the Background section (bubenkoff, arpe)
- Code cleanup (olegpidsadnyi)
2.4.5
-----
- Fix unicode issue with scenario name (bubenkoff, aohontsev)
2.4.3
-----
- Fix unicode regex argumented steps issue (bubenkoff, aohontsev)
- Fix steps timings in the json reporting (bubenkoff)
2.4.2
-----
- Recursion is fixed for the --generate-missing and the --feature parameters (bubenkoff)
2.4.1
-----
- Better reporting of a not found scenario (bubenkoff)
- Simple test code generation implemented (bubenkoff)
- Correct timing values for cucumber json reporting (bubenkoff)
- Validation/generation helpers (bubenkoff)
2.4.0
-----
- Background support added (bubenkoff)
- Fixed double collection of the conftest files if scenario decorator is used (ropez, bubenkoff)
2.3.3
-----
- Added timings to the cucumber json report (bubenkoff)
2.3.2
-----
- Fixed incorrect error message using e.argname instead of step.name (hvdklauw)
2.3.1
-----
- Implemented cucumber tags support (bubenkoff)
- Implemented cucumber json formatter (bubenkoff, albertjan)
- Added 'trace' keyword (bubenkoff)
2.1.2
-----
- Latest pytest compartibility fixes (bubenkoff)
2.1.1
-----
- Bugfixes (bubenkoff)
2.1.0
-----
- Implemented multiline steps (bubenkoff)
2.0.1
-----
- Allow more than one parameter per step (bubenkoff)
- Allow empty example values (bubenkoff)
2.0.0
-----
- Pure pytest parametrization for scenario outlines (bubenkoff)
- Argumented steps now support converters (transformations) (bubenkoff)
- scenario supports only decorator form (bubenkoff)
- Code generation refactoring and cleanup (bubenkoff)
1.0.0
-----
- Implemented scenario outlines (bubenkoff)
0.6.11
------
- Fixed step arguments conflict with the fixtures having the same name (olegpidsadnyi)
0.6.9
-----
- Implemented support of Gherkin "Feature:" (olegpidsadnyi)
0.6.8
-----
- Implemented several hooks to allow reporting/error handling (bubenkoff)
0.6.6
-----
- Fixes to unnecessary mentioning of pytest-bdd package files in py.test log with -v (bubenkoff)
0.6.5
-----
- Compartibility with recent pytest (bubenkoff)
0.6.4
-----
- More unicode fixes (amakhnach)
0.6.3
-----
- Added unicode support for feature files. Removed buggy module replacement for scenario. (amakhnach)
0.6.2
-----
- Removed unnecessary mention of pytest-bdd package files in py.test log with -v (bubenkoff)
0.6.1
-----
- Step arguments in whens when there are no given arguments used. (amakhnach, bubenkoff)
0.6.0
-----
- Added step arguments support. (curzona, olegpidsadnyi, bubenkoff)
- Added checking of the step type order. (markon, olegpidsadnyi)
0.5.2
-----
- Added extra info into output when FeatureError exception raises. (amakhnach)
0.5.0
-----
- Added parametrization to scenarios
- Coveralls.io integration
- Test coverage improvement/fixes
- Correct wrapping of step functions to preserve function docstring
0.4.7
-----
- Fixed Python 3.3 support
0.4.6
-----
- Fixed a bug when py.test --fixtures showed incorrect filenames for the steps.
0.4.5
-----
- Fixed a bug with the reuse of the fixture by given steps being evaluated multiple times.
0.4.3
-----
- Update the license file and PYPI related documentation.
Platform: UNKNOWN
Classifier: Development Status :: 6 - Mature
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: POSIX
Classifier: Operating System :: Microsoft :: Windows
Classifier: Operating System :: MacOS :: MacOS X
Classifier: Topic :: Software Development :: Testing
Classifier: Topic :: Software Development :: Libraries
Classifier: Topic :: Utilities
Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3.0
Classifier: Programming Language :: Python :: 3.1
Classifier: Programming Language :: Python :: 3.2
Classifier: Programming Language :: Python :: 3.3
Classifier: Programming Language :: Python :: 3.4
|