[Prachi]

Hi Hariom,

The following are the major differences between a VisualForce component and a Lightning component in Salesforce:

1. Visualforce was designed to follow a Page-Centric model whereas Lightning was designed to follow an App-Centric model.

2. In Visualforce page all back-end processing is done with Apex Code on the Server-Side where as in Lightning all backend processing is done using Javascript on the Client-Side Server.

3. Visualforce is built for only Desktop purpose where as Lightning is built for both Desktop and mobile purpose.

4. In Visualforce ,apex code is used to handle server side operation where as in Lightning ,javascript is used to handle client side server and Apex for Server side process.

5. In Visualforce HTML markup language is used and Apex code to handle DML operation where as in Lightning, Lightning Components and Applications come in "Bundles" that store all of the necessary files to run the DML Operation.

Lightning framework aligns with Salesforce user interface strategy to empower users with highly immersive and interactive experience but involves a steep learning curve in comparison to Visualforce. Since application building is an inherent part of Lightning, it is considered a bit more complex than Visualforce.

Both the frameworks encompass some pros and cons associated with them. If you are developing for a Salesforce1 mobile app, you should prefer Lightning framework and if you want to create a page-centric experience with limited client-side logic, you must opt Visualforce framework.

Thanks

[Prachi]

Hi Saddam,

We use @testSetup because methods defined with the @testSetup annotation are used for creating common test records that are available for all test methods in the class.

If a test class contains a test setup method, the testing framework executes the test setup method first, before any test method in the class. Records that are created in a test setup method are available to all test methods in the test class and are rolled back at the end of test class execution. If a test method changes those records, such as record field updates or record deletions, those changes are rolled back after each test method finishes execution. The next executing test method gets access to the original unmodified state of those records.

Thanks.

• This reply was modified 5 years, 3 months ago by  Prachi.

[Prachi]

It is not possible, by default Grant Access Using Hierarchies options are enabled for standard objects and they can not be changed. For custom objects we can change "Grant Access Using Hierarchies" settings.

[Prachi]

An Apex transaction represents a set of operations that are executed as a single unit. All DML operations in a transaction either complete successfully, or if an error occurs in one operation, the entire transaction is rolled back and no data is committed to the database. The boundary of a transaction can be a trigger, a class method, an anonymous block of code, a Visualforce page, or a custom Web service method.