Timeline for Should you unit test order of operations? If so, how?
Current License: CC BY-SA 3.0
15 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 10, 2017 at 20:41 | history | edited | amon | CC BY-SA 3.0 |
added syntax highlighting; made code more compact – it just serves as an illustration
|
Nov 10, 2017 at 19:12 | history | tweeted | twitter.com/StackSoftEng/status/929064311930195969 | ||
Nov 10, 2017 at 16:25 | comment | added | Frank Hileman | @DocBrown True, but if extreme or precise enough, such a test can be done, satisfies the goal, and other performance problems will be uncovered as well. | |
Nov 10, 2017 at 16:24 | comment | added | Matthew | This doesn't answer the question you have (regarding knowing whether your method was called), but I can see a use case where the caller would want to know whether it was a fuzzy match or not. | |
Nov 10, 2017 at 13:27 | answer | added | JacquesB | timeline score: 1 | |
Nov 10, 2017 at 13:21 | comment | added | Doc Brown | @FrankHileman: unit tests for performance tend to become brittle, since they depend on the hardware involved. For this case, there are better alternatives. | |
Nov 10, 2017 at 10:58 | answer | added | Doc Brown | timeline score: 6 | |
Nov 10, 2017 at 9:06 | vote | accept | Bob Tway | ||
Nov 10, 2017 at 0:32 | comment | added | Frank Hileman | If you are concerned about performance, why not write a test for that instead? | |
Nov 9, 2017 at 20:52 | answer | added | Stop harming Monica | timeline score: 5 | |
Nov 9, 2017 at 18:04 | answer | added | kevin cline | timeline score: 11 | |
Nov 9, 2017 at 17:38 | comment | added | Eternal21 | Most mock frameworks have that functionality. For example: alastairchristian.com/… | |
Nov 9, 2017 at 17:29 | comment | added | Robert Harvey | This is also a good reason to put some comments in the public method that explain why the private methods are being called in a specific order. | |
Nov 9, 2017 at 17:27 | comment | added | Robert Harvey |
You're describing a functional requirement (public method must execute in x time) that can be tested with another unit test, given some assumptions about the hardware you're running the tests on.
|
|
Nov 9, 2017 at 17:23 | history | asked | Bob Tway | CC BY-SA 3.0 |