function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion

Problems Deploying New Trigger Via Eclipse Toolkit

Hey all,
With Apex now being available in EE, some new opportunities have opened to address requests from my users.

One of them is fairly straightforward - my users would like to see a contacts cellular number automatically populated on the task record - this would prevent them from needing to toggle back to the Contact record.

I played around in my DE account and got it working A-OK.  All good.

However, when I go to deploy the code via Eclipse to my prod environment, I get the message about coverage:
"Copy_Contact_Cell_and_Mobile_To_Task_Record Test coverage of selected Apex Trigger is 0%, at least 1% test coverage is required
  Test coverage of selected Apex Class and Trigger is 0%, at least 75% test coverage is required"

I've read some of the other posts referring to the Code preview doc and the PDF overview of the, but my ignorant, non-programmer mind is struggling to make any headway in correcting the error.

I've enclosed my code below.  Am I missing something easy?  Or is this much more complicated in Production than it is in Dev.

Any guidance would be appreciated..
trigger Copy_Contact_Cell_and_Mobile_To_Task_Record on Task (after insert) 
Id ContactIDOnTheTask;
String contactCellNumber;
String contactPhone2;
    for (Task TReadOnly :
if (TReadOnly.RecordTypeID == '0123000000005z2')//Limit Code to only FID Tasks
        Task t = [select Id, WhoID from Task where Id = :TReadOnly.Id  limit 1]; //get ContactID
ContactIDOnTheTask= t.WhoID;
Contact[] phoneValueArray = [Select c.Id,c.mobilePhone,c.Phone_2__c from Contact c 
where c.Id = :ContactIDOnTheTask limit 1]; 
for(Integer i=0;i<phoneValueArray.size();i++)
contactCellNumber = phoneValueArray[0].mobilePhone;  //grab mobile number from array
contactPhone2 = phoneValueArray[0].Phone_2__c;  //grab phone2 number from array
t.Mobile__c = contactCellNumber;  //set mobile custom field on task to the contact mobile number
t.Phone2__c = contactPhone2;  //set phone2 custom field on task to contact phone2 number
  update t;


I've found some other posts on this topic, and I think I'm making some progress.  But, there is still one area that I'm confused on.

I beleive that I need to create the test method that will ultimatley kick off my trigger code. From looking at some other examples, I beleive the general gist of the TestMethod is below.

However - how do I introduce this code?  Is it entered as a separate class?  Or do I append it to the code for my trigger?

It feels that if I introduce them separately that they will both fail.
Am I totally off base?

public static testMethod void testCascade() {
 // Create two Tasks for test
   Task1 t1 = new task(Subject='Task1Test', WhoID = 'ContactIDforContact1',ActivityDate = 'Today');
   insert t1;
 Task2 t2 = new task(Subject='Task2Test', WhoID = 'ContactIDforContact2',ActivityDate = 'Today');
 insert t2;  

 //Get the new tasks(s)
 //assert the cell and phone 2 field on the task are the same as what is
on the contact record. --WriteCodeToCompareMobileNumberOnContactToMobileNumberOTask-- }

 --Code borrowed from MTBClimber.  He wrote it much better, is not at all representative of what he/she produced and is only representative at the moment.

Message Edited by RK on 01-07-2008 06:00 AM

Message Edited by RK on 01-07-2008 11:24 PM
So I think that I'm getting closer..

From what I can tell, the test method needs to be a separate class, and it and the trigger need to be validated simultaneously.

I'm still struggling to get appropiate coverage.  I stil feel as if my trigger code is sound, just can't get the TestMethod code proper.

More as I let my frustration dissipate...

I just want to reply to say that you are not being ignored. I understand that the testing requirement is not something a lot of salesforce users are accustomed to, and I'll work on documenting this in the future.

There is no code testing requirements for DE, which is why you didn't have that problem in that org.
Thanks for the reply.  And I didn't think that it was being ignored.  I realize that I'm asking what is a very basic to those who are experienced in general programming. 

Unfortunately, I am not experienced, and my job will probably never allow me the opportunity to be (because of other priorities).

I'm glad to hear that there is a plan to document this a bit will most likely help people like me.

I do have two requests as you are in the process of creating the documentation , and they are again very basic.

1.  Am I barking up the right tree about the fact that the TestMethods need to be entered into a separate class and then uploaded/deployed at the same time as the trigger?
2.  Would it be possible, as simplistic as it might be, to get sample of what the TestMethod would look like for the HelloWorld application, as contained on pages 56-58 in the cookbook?  A simple example like that would help my non-programming mind visualize what is hapening a bit easier than some of the longer ones in the cookbook.

Thanks again,

Message Edited by RK on 01-08-2008 12:01 PM
Do you have the Apex Developer's Guide? There is a testMethod for the HelloWorld sample on page 19. You  can find this developer's guide in the online help. Click Help &Training and search, you'll find it.
Ah...Not sure how I missed that.

Thanks for passing it along...will see what I can take away from it.