Closed cordoval closed 10 years ago
first time i see a test marked as risky:
~ php bin/phpunit -c phpunit.xml tests --debug Luiss-MacBook-Pro-3 [3:13:15]
PHPUnit 4.1.4 by Sebastian Bergmann.
Configuration read from /Users/cordoval/Sites/ddd/deps/event-centric/EventCentric.Core/phpunit.xml
................................R....
Time: 198 ms, Memory: 7.00Mb
OK, but incomplete, skipped, or risky tests!
Tests: 37, Assertions: 82, Risky: 1.
Thanks Luis. This PR breaks the build. It's also a mess, lots of different things mixed within the same PR, and even within the same commit. Please send 1 PR per problem. If you can't state a problem, don't send a PR.
Commits like this do not solve any problem:
-final class ConventionalCommandHandlingTest extends \PHPUnit_Framework_TestCase
+final class ConventionalCommandHandlingTest extends PHPUnit_Framework_TestCase
Closing.
the problem i see is consistency. It is ok though, i don't send this PRs just to contribute but also to read and review code and provide some feedback. I also noticed you set your phpstorm to template for class to display final by default which is interesting, so i learn from that. However it also has some spaces at the end of the classes that is just weird.
Also the break on the build is only on hhvm which is a bit weird. https://travis-ci.org/event-centric/EventCentric.Core/jobs/31309611 . So in reality the dependency can be lowered without problems.
HHVM support is essential.
"Consistency" is not a problem statement, it's a potential solution to some other (perceived) problem. "High cognitive load when reading the code" can be a problem, and that problem can partially be solved by increasing consistency. However, the example above, or the number of spaces at the end of a class, have zero effect on readability.
yes that "effect on readability" is somewhat subjective and i get you too. So no worries. To me is good to have good cs and "consistency" as in the PR. Some of my neuroscience :blush: reasoning but that is too long to explain. Is cool.
Sent with Gush