forevermatt / readable-unit-tests-php Goto Github PK

This will probably also require changing how I write output to the console during tests, so that progress can be written out, but an exception still thrown for a failure (without losing the console output).

As of version 0.1.0, all the console output is returned as a string, so the run-tests.php file's code doesn't actually know whether things passed or failed. It will need to in order to return an appropriate exit code.

https://github.com/nikic/PHP-Parser

Rather than indicating that the tests failed when some files lack tests, simply indicate that and keep going. Otherwise, we'll have a lot of basically-empty test files, which is no better than not having the tests.

Ideas:

• Replace "Feature: Description of feature" (in the Gherkin file) with "Class: \namespaced\Class".

Rather than having to re-invent the wheel, figure out how to use existing Behat code to do all the parsing of Gherkin files so that we can use things like Scenario Outline and Examples.

Unfortunately, I haven't figured out yet how to use Behat's classes to accomplish this. Can someone give me some pointers in how to get started?

For a Gherkin step that has a string in quotes, the contents of the quotes end up as part of the expected method name, rather than as arguments to the method the way they should.

Use this to write unit tests for itself

See Keep a Changelog