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 telemetetry call via eval + setup test for it #786

Merged
merged 2 commits into from
Mar 7, 2018

Conversation

aebadirad
Copy link
Contributor

No description provided.

@@ -21,12 +21,19 @@
import static org.junit.Assert.assertTrue;

public class DataHubInstallTest extends HubTestBase {
private static int afterTelemetryInstallCount = 0;
Copy link
Contributor

Choose a reason for hiding this comment

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

A bunch of our tests call installHub. What if one of the other test classes runs before this one? Wouldn't it be better to check getTelemtryInstallCount before and after the install and look for the +1?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There's no +1. It only stores the count until it transmits it, then dumps it, usually within 30 seconds. I'm more concerned the check won't pass if a machine is a bit slow at running the tests - as it'll show null instead of 1.

eval.xquery(query).eval().close();
}
catch(FailedRequestException e) {
logger.error("Failed to increment feature metric telementry count: " + query, e);
Copy link
Contributor

Choose a reason for hiding this comment

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

(minor) typo: "telementry" -> "telemetry"

@aebadirad aebadirad merged commit ad6b7cb into develop Mar 7, 2018
@aebadirad aebadirad deleted the feature/Telemetry_counter branch March 7, 2018 17:38
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.

2 participants