-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Add unit test execution commands #1157
base: release/next
Are you sure you want to change the base?
Add unit test execution commands #1157
Conversation
Co-authored-by: Michael Lehmkuhl <[email protected]> Co-authored-by: Jenyamba <[email protected]> Co-authored-by: Tu Van <[email protected]> Co-authored-by: Cid Lopes <[email protected]>
PR Summary
|
Hello @markshust I'm sure these commands simplify the use of unit tests. I added a new folder 'test' to the 'bin' folder. The general idea is to simplify and combine test scripts in one folder. I'm not sure if this approach aligns with your thoughts, but let's find the best place for it. Also, it works well with configured xdebug (as you configured it in the academy video). So potentially, it should work without any problems from scratch. |
@markshust Hello. Please check idea that I provided. |
The new pull of commands for simplifying unit test execution:
bin/test/unit
Usage:
bin/test/unit <unit_test_path>
Description: Run specific unit tests
bin/test/unit-coverage
Usage:
bin/test/unit-coverage <unit_test_path>
Description: Generate unit tests coverage report in the folder: dev/tests/unit/report
bin/test/unit-xdebug
Usage:
bin/test/unit-xdebug <unit_test_path>
Description: Run unit tests with xdebug (you need to turn on xdebug in IDE as usual). Works natively with configured xdebug within docker-magento.