Hi Chris, 


Hope this solves the puzzle. 

Apex test class to simulate two users !
Create an Apex test class that tries to simulate the same using System.runAs().

My use case(scenario) was to create a test method in this class that :

Creates an account from the logged in user.
Query that same account back using “for update”.
Start new context using “System.runAs()” from some other user i.e. not the logged in user.
Try updating the same locked account, using that other simulation user.
Here is the apex test class, if you want to experiment.


public class TestRecordLocking {
  testmethod public static void testLocking() {
    // create a account from logged in user
    Account accoutU1 = new Account(Name = 'Abhinav Gupta');
    insert accoutU1;
    // lock the same account  
    accoutU1 = [Select Id, Name, Website from Account where Id =:accoutU1.id for update];
    
    //Start updating it
    accoutU1.website = 'www.salesforce.com';
    
    // Now lets say, some other user comes and tries to update the same record
    User u2 = [Select Id from user where id !=:UserInfo.getUserId() limit 1];
    System.runAs(u2) {
      // other user queries the same account
      Account accountU2 = [Select Id, Name, Website from Account where Id =:accoutU1.id ];
      // other user tries to update it
      accountU2.WebSite = 'www.yahoo.com';
      update accountU2;    
    }
    
    // Now update the original account back.
    update accoutU1;  
  }
}
Expected Result on Executing this Apex Test ?
It should fail, isn’t ? As I am trying to update record locked by some other user. Unfortunately it works like a charm. I believe, System.runAs() is not creating exact multi user context that might be created in real life ?

http://www.tgerm.com/2011/04/visualizing-record-locking-in-soql-ie.html


Regards,
Ashish