Pretty sure they could upgrade that at some point in a major version. As they have written a lot of tests in Magento 2, they probably stick with the version they used at the time they wrote the first tests in order not to break the tests. My guess is that, as Magento 2 development started a few years ago, the team used the library that were available at that time. Is there any reason why M2 use testing libs (PHPUnit and PHP_CS) from I'm just going to give you my thoughs about that, I may be wrong for some points but maybe it'll clarify some things: It looks like PHP_CS has already a simple wrapper for Gulp, but I'm not sure where configuration is stored. theme), not whole Magento 2 instance (CI tests)? How to run this type of tests when we have single module (i.e.Most of front-end tests in worst case take a few seconds, so there is no way to get live feedback about issues. Is there any reason why it's so slow? It take ~7-8 minutes to analyse template files.Is there any better reporter available or some other way to get a meaningful report, instead of something looking like a PHP backtrace? Is it normal that output of this test looks like a mess and it's hard to understand what and where something wrong happened? I compare it with output of code quality tests for CSS/JS and it's a nightmare.Is there any reason why M2 use testing libs (PHPUnit and PHP_CS) from 2014 instead of fresh one?.I'm not familiar with PHP testing libs / tools, so have few questions for you: I'm trying to add PHP Static test at Frontools to simplify and improve testing process and if it's possible increase performance, b/c it takes so long to get any results.
0 Comments
Leave a Reply. |