Timeline for Avoiding triggers/flows on managed objects during Apex testing
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 26, 2016 at 17:34 | comment | added | Egor | This is for a CPQ engine, so it has some pretty complicated relationships with products, quotes, prices, proposals, options, etc. We talked about it as a team and the decision was to modify the controller to not do DML when it's being tested. Ugly as sin, but it was quick and easy, and the controller is quite small. We didn't want to invest too much time into something we may (hopefully) not need again. | |
| Jul 26, 2016 at 1:12 | comment | added | Eric | you hit the nail on the head (as always). Try doing this for FinancialForce Accounting (record, groups, queues, setup and non setup objects, oh my). What a process that was...... | |
| Jul 25, 2016 at 22:11 | history | answered | sfdcfox♦ | CC BY-SA 3.0 |