Skip to content

Instantly share code, notes, and snippets.

@vortec

vortec/gist:9992923

Created April 5, 2014 14:47
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save vortec/9992923 to your computer and use it in GitHub Desktop.
Save vortec/9992923 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
gistfile1.txt
(versionbump)[vortec@MBPro] ~VIRTUAL_ENV/versionbump (git)-[master]$ time tox †: 0
GLOB sdist-make: /Users/vortec/workspace/virtualenvs/versionbump/versionbump/setup.py
py26 inst-nodeps: /Users/vortec/workspace/virtualenvs/versionbump/versionbump/.tox/dist/versionbump-1.0.0.zip
py26 runtests: PYTHONHASHSEED='754264446'
py26 runtests: commands[0] | py.test
========================================= test session starts ==========================================
platform darwin -- Python 2.6.8 -- py-1.4.20 -- pytest-2.5.2
collected 14 items
tests/unit/test_filebump.py ......
tests/unit/test_versionbump.py ........
====================================== 14 passed in 0.06 seconds =======================================
py26 runtests: commands[1] | behave tests/features
Feature: Bump version from stdin # tests/features/bump_version_from_stdin.feature:1
Scenario: Increase patch version from stdin # tests/features/bump_version_from_stdin.feature:3
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.071s
Then the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase minor version from stdin # tests/features/bump_version_from_stdin.feature:9
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump minor # tests/features/steps/cli_steps.py:11 0.074s
Then the output was 0.2.0 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase major version from stdin # tests/features/bump_version_from_stdin.feature:15
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump major # tests/features/steps/cli_steps.py:11 0.072s
Then the output was 1.0.0 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Run in quiet mode # tests/features/bump_version_from_stdin.feature:21
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
And we use parameter --quiet # tests/features/steps/cli_steps.py:3 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.078s
Then there was no output # tests/features/steps/cli_steps.py:28 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Feature: Bump version in a file # tests/features/bump_version_in_a_file.feature:1
Scenario: Increase patch version in a file # tests/features/bump_version_in_a_file.feature:3
Given a file that contains 0.1.2 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.072s
Then the file contains 0.1.3 # tests/features/steps/file_steps.py:19 0.000s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase minor version in a file # tests/features/bump_version_in_a_file.feature:11
Given a file that contains 0.1.2 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump minor # tests/features/steps/cli_steps.py:11 0.084s
Then the file contains 0.2.0 # tests/features/steps/file_steps.py:19 0.000s
And the output was 0.2.0 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase major version in a file # tests/features/bump_version_in_a_file.feature:19
Given a file that contains 0.1.2 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump major # tests/features/steps/cli_steps.py:11 0.076s
Then the file contains 1.0.0 # tests/features/steps/file_steps.py:19 0.000s
And the output was 1.0.0 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Feature: Bump version in multiple files # tests/features/bump_version_in_multiple_files.feature:1
Scenario: Increase patch version in multiple files # tests/features/bump_version_in_multiple_files.feature:3
Given a file named aa.txt that contains 0.1.2 # tests/features/steps/file_steps.py:9 0.000s
And a file named bb.txt that contains 0.1.2 # tests/features/steps/file_steps.py:9 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.073s
Then the file aa.txt contains 0.1.3 # tests/features/steps/file_steps.py:26 0.000s
And the file bb.txt contains 0.1.3 # tests/features/steps/file_steps.py:26 0.000s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Feature: Fail invalid versions # tests/features/fail_invalid_versions.feature:1
Scenario: Fail if the assumed version is invalid # tests/features/fail_invalid_versions.feature:3
Given we assume version 0.1.2.3 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.076s
Then the exit code was 1 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Fail if file is empty # tests/features/fail_invalid_versions.feature:8
Given an empty file # tests/features/steps/file_steps.py:15 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.072s
Then the file is empty # tests/features/steps/file_steps.py:33 0.000s
And the exit code was 1 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Fail if file doesn't contain a version # tests/features/fail_invalid_versions.feature:15
Given a file that contains foobar # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.075s
Then the file contains foobar # tests/features/steps/file_steps.py:19 0.000s
And the exit code was 1 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Fail if file doesn't contain the assumed version # tests/features/fail_invalid_versions.feature:22
Given a file that contains 2.1.0 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.078s
Then the file contains 2.1.0 # tests/features/steps/file_steps.py:19 0.000s
And the exit code was 1 # tests/features/steps/cli_steps.py:32 0.000s
Feature: Ignore invalid versions # tests/features/ignore_invalid_versions.feature:1
Scenario: Ignore invalid file when increasing patch version # tests/features/ignore_invalid_versions.feature:3
Given a file that contains 2.1.0 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
And we use parameter --ignore # tests/features/steps/cli_steps.py:3 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.071s
Then the file contains 2.1.0 # tests/features/steps/file_steps.py:19 0.000s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Ignore invalid files when increasing patch version # tests/features/ignore_invalid_versions.feature:12
Given a file named aa.txt that contains 0.1.2 # tests/features/steps/file_steps.py:9 0.000s
And a file named bb.txt that contains 2.1.0 # tests/features/steps/file_steps.py:9 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
And we use parameter --ignore # tests/features/steps/cli_steps.py:3 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.073s
Then the file aa.txt contains 0.1.3 # tests/features/steps/file_steps.py:26 0.000s
And the file bb.txt contains 2.1.0 # tests/features/steps/file_steps.py:26 0.000s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
5 features passed, 0 failed, 0 skipped
14 scenarios passed, 0 failed, 0 skipped
77 steps passed, 0 failed, 0 skipped, 0 undefined
Took 0m1.055s
py27 inst-nodeps: /Users/vortec/workspace/virtualenvs/versionbump/versionbump/.tox/dist/versionbump-1.0.0.zip
py27 runtests: PYTHONHASHSEED='754264446'
py27 runtests: commands[0] | py.test
========================================= test session starts ==========================================
platform darwin -- Python 2.7.6 -- py-1.4.20 -- pytest-2.5.2
collected 14 items
tests/unit/test_filebump.py ......
tests/unit/test_versionbump.py ........
====================================== 14 passed in 0.06 seconds =======================================
py27 runtests: commands[1] | behave tests/features
Feature: Bump version from stdin # tests/features/bump_version_from_stdin.feature:1
Scenario: Increase patch version from stdin # tests/features/bump_version_from_stdin.feature:3
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.063s
Then the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase minor version from stdin # tests/features/bump_version_from_stdin.feature:9
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump minor # tests/features/steps/cli_steps.py:11 0.064s
Then the output was 0.2.0 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase major version from stdin # tests/features/bump_version_from_stdin.feature:15
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump major # tests/features/steps/cli_steps.py:11 0.058s
Then the output was 1.0.0 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Run in quiet mode # tests/features/bump_version_from_stdin.feature:21
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
And we use parameter --quiet # tests/features/steps/cli_steps.py:3 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.059s
Then there was no output # tests/features/steps/cli_steps.py:28 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Feature: Bump version in a file # tests/features/bump_version_in_a_file.feature:1
Scenario: Increase patch version in a file # tests/features/bump_version_in_a_file.feature:3
Given a file that contains 0.1.2 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.060s
Then the file contains 0.1.3 # tests/features/steps/file_steps.py:19 0.000s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase minor version in a file # tests/features/bump_version_in_a_file.feature:11
Given a file that contains 0.1.2 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump minor # tests/features/steps/cli_steps.py:11 0.058s
Then the file contains 0.2.0 # tests/features/steps/file_steps.py:19 0.000s
And the output was 0.2.0 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase major version in a file # tests/features/bump_version_in_a_file.feature:19
Given a file that contains 0.1.2 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump major # tests/features/steps/cli_steps.py:11 0.057s
Then the file contains 1.0.0 # tests/features/steps/file_steps.py:19 0.000s
And the output was 1.0.0 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Feature: Bump version in multiple files # tests/features/bump_version_in_multiple_files.feature:1
Scenario: Increase patch version in multiple files # tests/features/bump_version_in_multiple_files.feature:3
Given a file named aa.txt that contains 0.1.2 # tests/features/steps/file_steps.py:9 0.000s
And a file named bb.txt that contains 0.1.2 # tests/features/steps/file_steps.py:9 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.063s
Then the file aa.txt contains 0.1.3 # tests/features/steps/file_steps.py:26 0.000s
And the file bb.txt contains 0.1.3 # tests/features/steps/file_steps.py:26 0.000s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Feature: Fail invalid versions # tests/features/fail_invalid_versions.feature:1
Scenario: Fail if the assumed version is invalid # tests/features/fail_invalid_versions.feature:3
Given we assume version 0.1.2.3 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.056s
Then the exit code was 1 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Fail if file is empty # tests/features/fail_invalid_versions.feature:8
Given an empty file # tests/features/steps/file_steps.py:15 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.060s
Then the file is empty # tests/features/steps/file_steps.py:33 0.000s
And the exit code was 1 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Fail if file doesn't contain a version # tests/features/fail_invalid_versions.feature:15
Given a file that contains foobar # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.063s
Then the file contains foobar # tests/features/steps/file_steps.py:19 0.000s
And the exit code was 1 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Fail if file doesn't contain the assumed version # tests/features/fail_invalid_versions.feature:22
Given a file that contains 2.1.0 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.060s
Then the file contains 2.1.0 # tests/features/steps/file_steps.py:19 0.000s
And the exit code was 1 # tests/features/steps/cli_steps.py:32 0.000s
Feature: Ignore invalid versions # tests/features/ignore_invalid_versions.feature:1
Scenario: Ignore invalid file when increasing patch version # tests/features/ignore_invalid_versions.feature:3
Given a file that contains 2.1.0 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
And we use parameter --ignore # tests/features/steps/cli_steps.py:3 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.057s
Then the file contains 2.1.0 # tests/features/steps/file_steps.py:19 0.000s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Ignore invalid files when increasing patch version # tests/features/ignore_invalid_versions.feature:12
Given a file named aa.txt that contains 0.1.2 # tests/features/steps/file_steps.py:9 0.000s
And a file named bb.txt that contains 2.1.0 # tests/features/steps/file_steps.py:9 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
And we use parameter --ignore # tests/features/steps/cli_steps.py:3 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.061s
Then the file aa.txt contains 0.1.3 # tests/features/steps/file_steps.py:26 0.000s
And the file bb.txt contains 2.1.0 # tests/features/steps/file_steps.py:26 0.000s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
5 features passed, 0 failed, 0 skipped
14 scenarios passed, 0 failed, 0 skipped
77 steps passed, 0 failed, 0 skipped, 0 undefined
Took 0m0.848s
py34 inst-nodeps: /Users/vortec/workspace/virtualenvs/versionbump/versionbump/.tox/dist/versionbump-1.0.0.zip
py34 runtests: PYTHONHASHSEED='754264446'
py34 runtests: commands[0] | py.test
========================================= test session starts ==========================================
platform darwin -- Python 3.4.0 -- py-1.4.20 -- pytest-2.5.2
collected 14 items
tests/unit/test_filebump.py ......
tests/unit/test_versionbump.py ........
====================================== 14 passed in 0.07 seconds =======================================
py34 runtests: commands[1] | behave tests/features
Feature: Bump version from stdin # tests/features/bump_version_from_stdin.feature:1
Scenario: Increase patch version from stdin # tests/features/bump_version_from_stdin.feature:3
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.094s
Then the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase minor version from stdin # tests/features/bump_version_from_stdin.feature:9
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump minor # tests/features/steps/cli_steps.py:11 0.091s
Then the output was 0.2.0 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase major version from stdin # tests/features/bump_version_from_stdin.feature:15
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump major # tests/features/steps/cli_steps.py:11 0.089s
Then the output was 1.0.0 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Run in quiet mode # tests/features/bump_version_from_stdin.feature:21
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
And we use parameter --quiet # tests/features/steps/cli_steps.py:3 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.089s
Then there was no output # tests/features/steps/cli_steps.py:28 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Feature: Bump version in a file # tests/features/bump_version_in_a_file.feature:1
Scenario: Increase patch version in a file # tests/features/bump_version_in_a_file.feature:3
Given a file that contains 0.1.2 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.091s
Then the file contains 0.1.3 # tests/features/steps/file_steps.py:19 0.000s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase minor version in a file # tests/features/bump_version_in_a_file.feature:11
Given a file that contains 0.1.2 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump minor # tests/features/steps/cli_steps.py:11 0.089s
Then the file contains 0.2.0 # tests/features/steps/file_steps.py:19 0.001s
And the output was 0.2.0 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase major version in a file # tests/features/bump_version_in_a_file.feature:19
Given a file that contains 0.1.2 # tests/features/steps/file_steps.py:3 0.001s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump major # tests/features/steps/cli_steps.py:11 0.098s
Then the file contains 1.0.0 # tests/features/steps/file_steps.py:19 0.000s
And the output was 1.0.0 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Feature: Bump version in multiple files # tests/features/bump_version_in_multiple_files.feature:1
Scenario: Increase patch version in multiple files # tests/features/bump_version_in_multiple_files.feature:3
Given a file named aa.txt that contains 0.1.2 # tests/features/steps/file_steps.py:9 0.000s
And a file named bb.txt that contains 0.1.2 # tests/features/steps/file_steps.py:9 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.091s
Then the file aa.txt contains 0.1.3 # tests/features/steps/file_steps.py:26 0.000s
And the file bb.txt contains 0.1.3 # tests/features/steps/file_steps.py:26 0.000s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Feature: Fail invalid versions # tests/features/fail_invalid_versions.feature:1
Scenario: Fail if the assumed version is invalid # tests/features/fail_invalid_versions.feature:3
Given we assume version 0.1.2.3 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.087s
Then the exit code was 1 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Fail if file is empty # tests/features/fail_invalid_versions.feature:8
Given an empty file # tests/features/steps/file_steps.py:15 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.088s
Then the file is empty # tests/features/steps/file_steps.py:33 0.001s
And the exit code was 1 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Fail if file doesn't contain a version # tests/features/fail_invalid_versions.feature:15
Given a file that contains foobar # tests/features/steps/file_steps.py:3 0.001s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.097s
Then the file contains foobar # tests/features/steps/file_steps.py:19 0.000s
And the exit code was 1 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Fail if file doesn't contain the assumed version # tests/features/fail_invalid_versions.feature:22
Given a file that contains 2.1.0 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.093s
Then the file contains 2.1.0 # tests/features/steps/file_steps.py:19 0.000s
And the exit code was 1 # tests/features/steps/cli_steps.py:32 0.000s
Feature: Ignore invalid versions # tests/features/ignore_invalid_versions.feature:1
Scenario: Ignore invalid file when increasing patch version # tests/features/ignore_invalid_versions.feature:3
Given a file that contains 2.1.0 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
And we use parameter --ignore # tests/features/steps/cli_steps.py:3 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.089s
Then the file contains 2.1.0 # tests/features/steps/file_steps.py:19 0.001s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Ignore invalid files when increasing patch version # tests/features/ignore_invalid_versions.feature:12
Given a file named aa.txt that contains 0.1.2 # tests/features/steps/file_steps.py:9 0.001s
And a file named bb.txt that contains 2.1.0 # tests/features/steps/file_steps.py:9 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
And we use parameter --ignore # tests/features/steps/cli_steps.py:3 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.095s
Then the file aa.txt contains 0.1.3 # tests/features/steps/file_steps.py:26 0.000s
And the file bb.txt contains 2.1.0 # tests/features/steps/file_steps.py:26 0.000s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
5 features passed, 0 failed, 0 skipped
14 scenarios passed, 0 failed, 0 skipped
77 steps passed, 0 failed, 0 skipped, 0 undefined
Took 0m1.297s
pypy inst-nodeps: /Users/vortec/workspace/virtualenvs/versionbump/versionbump/.tox/dist/versionbump-1.0.0.zip
pypy runtests: PYTHONHASHSEED='754264446'
pypy runtests: commands[0] | py.test
========================================= test session starts ==========================================
platform darwin -- Python 2.7.3[pypy-2.2.1-final] -- py-1.4.20 -- pytest-2.5.2
collected 14 items
tests/unit/test_filebump.py ......
tests/unit/test_versionbump.py ........
====================================== 14 passed in 0.19 seconds =======================================
pypy runtests: commands[1] | behave tests/features
Feature: Bump version from stdin # tests/features/bump_version_from_stdin.feature:1
Scenario: Increase patch version from stdin # tests/features/bump_version_from_stdin.feature:3
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.199s
Then the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase minor version from stdin # tests/features/bump_version_from_stdin.feature:9
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump minor # tests/features/steps/cli_steps.py:11 0.185s
Then the output was 0.2.0 # tests/features/steps/cli_steps.py:24 0.001s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.001s
Scenario: Increase major version from stdin # tests/features/bump_version_from_stdin.feature:15
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump major # tests/features/steps/cli_steps.py:11 0.193s
Then the output was 1.0.0 # tests/features/steps/cli_steps.py:24 0.001s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.001s
Scenario: Run in quiet mode # tests/features/bump_version_from_stdin.feature:21
Given we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
And we use parameter --quiet # tests/features/steps/cli_steps.py:3 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.191s
Then there was no output # tests/features/steps/cli_steps.py:28 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.003s
Feature: Bump version in a file # tests/features/bump_version_in_a_file.feature:1
Scenario: Increase patch version in a file # tests/features/bump_version_in_a_file.feature:3
Given a file that contains 0.1.2 # tests/features/steps/file_steps.py:3 0.001s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.186s
Then the file contains 0.1.3 # tests/features/steps/file_steps.py:19 0.001s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.003s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase minor version in a file # tests/features/bump_version_in_a_file.feature:11
Given a file that contains 0.1.2 # tests/features/steps/file_steps.py:3 0.001s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump minor # tests/features/steps/cli_steps.py:11 0.167s
Then the file contains 0.2.0 # tests/features/steps/file_steps.py:19 0.001s
And the output was 0.2.0 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Increase major version in a file # tests/features/bump_version_in_a_file.feature:19
Given a file that contains 0.1.2 # tests/features/steps/file_steps.py:3 0.001s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump major # tests/features/steps/cli_steps.py:11 0.191s
Then the file contains 1.0.0 # tests/features/steps/file_steps.py:19 0.001s
And the output was 1.0.0 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Feature: Bump version in multiple files # tests/features/bump_version_in_multiple_files.feature:1
Scenario: Increase patch version in multiple files # tests/features/bump_version_in_multiple_files.feature:3
Given a file named aa.txt that contains 0.1.2 # tests/features/steps/file_steps.py:9 0.001s
And a file named bb.txt that contains 0.1.2 # tests/features/steps/file_steps.py:9 0.001s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.191s
Then the file aa.txt contains 0.1.3 # tests/features/steps/file_steps.py:26 0.001s
And the file bb.txt contains 0.1.3 # tests/features/steps/file_steps.py:26 0.001s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.000s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Feature: Fail invalid versions # tests/features/fail_invalid_versions.feature:1
Scenario: Fail if the assumed version is invalid # tests/features/fail_invalid_versions.feature:3
Given we assume version 0.1.2.3 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.189s
Then the exit code was 1 # tests/features/steps/cli_steps.py:32 0.001s
Scenario: Fail if file is empty # tests/features/fail_invalid_versions.feature:8
Given an empty file # tests/features/steps/file_steps.py:15 0.001s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.001s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.188s
Then the file is empty # tests/features/steps/file_steps.py:33 0.000s
And the exit code was 1 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Fail if file doesn't contain a version # tests/features/fail_invalid_versions.feature:15
Given a file that contains foobar # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.188s
Then the file contains foobar # tests/features/steps/file_steps.py:19 0.000s
And the exit code was 1 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Fail if file doesn't contain the assumed version # tests/features/fail_invalid_versions.feature:22
Given a file that contains 2.1.0 # tests/features/steps/file_steps.py:3 0.000s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.191s
Then the file contains 2.1.0 # tests/features/steps/file_steps.py:19 0.001s
And the exit code was 1 # tests/features/steps/cli_steps.py:32 0.001s
Feature: Ignore invalid versions # tests/features/ignore_invalid_versions.feature:1
Scenario: Ignore invalid file when increasing patch version # tests/features/ignore_invalid_versions.feature:3
Given a file that contains 2.1.0 # tests/features/steps/file_steps.py:3 0.001s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
And we use parameter --ignore # tests/features/steps/cli_steps.py:3 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.186s
Then the file contains 2.1.0 # tests/features/steps/file_steps.py:19 0.001s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.001s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.000s
Scenario: Ignore invalid files when increasing patch version # tests/features/ignore_invalid_versions.feature:12
Given a file named aa.txt that contains 0.1.2 # tests/features/steps/file_steps.py:9 0.001s
And a file named bb.txt that contains 2.1.0 # tests/features/steps/file_steps.py:9 0.001s
And we assume version 0.1.2 # tests/features/steps/cli_steps.py:7 0.000s
And we use parameter --ignore # tests/features/steps/cli_steps.py:3 0.000s
When we run versionbump patch # tests/features/steps/cli_steps.py:11 0.185s
Then the file aa.txt contains 0.1.3 # tests/features/steps/file_steps.py:26 0.001s
And the file bb.txt contains 2.1.0 # tests/features/steps/file_steps.py:26 0.001s
And the output was 0.1.3 # tests/features/steps/cli_steps.py:24 0.001s
And the exit code was 0 # tests/features/steps/cli_steps.py:32 0.001s
5 features passed, 0 failed, 0 skipped
14 scenarios passed, 0 failed, 0 skipped
77 steps passed, 0 failed, 0 skipped, 0 undefined
Took 0m2.666s
_______________________________________________ summary ________________________________________________
py26: commands succeeded
py27: commands succeeded
py34: commands succeeded
pypy: commands succeeded
congratulations :)
tox 10.25s user 2.45s system 89% cpu 14.177 total
(versionbump)[vortec@MBPro] ~VIRTUAL_ENV/versionbump (git)-[master]$
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment