+ Start a Discussion
sundhar.mks1.3962649227519546E12sundhar.mks1.3962649227519546E12 

how to write the test class?

Hi,

Kindly refer the following code, How to write test class for this?
Code
===============
public with sharing class QuoteLineItemsManager{
    
    Public String qteId;
    Public List<QuoteLineItem> QLIs{get; set;} 
    
    public void setqteId (String s) {
        qteId= s;
        QLIs=new List<QuoteLineItem>();
        QLISELECT id,(Select id, PricebookEntry.Name,Description,Quantity,UnitPrice,TotalPrice, Capacity__c from QuoteLineItems ORDER BY SortOrder) from Quote where Id=:qteId].QuoteLineItems;
        system.debug('qteId==='+qteId);
    }      
    Public String getqteId(){
        return qteId;
    }
    Public QuoteLineItemsManager() {                        
        
    }

}

Thanks
pconpcon
Since writing a test class to cover all of the facets of this class is not something that anyone on here will do for you, I can give you some pointers and hopefully get you started.  I would recommend that you do some reading on testing [1] [2] [3] to get a better understanding.  Each of your individual tests should only tests one specific portion of you class (ie a constructor test, sendEmail test, contactSelected test, etc).  You should also have both a postitive (everything works perfectly) and a negative (things are not right) test.

Each test should follow the following structure:
  • Setup of test data. This includes creation of any data needed by your class.  Account, Contacts etc
  • Starting the test. This is calling Test.startTest() to reset the governor limits
  • Calling your class / method
  • Stopping the test.This is calling Test.stopTest() to reset the governor limits and allow for any async jobs to finish
  • Asserting that your changes have worked
    • If you have inserted/updated/deleted data, you need to query for the updates
    • Run System.assert, System.assertEquals, System.assertNotEquals to verify that you got the correct data back
In your case you will be inserting new Quotes and QuoteLineItems, making a new instance of your class and calling your methods directly.

If you have any specific problems with your tests, feel free to create a new post with the part of the class you are trying to test and your current test method, and you will more likely get a better response then asking for someone to essentially write an entire test class for you.

NOTE: Please use the "Add a code sample" button (icon <>) next time to increase readability of your code and make it easier to reference.

[1] http://www.sfdc99.com/2013/05/14/how-to-write-a-test-class/
[2] http://pcon.github.io/presentations/testing/
[3] http://blog.deadlypenguin.com/blog/2014/07/23/intro-to-apex-auto-converting-leads-in-a-trigger/