Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow user to specify level for Fixer #7

Open
triopter opened this issue Oct 20, 2014 · 2 comments
Open

Allow user to specify level for Fixer #7

triopter opened this issue Oct 20, 2014 · 2 comments

Comments

@triopter
Copy link

i.e. artisan inspect:fix --level=psr-2

Thanks for all your work on this project -- it's a lifesaver!

@brodkin
Copy link
Member

brodkin commented Oct 20, 2014

This is a good idea, but I don't know when I'll have time to implement new features on this project. I'll accept a PR if anyone is interested.

@triopter
Copy link
Author

This may be a silly question, but can you please provide more in-depth guidance on running the unit tests?

I've got the package installed in the context of a Laravel application (and artisan inspect:<whatever> commands work. I can run the application test suite, but running phpunit vandor/bca/laravel-inspect/tests results in an error (looks like some sort of problem with autoloading only in the context of the test suite).

Fatal error: Class 'BCA\LaravelInspect\Tests\InspectCommandTestCase' not found in /home/vagrant/src/Oyster/workbench/bca/laravel-inspect/tests/InspectFixCommandTest.php on line 22

Call Stack:
    0.0008     225824   1. {main}() /home/vagrant/src/Oyster/vendor/phpunit/phpunit/phpunit:0
    0.0483    1392456   2. PHPUnit_TextUI_Command::main() /home/vagrant/src/Oyster/vendor/phpunit/phpunit/phpunit:56
    0.0483    1393080   3. PHPUnit_TextUI_Command->run() /home/vagrant/src/Oyster/vendor/phpunit/phpunit/src/TextUI/Command.php:138
    0.0483    1395696   4. PHPUnit_TextUI_Command->handleArguments() /home/vagrant/src/Oyster/vendor/phpunit/phpunit/src/TextUI/Command.php:148
    0.1777    2720360   5. PHPUnit_Util_Configuration->getTestSuiteConfiguration() /home/vagrant/src/Oyster/vendor/phpunit/phpunit/src/TextUI/Command.php:696
    0.2298    4424904   6. PHPUnit_Util_Configuration->getTestSuite() /home/vagrant/src/Oyster/vendor/phpunit/phpunit/src/Util/Configuration.php:845
    0.2819    4427704   7. PHPUnit_Framework_TestSuite->addTestFiles() /home/vagrant/src/Oyster/vendor/phpunit/phpunit/src/Util/Configuration.php:924
    0.2819    4428512   8. PHPUnit_Framework_TestSuite->addTestFile() /home/vagrant/src/Oyster/vendor/phpunit/phpunit/src/Framework/TestSuite.php:435
    0.2824    4467808   9. PHPUnit_Util_Fileloader::checkAndLoad() /home/vagrant/src/Oyster/vendor/phpunit/phpunit/src/Framework/TestSuite.php:363
    0.2836    4467960  10. PHPUnit_Util_Fileloader::load() /home/vagrant/src/Oyster/vendor/phpunit/phpunit/src/Util/Fileloader.php:77
    0.2862    4472216  11. include_once('/home/vagrant/src/Oyster/workbench/bca/laravel-inspect/tests/InspectFixCommandTest.php') /home/vagrant/src/Oyster/vendor/phpunit/phpunit/src/Util/Fileloader.php:93

I can't find any information online on how to install an existing package in the workbench (as opposed to creating a new package) and my feeble attempt didn't accomplish anything installing as a vendor package doesn't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants