[SalesForce] How to run multiple test scenarios in one test code, for the Same APEX code

I have a previous question:

How to achieve ~100% code coverage with if-then-else statements?

I followed Peter Knolle advice and so far I have 90% coverage. I’m Just going through the code when I have time to reach the max coverage possible, but I ended up having multiple test codes for the same APEX code where each one represents a different scenario. Is it possible to add them up into one code?

For example [referring to the example in the link above] when I try adding up two test codes in one file, and I need to delete an account so I can change things in the account and then insert the new account,

It tells me that I have a duplicate record when I try to run:

System.assertEquals(null, retPageRef, 'PageReference returned should be null');

How can I delete the records completely? Using delete account does not seem to work

Best Answer

Depending on how complicated the terms of the if statement are I'd do different things.

If it's a simple switch based on some user input then doing it in one method is perfectly fine, if things are more complicated than that it's often easier to read and understand the test code when you have a method per scenario.

You can often write the tests for an entire controller in a single method, but it can get messy and test code is something you will always be coming back to in order to update and fix it as it depends on so many other factors; therefore it's code that you want to be as easy to maintain as possible, so let that guide your decision.

Your particular issues sound like issues with your test code and you should post that for help with it, but there's no reason why you shouldn't be able to delete the account you've created and inserted. Also, consider whether you need to delete it or if updating the record will be enough.

Related Solutions

[SalesForce] Create multiple users in APEX test coverage

I have solved this error:

Failure Message: "System.DmlException: Insert failed. First exception on row 0; first error: DUPLICATE_USERNAME, Duplicate Username.
Another user has already selected this username.
Please select another.: [Username]"

By creating this:

`String orgId = UserInfo.getOrganizationId();
 String dateString = String.valueof(Datetime.now()).replace('   ','').replace(':','').replace('-','');
 Integer randomInt = Integer.valueOf(math.rint(math.random()*1000000));
 String uniqueName = orgId + dateString + randomInt;`

And then I use this combination to obtain a unique username.

`Profile p = [select id FROM Profile WHERE Name ='Administrator'];

 User user1 = new User();
 user1.Username = uniqueName + '@test' + orgId + '.org';
 user1.Email = uniqueName + '@test' + orgId + '.org';
 user1.LastName = 'LastName1';
 user1.FirstName = 'FirstName1';
 user1.Alias = uniqueName.substring(18, 23);
 user1.CommunityNickname ='use1';
 user1.ProfileId =p.id;

 user1.EmailEncodingKey='UTF-8';
 user1.LanguageLocaleKey='en_US';
 user1.LocaleSidKey='en_US';
 user1.TimeZoneSidKey='America/Los_Angeles';
 user1.Country = 'US';
 user1.Title = 'Territory Manager';


insert user1;`

If I try to transfer my change set now I have no problems with the username. I repeat this for the second user but I created a second set of Integer radomInt and String uniqueName.

Integer randomInt2 = Integer.valueOf(math.rint(math.random()*2000000));

I notice that if I use the same randomInt for my second username the random composition of String uniqueName = orgId + dateString + randomInt; will be the same than the one for the first user and it's not unique.

But using String uniqueName2 = orgId + dateString + randomInt2; for the second user will works, creating a new username that is unique.

This is a solution. Any comments on this?

Edit 11-21-14

So far there is not problems and the code has been active for a few months. We are going to modify all test classes and add a test factory class to avoid issues like this one.

[SalesForce] Apex test code – system assert error

When testing workflow rules, you will need to wrap your insert DML in a startTest() and stopTest() method to ensure that the workflow rule has had time to finish processing prior to querying for the record. Since you can only have one startTest() and stopTest() method per unit test, you will likely need to breakout the delete scenario into a separate test method:

Test.startTest();
insert R;
Test.stopTest();

c1 = [SELECT Id, Roles__c FROM Contact WHERE Id=:c1.Id];
...

Best Answer

Related Solutions

[SalesForce] Create multiple users in APEX test coverage

[SalesForce] Apex test code – system assert error

Related Topic