Skip to content

Conversation

@bshaffer
Copy link
Contributor

No description provided.

@bshaffer bshaffer force-pushed the gce-logging branch 3 times, most recently from 59986d4 to e49b01d Compare April 14, 2016 20:38
@tmatsuo
Copy link
Contributor

tmatsuo commented Apr 14, 2016

Is it worthwhile to add a test?

@bshaffer
Copy link
Contributor Author

Yeah, I'll add a mock test

@bshaffer
Copy link
Contributor Author

@tmatsuo PTAL

-->
<phpunit bootstrap="test/bootstrap.php">
<testsuites>
<testsuite name="PHP twilio test">
Copy link
Contributor

Choose a reason for hiding this comment

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

Name: PHP GCE logging test

</testsuites>
<logging>
<log type="coverage-clover" target="../../../build/logs/clover-gce-logging.xml"/>
</logging>
Copy link
Contributor

Choose a reason for hiding this comment

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

add whitelist

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think I need to whitelist anything, since there's only index.php, which gets tested.

Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry for not explaining why. We should mark which files to measure the coverage. Otherwise phpunit thinks it should measure the coverage for everything including under vendor directory and we'll have very low coverage report :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I noticed there was a 30% decrease in coverage without this

Whitelist has been added!

@tmatsuo
Copy link
Contributor

tmatsuo commented Apr 15, 2016

LGTM

@coveralls
Copy link

Coverage Status

Coverage remained the same at 86.822% when pulling f718720 on gce-logging into 5f2d7f7 on master.

</testsuite>
</testsuites>
<logging>
<log type="coverage-clover" target="../../../build/logs/clover-gce-logging.xml"/>
Copy link
Contributor

Choose a reason for hiding this comment

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

I think it should be ../../build/logs/clover-gce-logging.xml.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ahh darn, good catch

@tmatsuo
Copy link
Contributor

tmatsuo commented Apr 15, 2016

Oh wait. The compute/index.php is not in the list on coveralls.

Probably because it uses a wrong clover log file path.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.1%) to 86.957% when pulling 784bbc5 on gce-logging into 5f2d7f7 on master.

@tmatsuo
Copy link
Contributor

tmatsuo commented Apr 15, 2016

LGTM
I'm wondering though we should make the coverage repirt mechanism more
robust. The current way is a bit error prone.

On Fri, Apr 15, 2016, 1:22 PM Coveralls [email protected] wrote:

[image: Coverage Status] https://coveralls.io/builds/5808282

Coverage increased (+0.1%) to 86.957% when pulling 784bbc5
784bbc5
on gce-logging
into 5f2d7f7
5f2d7f7
on master
.


You are receiving this because you were mentioned.

Reply to this email directly or view it on GitHub
#59 (comment)

@bshaffer bshaffer merged commit 64e332d into master Apr 15, 2016
@bshaffer bshaffer deleted the gce-logging branch April 15, 2016 20:30
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.

3 participants