Timeline for Reusing array with static test data across test classes
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 16, 2015 at 11:31 | comment | added | jbailie1991 | @DocBrown I wasn't expecting someone to make the decision for me, I was seeking advice/guidance not hand holding | |
| Dec 14, 2015 at 12:29 | comment | added | Doc Brown | @jbailie1991: finding the right balance is up to someone who knows the code, the data and the test requirements, so in short it is up to you. Do not expect someone here to make this decision for you. | |
| Dec 14, 2015 at 12:22 | comment | added | jbailie1991 | So for my vcase, the array initialisations would be extracted out but any manipulation of the arrays would happen in the test classes. If the array needs to differ from the shared one then it can be initialised and altered in the test or a different array can be initalised in the test instead. Would that be considered a balanced approach? | |
| Dec 14, 2015 at 12:07 | history | answered | amon | CC BY-SA 3.0 |