Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • 7
    That test just fails, sometimes. martinfowler.com/articles/nonDeterminism.html Commented Dec 17, 2013 at 13:54
  • 2
    Thanks for that link. With that article in mind, I felt I needed to clarify that non-determinism means in the context of this test suite. Because data is selected randomly from a database, all data fed to the controller is valid data by default. This means that false negatives don't exist in the test suite when it comes to the non determinism. In a way, this randomness simulates a user selecting data 'at random' for use in a controller. This is not necessarily the same non-determinism the article discusses, right? Commented Dec 17, 2013 at 14:15
  • 3
    recommended reading: Why is asking a question on “best practice” a bad thing? Commented Dec 17, 2013 at 14:19
  • 16
    @DCKing: Consider what happens if your test fails. Okay, you have a bug. Uh, now what? Run it again in debug mode! Where it succeeds! Like it does the next hundred times you run it, and then you write off the issue as a cosmic ray strike. Non-determinisim in tests sounds absolutely unworkable. If you feel the need to cover more ground in your test cases, cover more ground. Initilise your RNG with a set seed and run the "test" a few hundred times with consistently random values. Commented Dec 17, 2013 at 14:35
  • 2
    (finally got around to a machine where I could properly search twitter - the "That test just fails sometimes" is from the #FiveWordTechHorrors on Twitter - wanted to properly credit it) Commented Dec 17, 2013 at 15:25