I'm brand new to Apex/Salesforce development, and am attempting to create some Apex triggers and tests. Each time I try to add a new class, when I start it with @IsTest I am unable to save it. I see the error: "Error: Compile Error: unexpected token: @ at line 1 column 0".
Is there somewhere else I'm supposed to put tests for triggers? Or something else I should be doing?
Thanks.
Triggers can't have annotations, and while they can contain classes, those classes can't be "special" classes, such as @RestResource classes. You need to make a class to test the trigger. Do not confuse a class with a trigger. A trigger looks like a class, but has different semantics.
The following code won't compile:
@isTest trigger MyTrigger on Case (after insert) { ...
Nor will this:
trigger MyTrigger on Case (after insert) {
@isTest class TestTrigger { ...
Instead, make your trigger:
trigger X on Y (...) { ...
And a class for that trigger:
@isTest class TestTriggerX {
@isTest static void testTrigger() { ...
Classes are made in Setup > Develop > Apex Classes, while triggers are made on the object (e.g. Setup > Customize > Accounts > Triggers). The word "class" generally should never appear in your triggers, and the word "trigger" should generally never appear in your classes.
You can't combine multiple top-level elements into a single class or trigger.
@isTest class CheckLead_Test { static testMethod void insertNewLead() {
Commented
Oct 15, 2014 at 12:45
In case other folks find this one, the problem was with the Developer Console (at least in our case it was). I was unable to create new test classes in there, but instead had to install Eclipse and Force.com package and deploy from there.
To be clear, I can run tests in Developer Console, but have to create them in Eclipse.