Hi Dmitrij,
agree with you that the second question is subject to discussion.
With setup SP, below are the encounter challenges till now?
- As setup SP invoked before every Unit test - Have to maintain expected output every time for an un-touched unit test when any data modification inside setup SP as objects consumes common tables.
- Right now implemented unit test for around 50 SPs which consume 100+ tables[still adding] and will manage data for every table inside setup - However logically every table is not part of every Unit test but its invoke un-necessary data for all table every time which may lead to higher completion time.