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

codeception code coverage infos #5773

Merged
merged 5 commits into from Apr 24, 2018

Conversation

gymad
Copy link
Contributor

@gymad gymad commented Apr 23, 2018

Description

changing codeception.yml file to get correct coverage infos:
terminal command:
./vendor/bin/codecept run unit --coverage --coverage-html
output in:
path/to/SuiteCRM/tests/_output/coverage/index.html

Motivation and Context

measuring code coverage

How To Test This

see in decription

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Final checklist

  • My code follows the code style of this project found here.
  • My change requires a change to the documentation.
  • I have read the How to Contribute guidelines.

@gymad gymad changed the title Test coverage stage codection code coverage infos Apr 23, 2018
@gymad gymad changed the title codection code coverage infos codeception code coverage infos Apr 23, 2018
codeception.yml Outdated
- service/*
- soap/*
exclude:
- cache/*
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we exclude third party libraries from the code coverage?

@Dillon-Brown
Copy link
Contributor

Dillon-Brown commented Apr 24, 2018

Assessed

Approved with PullApprove

@Dillon-Brown Dillon-Brown merged commit 50a00db into salesagility:hotfix Apr 24, 2018
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.

None yet

4 participants