-
Notifications
You must be signed in to change notification settings - Fork 3k
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
locust/test/test_average.py present but never run #85
Comments
Ah, good find. I'm no sure. From the comments in test_average.py, it says that the tests might fail (due to randomness). What is the likelihood of them failing? If it's possible to modify them so that the likelihood is extremely small (to the point where they're almost deterministic in practice, while still testing something useful), I think the working one would be great :). |
After a brief test I conclude that it'll fail relatively often. Maybe 10-20% of the time. Certainly way to much to be enabled in trunk as it is. |
I enabled test_average for now in #86 but I agree that the test should be reworked to only fail or succeed without the current randomness. Still I think having a test is better than no one. |
Well I'll close this case anyway. It's misleading as it is, as those tests are being run in trunk after @EnTeQuAk 's branch |
Consequently it fails in trunk. I suspect it's probably been failing for a long time. There's not much point in having a test suite if it never runs, it just confuses people like me, when they happen to use another test runner and notice that tests are failing in trunk ;)
I have a branch that kills that file and also one that makes it work. Which would you rather?
The text was updated successfully, but these errors were encountered: