[SalesForce] Test Class – Error: Compile Error: Field is not writeable: Opportunity.ConnectionReceivedId

I have a re-parenting trigger that fires if the connectionReceivedId is of a certain value. The sad part is that it looks like that field is not writeable, so testing is not possible. I know I could rewrite the trigger to work around this, but I would enjoy being able to actually sort records needing re-parenting by the connection from which they were received.

@istest
public class reparenttestclass{
static testmethod void reparenttestclassmethod(){

Opportunity testopp = new Opportunity(
name = 'testopp', recordTypeId = 'xxxxxxxxxx', connectionReceivedId = 'testconnid', AccountId = 'xxxxxxxxxxx', CloseDate = Date.newInstance(2009, 3, 11), StageName = 'testopp');
insert testopp;

Account testacct = new Account(
name = 'testacct');
insert testacct;

}}

Best Answer

To test things like this, I create a class that mimics the object. During the test I deserialize the class into a list of those objects. In the code that the trigger calls, I check for a static test property to be true and if so then get the test objects instead of database object. It allows you to test the functionality of that piece (sorting, etc) while being able to control the testing of actual database records for other tests.

An example (a bit abstract) of how to deserialize a class to get an sObject that can be used in your code:

Public class parentClassTest{
  public static useTestObject = false;

  public static test method void doTest(){
        useTestObject = true;

        //insert records to cause trigger to fire
  }

  public static Opportunity[] getTestOpps(){
      mytestClass[] tmp = new MyTestClass[]{};
      //populate with records
      return (Opportunity[])json.deserialize(json.serialize(New myTestClass()),List<Opportunity>.class);
  }
public class myTestClass{

    public id id {get;set;}
    public String name {get;set;}
    public Id connectionReceivedId {get;set;}

    public mytestClass(){
        name = 'test';
    }

}

In your code you would:

Opportunity[] o = parentClassTest.useTestObject ? parentTestClass.getTestOpps() : TRIGGERVALUES;

Related Solutions

[SalesForce] Unit Test is Providing 0% Coverage for Apex Trigger

The trigger code is having lot of redundancy, So I modified it. before posting the modified code few lines of explanation what I changed. you collected account Ids twice and did the condition check twice where once is more enough. I am also made changes to the test class, where Task data is provided which is not required because the trigger has to create it once the necessary conditions are met. I am expecting this trigger should work for you, if there is any errors feel free to post as a comment.

trigger OpportunityAfter on Opportunity (after update){

    Set AccountIDs = new Set();

    for(Opportunity o : trigger.new){
        if(opp.StageName == 'Closed - Lost' && opp.Business_Line__c == 'Workforce' && 
            opp.Survey_Type__c != 'APulse' && trigger.oldMap.get(opp.Id).StageName != opp.StageName){

                AccountIDs.add(o.AccountId);
         }
    }

    Task[] tasksToInsert = new Task[]{};

    for (Account acc : [Select Id, Name, OwnerId from Account where Id IN :AccountIds]){
        for (Opportunity opp : trigger.new){
            if(opp.AccountId == acc.Id){
                Task tas = new Task();
                tas.WhatId=acc.Id;
                tas.OwnerId=opp.OwnerId;
                tas.Subject='Follow-up: ' + opp.name + ' - ' + acc.name;
                tas.ActivityDate=(opp.CloseDate + 180);
                tas.Description='Follow up to see how engagement initiatives are going and if Avatar can help. Refer to lost opportunity: ' + opp.name;
                tasksToInsert.add(tas);                                                         
            }
        }
    }
    if(tasksToInsert != null && !tasksToInsert.isEmpty())
    Database.insert(tasksToInsert);

}

@isTest
public class TestClass {

    static testMethod void myUnitTest() {

    //Set up user
    User u1 = [SELECT Id FROM User WHERE Email='abc@sampleemail.com'];
    test.startTest();  
    //Run As U1
    System.RunAs(u1){

    System.debug('Testing trigger... (single record validation)');

    //NEW Account record
    Account acc = new account();
    acc.Name = 'Test Account';
    acc.Industry = 'Healthcare';

    insert acc;

    //NEW Opportunity record
    Opportunity opp = new Opportunity();
    opp.Name = 'Test Opportunity'; 
    opp.CloseDate = System.today();
    opp.StageName = 'S1 - Investigative';
    opp.Type = 'Repeat Business - Wrkforce HC';
    opp.AccountId = acc.Id;
    opp.Survey_Type__c = 'Product Name';

    insert opp;

    opp.StageName = 'Closed - Lost';
    opp.Reason_Won_Lost__c = 'Relationship';
    opp.Business_Line__c = 'Workforce'  //added this line to meet the if condition while collecting the set of id in the trigger.

    update opp;
   test.stopTest();
    // Here I am expecting the task has been inserted and doing a query for it         and check it in the assert statement.
   Task  testTask=[Select Id, WhatId from Task where WhatId=:acc.Id];
    //Validate single insert
    System.assertEquals(acc.Id, testTask.WhatId);

    }
    }
}

[SalesForce] Test class error – Field is not writeable: OpportunityPartner.OpportunityId

OpportunityPartner records are read-only and are created automatically by Salesforce

when a Partner object is created for a partner relationship between an account and an opportunity.

Creating an Account-Opportunity Partner Relationship

When you create a partner relationship between an account and an opportunity (when you create a Partner object and specify the OpportunityId field), the API automatically creates an OpportunityPartner with the corresponding values:

The value of the Partner field AccountToId maps to the value of the OpportunityPartner field AccountToId.

The values of the OpportunityId, Role, and IsPrimary fields in both objects are the same.

If you set the IsPrimary value to 1 (true) upon insert of a new OpportunityPartner, any other existing primary partners for that opportunity will automatically have the IsPrimary value set to 0 (false).

Also, they share the 00I keyprefix with Partner. As such, I tend to think of them as a specialised view over Partner.

So you shouldn't need to explicitly insert the record during a test case. The Partner object that you insert will have accountToId to an Account and opportunityId to an Opportunity on a different Account.

Best Answer

Related Solutions

[SalesForce] Unit Test is Providing 0% Coverage for Apex Trigger

[SalesForce] Test class error – Field is not writeable: OpportunityPartner.OpportunityId

Creating an Account-Opportunity Partner Relationship

Related Topic