Case Conventions Creating Your First Test Case Running Tests Filtering Test Cases Generating Code Coverage Combining Test Suites for Plugins Test Case Lifecycle Callbacks Fixtures Test Connections PHPUnit assert() will yield faster runtime performance, and is recommended for applications that have good test coverage or that are using a static analyzer. Deploying an update On each deploy you’ll likely have a few Code Coverage You can generate code coverage reports from the command line using PHPUnit’s built-in code coverage tools. PHPUnit will generate a set of static HTML files containing the coverage results

assert() will yield faster runtime performance, and is recommended for applications that have good test coverage or that are using a static analyzer. Deploying an update On each deploy you’ll likely have a few Code Coverage You can generate code coverage reports from the command line using PHPUnit’s built-in code coverage tools. PHPUnit will generate a set of static HTML files containing the coverage results You can generate coverage for a test case by doing the following: $ phpunit --coverage-html webroot/coverage tests/TestCase/Model/Table/ArticlesTableTest This will put the coverage results in your application’s

Case Conventions Creating Your First Test Case Running Tests Filtering Test Cases Generating Code Coverage Combining Test Suites for Plugins Test Case Lifecycle Callbacks Fixtures Test Connections PHPUnit Code Coverage You can generate code coverage reports from the command line using PHPUnit’s built-in code coverage tools. PHPUnit will generate a set of static HTML files containing the coverage results You can generate coverage for a test case by doing the following: $ phpunit --coverage-html webroot/coverage tests/TestCase/Model/Table/ArticlesTableTest This will put the coverage results in your application’s

Code Coverage You can generate code coverage reports from the command line using PHPUnit’s built-in code coverage tools. PHPUnit will generate a set of static HTML files containing the coverage results You can generate coverage for a test case by doing the following: $ phpunit --coverage-html webroot/coverage tests/TestCase/Model/Table/ArticlesTableTest This will put the coverage results in your application’s pp/coverage. If you are using PHP 5.6.0 or greater, you can use phpdbg to generate coverage instead of xdebug. phpdbg is generally faster at generating coverage: $ phpdbg -qrr phpunit --coverage-html

Case Conventions Creating Your First Test Case Running Tests Filtering Test Cases Generating Code Coverage Combining Test Suites for Plugins Test Case Lifecycle Callbacks Fixtures Test Connections PHPUnit Code Coverage You can generate code coverage reports from the command line using PHPUnit’s built-in code coverage tools. PHPUnit will generate a set of static HTML files containing the coverage results You can generate coverage for a test case by doing the following: $ phpunit --coverage-html webroot/coverage tests/TestCase/Model/Table/ArticlesTableTest This will put the coverage results in your application’s

Code Coverage You can generate code coverage reports from the command line using PHPUnit’s built-in code coverage tools. PHPUnit will generate a set of static HTML files containing the coverage results You can generate coverage for a test case by doing the following: $ phpunit --coverage-html webroot/coverage tests/TestCase/Model/Table/ArticlesTableTest This will put the coverage results in your application’s http://localhost/your_app/coverage. You can also use phpdbg to generate coverage instead of xdebug. phpdbg is generally faster at generating coverage: $ phpdbg -qrr phpunit --coverage-html webroot/coverage tests/TestCase/Model/Table/

great with async libraries like gevent Minimal attack surface for writing secure APIs 100% code coverage with a comprehensive test suite Only depends on six and mimeparse Python 2.6, 2.7, 3.3, 3.4 + PyPy please ensure you have added new tests and updated existing ones as appropriate. We require 100% code coverage. Also, please ensure your coding style follows PEP 8 and doesn’t make pyflakes sad. Additional Resource responders set response variables to sane values. 2. Your code is well-tested, with high code coverage. 3. Errors are anticipated, detected, and handled appropriately within each responder and with

great with async libraries like gevent Minimal attack surface for writing secure APIs 100% code coverage with a comprehensive test suite Only depends on six and mimeparse Supports Python 2.6, 2.7, 3.3 major version increment. The code is rigorously tested with numerous inputs and we require 100% coverage at all times. Six and mimeparse are the only third-party dependencies. Flexible. Falcon leaves testable. Tip Checking code coverage [https://coverage.readthedocs.io/] would have helped us detect the missing test above; it’s always a good idea to include coverage testing in your workflow to ensure

with async libraries like gevent • Minimal attack surface for writing secure APIs • 100% code coverage with a comprehensive test suite • No dependencies on other Python packages • Supports Python 3 major version increment. The code is rigorously tested with numerous inputs and we require 100% coverage at all times. Falcon does not depend on any external Python packages. Debuggable. Falcon eschews more flexible and testable. Tip: Checking code coverage would have helped us detect the missing test above; it’s always a good idea to include coverage testing in your workflow to ensure you don’t have

great with async libraries like gevent Minimal attack surface for writing secure APIs 100% code coverage with a comprehensive test suite Only depends on six and mimeparse Supports Python 2.6, 2.7, 3.3 Resource responders set response variables to sane values. 2. Your code is well-tested, with high code coverage. 3. Errors are anticipated, detected, and handled appropriately within each responder and with testable. Tip Checking code coverage [https://coverage.readthedocs.io/] would have helped us detect the missing test above; it’s always a good idea to include coverage testing in your workflow to ensure