Timeline for Print a nice Latex table from an array of values
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 15, 2019 at 15:21 | comment | added | IEatBagels |
@Graipher Oops yes, obviously if your testing framework works with method prefixed with test_, you should put this. The book in question was for C#, but the point still stands. I understand your point about the output, but if your unit tests were executed by an external tool, it might be easier to just see which test failed instead of having to "dig" through multiple outputs. It also makes it easier to see what the test tests without having to read the code, which I think is great when it comes to seeing what's tested in the class.
|
|
| Aug 15, 2019 at 15:18 | comment | added | Graipher |
I always thought the methods need to start with test_ in order for unittest to automatically execute them? In addition, if a test fails, the input, the expected and the actual output are printed, so I see no need to also encode them in the method name
|
|
| Aug 15, 2019 at 14:56 | history | answered | IEatBagels | CC BY-SA 4.0 |