Apex Code Development You need to sign in to do that
Don't have an account?
Bahri Yucesan Code Coverage Problem
Hi all , We have a serious problem about our Apex Classes. Approximately 5 days ago our all Apex Codes and all Apex Triggers start getting " 0% Code Coverage " error. Before that everythings are ok. But when we trying create new very basic Apex Class , then getting always same problem. We are deleted all Apex Classes and Apex Triggers but still getting same error. The Sample Code and Test Code as follows , How can we fix that coverage problem.
------------------------------
public class GunlukRaporlar {
static void Yap()
{
List<Account> allAcc = [select Id,Name from Account limit 5];
for(Account acc:allAcc)
{
String cc = acc.Industry;
}
String aa = 'bb';
}
}
------------------------------
---------- TEST -----------
@isTest
public with sharing class GunlukRaporlarTest {
static testMethod void testYap()
{
List<Account> accList = new List<Account>();
Account a = new Account();
a.Name='TESTACCOUNT';
a.Industry = 'Banka';
insert a;
accList.add(a);
System.assertEquals(accList[0].Industry, 'Banka');
}
}
-----------------------------
Thanks for all
King Regards.
------------------------------
public class GunlukRaporlar {
static void Yap()
{
List<Account> allAcc = [select Id,Name from Account limit 5];
for(Account acc:allAcc)
{
String cc = acc.Industry;
}
String aa = 'bb';
}
}
------------------------------
---------- TEST -----------
@isTest
public with sharing class GunlukRaporlarTest {
static testMethod void testYap()
{
List<Account> accList = new List<Account>();
Account a = new Account();
a.Name='TESTACCOUNT';
a.Industry = 'Banka';
insert a;
accList.add(a);
System.assertEquals(accList[0].Industry, 'Banka');
}
}
-----------------------------
Thanks for all
King Regards.
@isTest public with sharing class GunlukRaporlarTest { static testMethod void testYap() { List<Account> accList = new List<Account>(); Account a = new Account(); a.Name='TESTACCOUNT'; a.Industry = 'Banka'; insert a; accList.add(a); //System.assertEquals(accList[0].Industry, 'Banka'); GunlukRaporlar.Yap(); } }Please follow below salesforce Best Practice for Test Classes :-1. Test class must start with @isTest annotation if class class version is more than 25
2. Test environment support @testVisible , @testSetUp as well
3. Unit test is to test particular piece of code working properly or not .
4. Unit test method takes no argument ,commit no data to database ,send no email ,flagged with testMethod keyword .
5. To deploy to production at-least 75% code coverage is required
6. System.debug statement are not counted as a part of apex code limit.
7. Test method and test classes are not counted as a part of code limit
9. We should not focus on the percentage of code coverage ,we should make sure that every use case should covered including positive, negative,bulk and single record .
Single Action -To verify that the the single record produces the correct an expected result .
Bulk action -Any apex record trigger ,class or extension must be invoked for 1-200 records .
Positive behavior : Test every expected behavior occurs through every expected permutation , i,e user filled out every correctly data and not go past the limit .
Negative Testcase :-Not to add future date , Not to specify negative amount.
Restricted User :-Test whether a user with restricted access used in your code .10. Test class should be annotated with @isTest .
11 . @isTest annotation with test method is equivalent to testMethod keyword .
12. Test method should static and no void return type .
13. Test class and method default access is private ,no matter to add access specifier .
14. classes with @isTest annotation can't be a interface or enum .
15. Test method code can't be invoked by non test request .
16. Stating with salesforce API 28.0 test method can not reside inside non test classes .
17. @Testvisible annotation to make visible private methods inside test classes.
18. Test method can not be used to test web-service call out . Please use call out mock .
19. You can't send email from test method.
20.User, profile, organization, AsyncApexjob, Corntrigger, RecordType, ApexClass, ApexComponent ,ApexPage we can access without (seeAllData=true) .
21. SeeAllData=true will not work for API 23 version eailer .
22. Accessing static resource test records in test class e,g List<Account> accList=Test.loadData(Account,SobjectType,'ResourceName').
23. Create TestFactory class with @isTest annotation to exclude from organization code size limit .
24. @testSetup to create test records once in a method and use in every test method in the test class .
25. We can run unit test by using Salesforce Standard UI,Force.com IDE ,Console ,API.
26. Maximum number of test classes run per 24 hour of period is not grater of 500 or 10 multiplication of test classes of your organization.
27. As apex runs in system mode so the permission and record sharing are not taken into account . So we need to use system.runAs to enforce record sharing .
28. System.runAs will not enforce user permission or field level permission .
29. Every test to runAs count against the total number of DML issued in the process .
Please let us know if this post will help you
All Answers
@isTest public with sharing class GunlukRaporlarTest { static testMethod void testYap() { List<Account> accList = new List<Account>(); Account a = new Account(); a.Name='TESTACCOUNT'; a.Industry = 'Banka'; insert a; accList.add(a); //System.assertEquals(accList[0].Industry, 'Banka'); GunlukRaporlar.Yap(); } }Please follow below salesforce Best Practice for Test Classes :-1. Test class must start with @isTest annotation if class class version is more than 25
2. Test environment support @testVisible , @testSetUp as well
3. Unit test is to test particular piece of code working properly or not .
4. Unit test method takes no argument ,commit no data to database ,send no email ,flagged with testMethod keyword .
5. To deploy to production at-least 75% code coverage is required
6. System.debug statement are not counted as a part of apex code limit.
7. Test method and test classes are not counted as a part of code limit
9. We should not focus on the percentage of code coverage ,we should make sure that every use case should covered including positive, negative,bulk and single record .
Single Action -To verify that the the single record produces the correct an expected result .
Bulk action -Any apex record trigger ,class or extension must be invoked for 1-200 records .
Positive behavior : Test every expected behavior occurs through every expected permutation , i,e user filled out every correctly data and not go past the limit .
Negative Testcase :-Not to add future date , Not to specify negative amount.
Restricted User :-Test whether a user with restricted access used in your code .10. Test class should be annotated with @isTest .
11 . @isTest annotation with test method is equivalent to testMethod keyword .
12. Test method should static and no void return type .
13. Test class and method default access is private ,no matter to add access specifier .
14. classes with @isTest annotation can't be a interface or enum .
15. Test method code can't be invoked by non test request .
16. Stating with salesforce API 28.0 test method can not reside inside non test classes .
17. @Testvisible annotation to make visible private methods inside test classes.
18. Test method can not be used to test web-service call out . Please use call out mock .
19. You can't send email from test method.
20.User, profile, organization, AsyncApexjob, Corntrigger, RecordType, ApexClass, ApexComponent ,ApexPage we can access without (seeAllData=true) .
21. SeeAllData=true will not work for API 23 version eailer .
22. Accessing static resource test records in test class e,g List<Account> accList=Test.loadData(Account,SobjectType,'ResourceName').
23. Create TestFactory class with @isTest annotation to exclude from organization code size limit .
24. @testSetup to create test records once in a method and use in every test method in the test class .
25. We can run unit test by using Salesforce Standard UI,Force.com IDE ,Console ,API.
26. Maximum number of test classes run per 24 hour of period is not grater of 500 or 10 multiplication of test classes of your organization.
27. As apex runs in system mode so the permission and record sharing are not taken into account . So we need to use system.runAs to enforce record sharing .
28. System.runAs will not enforce user permission or field level permission .
29. Every test to runAs count against the total number of DML issued in the process .
Please let us know if this post will help you
Here you need to modify your class for test coverage .Why because your method is private which you can not access in test class .So either you need to make problic or needs to add @testVisible so that your method wil visibel in test context .
@isTest public with sharing class GunlukRaporlarTest { static testMethod void testYap(){ Account acc = new Account(); acc.Name='TestAccount'; acc.Industry = 'Medicine'; insert acc; acc=[SELECT id,Industry FROM Account WHERE id=:acc.Id]; System.assertEquals(acc.Industry,'Medicine'); GunlukRaporlar.Yap(); } }You can try with belwo code it will help for sure .
public class GunlukRaporlar { @testVisible static void Yap(){ List<Account> allAcc = [select Id,Industry,Name from Account limit 5]; for(Account acc:allAcc){ String cc = acc.Industry; } String aa = 'bb'; } }Let me know if it helps !!Thanks
Manoj