[SalesForce] Using Developer Console & Checkpoints to debug w/ unit tests

Is it really possible to use the dev console & checkpoints to effectively debug code via unit tests? It seems like it should be possible, but I've never gotten it to really work for me.

Here's my biggest problem: I have a class & a test class. The test class contains several test methods, all of which test basically the same code in the main class. Each tests a different scenario. Pretty common.

I set a checkpoint, on a line of code that should be run (at least once) as part of every test method. Then I run the test class.

Result: I get one and only one checkpoint result. IT does not indicate anywhere (AFAIK) which test method produced it.

Expected result (or desired result if this is gonna be workable at all): one checkpoint result per test method (or per execution of that line per test method), clearly indicating which test method produced it.

Is there any way to get to there from here?

(FWIW, there have been several other questions about this, but none that I've seen has addressed this.)

Thanks!

Best Answer

Only one checkpoint per line (up to 5 lines) can be gathered per apex execution. For example, if you put the checkpoint location in a loop, you will only get one and only one checkpoint for that line. You can modify the "iteration" value of the checkpoint, which will wait until the nth time that line has been executed before gathering the heap. There is a line in the apex log for when the checkpoint is recorded.

In your example, you can see what test method the checkpoint is in by searching for "HEAPDUMP" (or "HEAP_DUMP") in the apex log, then look at the "Stack" panel to see what test method your are in. If you want to look at the setup for another test method, change the iteration. I don't know if test methods are ran in order but, if they are, an iteration of 1 would be the first test, 2 would be the second, and so on.

Related Solutions

[SalesForce] Challenge with unit tests, mock callouts and running as a user

Having recently gone through this exercise, I'm not certain that you're properly creating the communities portal user. From what you posted of the code above, you first need an owner for the account.

// THIS FAILS - because we try to run as a user we create
 @isTest static void testCalloutWithRunAsCreatedUser() {

Are you already using RunAs at this point? If so, did you specify a UserRoleId and ProfileId for the User? The Portal User essentially needs the UserRoleId of the User that creates him/her since a Communities Portal User has no Role. The Account and the Contact are both owned by the User who creates them, thus the need for the RunAs which it appears as though you already know.

 account a = new account(name = 'test acct');
 insert a;
 contact c = new contact(lastname = 'test', accountid = a.id);
 insert c;
 profile p = [select id from profile limit 1];
 user u = new User(alias = 'person', email='guest@testpkg.com',
                 emailencodingkey='UTF-8', firstname='Test', lastname='Person', languagelocalekey='en_US',
                 localesidkey='en_US', profileid = p.id,
                 timezonesidkey='America/Los_Angeles', username='guest@testpkg.com');
insert u;

The explanation I just gave is why the above would fail if User u is the RunAs User. If they're the Communities Portal User, the ProfileId for the Communities Guest User needs to have that particular license associated with it, not just any ProfileId.

One caveat is that any org can change the default ProfileName related to a License by cloning it when they create the Profile they intend to actually use, but for your purposes of a developer's test class, using the default name for a Communities Portal Profile/license in your query should be no problem and it could very well resolve your problem.

[SalesForce] Checkpoints not showing in Developer Console

I have observed that sometimes it takes more than 10 seconds to refresh but it worked correctly for me.

It may be performance degradation issue on your instance.

From the image your shared everything looks right from your side.

May be you can try waiting for longer time or raise a support ticket.

Best Answer

Related Solutions

[SalesForce] Challenge with unit tests, mock callouts and running as a user

[SalesForce] Checkpoints not showing in Developer Console

Related Topic