Timeline for Should one test the values of an enum using unit tests?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 29, 2017 at 6:26 | history | edited | JacquesB | CC BY-SA 3.0 |
deleted 114 characters in body
|
| Sep 27, 2017 at 16:20 | history | edited | JacquesB | CC BY-SA 3.0 |
added 37 characters in body
|
| Sep 27, 2017 at 15:56 | history | edited | JacquesB | CC BY-SA 3.0 |
added 5 characters in body
|
| Sep 27, 2017 at 15:47 | history | edited | JacquesB | CC BY-SA 3.0 |
added 19 characters in body
|
| Sep 27, 2017 at 15:33 | history | edited | JacquesB | CC BY-SA 3.0 |
added 19 characters in body
|
| Sep 27, 2017 at 15:19 | comment | added | JacquesB | @IS1_SO: Are you talking about testing an enum instance returned from a function has a certain expected value? Because yes you could test that. You just don't need to test the enum declaration itself. | |
| Sep 27, 2017 at 15:10 | comment | added | IS1_SO | No. What I meant is that in this case the language construct selected to represent the values is an enum. But as we know that is an implementation detail. What happens if one selects an array, or a Set<> (in Java) or a string with some separation tokens to represent the values? If that is the case then it would make sense to test that the values contained are the ones of interest to the business. That is my point. Does this explanation help? | |
| Sep 27, 2017 at 15:05 | comment | added | JacquesB | @IS1_SO: OK that confuses me - are you dynamically generating the enum values, or what is happening? | |
| Sep 27, 2017 at 15:03 | comment | added | IS1_SO | I have updated my question in an effort to address this answer, check it out to see if that helps. | |
| Sep 27, 2017 at 15:02 | history | edited | JacquesB | CC BY-SA 3.0 |
added 380 characters in body
|
| Sep 27, 2017 at 14:53 | history | answered | JacquesB | CC BY-SA 3.0 |