Timeline for Unit Testing Batch Delete Class
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 19, 2018 at 15:48 | history | tweeted | twitter.com/StackSalesforce/status/965613967904333824 | ||
| Feb 19, 2018 at 15:17 | vote | accept | Curious Blueprints | ||
| Feb 19, 2018 at 14:45 | comment | added | David Reed |
The documentation is kind of cagey about where the actual transaction boundaries are with Test.{start, stop}Test() (it's described as resetting limits only), particularly when async jobs are submitted. Does the batch class execute in the same transaction as the FOR UPDATE?
|
|
| Feb 19, 2018 at 14:31 | answer | added | Adrian Larson♦ | timeline score: 0 | |
| Feb 19, 2018 at 14:20 | answer | added | Adrian Larson♦ | timeline score: 1 | |
| Feb 19, 2018 at 14:13 | comment | added | Curious Blueprints | I tried it in both places, just in case, this just happened to be the configuration when I asked the question. | |
| Feb 19, 2018 at 14:12 | comment | added | Adrian Larson♦ |
It's for the entirety of the transaction. If that strategy were to work you would have to call the query before Test.startTest.
|
|
| Feb 19, 2018 at 14:09 | history | asked | Curious Blueprints | CC BY-SA 3.0 |