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

Pipeline test #57

Closed
Antar1011 opened this issue Sep 27, 2016 · 4 comments · Fixed by #63
Closed

Pipeline test #57

Antar1011 opened this issue Sep 27, 2016 · 4 comments · Fixed by #63
Milestone

Comments

@Antar1011
Copy link
Owner

Write a test that verifies the correct operation of the entire pipeline, from collection to reporting.

It doesn't have to be a "diabolical" test--just testing normal, easy-to-validate operation is fine.

@Antar1011 Antar1011 added this to the 0.1 Release milestone Sep 27, 2016
@Antar1011
Copy link
Owner Author

In progress on integreation-test branch

@Antar1011
Copy link
Owner Author

#61 created a one-log integration test, but it also made clear the need for a bulk (say, 1k log) test. This one should just check that everything goes through without failing (that is, no need to try to produce an "expected" result)

@Antar1011
Copy link
Owner Author

Weirdly, there's some inconsistency to the results of the integration test (when it passes): it looks like it's randomly altering the baseline. I suspect the issue is the randomly-generated rprd for each player.

@Antar1011
Copy link
Owner Author

A-yup, that would be it--if rprd>100, the player will get dropped, which is what I'm seeing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant