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

Add #626 coverage generation from phpunit #7

Merged
merged 5 commits into from
Jun 12, 2019
Merged

Conversation

ttibensky
Copy link
Collaborator

@ttibensky ttibensky commented Apr 4, 2019

we need to upload the artifacts somewhere regarding to https://docs.travis-ci.com/user/uploading-artifacts/

or we can use alternative service instead of travis, for example https://circleci.com/ which is free if we use a single parallel container + you can upload and review artifacts there

we could also probably use following code analysis tools all of which can be configured to fail the travis build:

  • phpmd ./vendor/bin/phpmd ./src html codesize,unusedcode --reportfile ./coverage/phpmd.html - generates html report
  • phpmd ./vendor/bin/phpcs src --generator=HTML > ./coverage/phpcs.html - generates html report
  • phpstan vendor/bin/phpstan analyse src tests --memory-limit=-1 --error-format=table prints issues which would cause a fatal error
  • other tools can be viewed here https://web-techno.net/code-quality-check-tools-php/

@ttibensky ttibensky added the wip work in progress label Apr 5, 2019
@ttibensky ttibensky changed the title Add coverage generation from phpunit Add #626 coverage generation from phpunit Apr 5, 2019
@ttibensky ttibensky removed the wip work in progress label Jun 12, 2019
@ttibensky ttibensky changed the base branch from master to develop June 12, 2019 09:39
@ttibensky ttibensky merged commit f967dca into develop Jun 12, 2019
@ttibensky ttibensky deleted the issue-coverage branch June 12, 2019 09:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant