work with the latest Flask code before it’s released, install or update the code from the master branch: $ pip install -U https://github.com/pallets/flask/archive/master.tar.gz Install virtualenv If the condition is met. You want to make sure that each function is tested with data that covers each branch. The closer you get to 100% coverage, the more comfortable you can be that making a change won’t added to the project’s setup.cfg file. setup.cfg [tool:pytest] testpaths = tests [coverage:run] branch = True source = flaskr To run the tests, use the pytest command. It will find and run all the

work with the latest Flask code before it’s released, install or update the code from the master branch: $ pip install -U https://github.com/pallets/flask/archive/master.tar.gz 1.3.5 Install virtualenv the condition is met. You want to make sure that each function is tested with data that covers each branch. The closer you get to 100% coverage, the more comfortable you can be that making a change won’t Guide Flask Documentation (1.1.x), Release 1.1.4 (continued from previous page) [coverage:run] branch = True source = flaskr To run the tests, use the pytest command. It will find and run all the test

ive Alternately, if you push changes to your fork on Github, Travis will run the tests for your branch automatically. A Tox config file is also provided so you can test against multiple python versions

ive Alternately, if you push changes to your fork on Github, Travis will run the tests for your branch automatically. A Tox config file is also provided so you can test against multiple python versions

ive Alternately, if you push changes to your fork on Github, Travis will run the tests for your branch automatically. A Tox config file is also provided so you can test against multiple python versions

ive Alternately, if you push changes to your fork on Github, Travis will run the tests for your branch automatically. A Tox config file is also provided so you can test against multiple python versions

ive Alternately, if you push changes to your fork on Github, Travis will run the tests for your branch automatically. A Tox config file is also provided so you can test against multiple python versions

ive Alternately, if you push changes to your fork on Github, Travis will run the tests for your branch automatically. A Tox config file is also provided so you can test against multiple python versions

ive Alternately, if you push changes to your fork on Github, Travis will run the tests for your branch automatically. A Tox config file is also provided so you can test against multiple python versions

ive Alternately, if you push changes to your fork on Github, Travis will run the tests for your branch automatically. A Tox config file is also provided so you can test against multiple python versions