Testing, Debugging, and Deployment (17%) Flashcards
Can anonymous code be executed to test Apex classes?
NO!
Major differences in executing Apex code anonymously and in unit tests:
- Anonymous code commits data changes to the system.
- Anonymous code does not provide code coverage.
- Anonymous code is executed in user mode with sharing enforced.
- Anonymous code is not saved or stored, even when executed (but it will generate a debug log!)
- Anonymous code does not reset governor limits if startTest() and stopTest() methods are used.
Proper procedure for unit testing
- Create test data
- Call the Apex class method in the test method
- Verify results
What are the different tools you can use to run Apex test methods?
- Developer console
- Salesforce UI (Apex Test Execution in Setup)
- VS Code
- SOAP API
What groupings of unit tests can you run?
- Some or all methods in a specific class
- Some or all methods in a set of classes
- Test suite (predefined suite of classes)
- All unit tests in your org
What is NOT counted as part of Apex code coverage?
- Calls to system.debug
- Test methods and test classes
What is Suite Manager?
Suite Manager is used to create or delete test suites or edit which classes your test suite contains.
A test suite is a collection of Apex test classes that you run together.
Suite Manager is only used to bundle test classes, not to create or edit them directly.
What does runAs() enforce and not enforce in regards to user access?
- Record sharing settings
- Does NOT enforce user permissions, object settings, or field level security!
- It ignores user license limits
- Can be used with new or existing users
What is a debug level?
A set of log levels for debug log categories
- You can reuse debug levels across your trace flags
What is the Log Inspector?
A context-sensitive execution viewer that shows the source of an operation, what triggered the operation, and what occurred afterward.
Use this tool to inspect debug logs that include database events, Apex processing, workflow, and validation logic.
What information can the Log Inspector contain?
- Stack Tree
- Execution Stack
- Execution Log
- Source
- Variables & Execution Overview
Difference between AsyncApexJob and CronTrigger objects when using a SOQL query to obtain information about a scheduled job?
AsyncApexJob uses “Status”, CronTrigger uses “State”
How often can Partial Copy and Full Copy sandboxes be refreshed?
- Partial copy = 5 days
- Full copy = 29 days
What information does the Checkpoints tab provide?
- Namespace
- Class
- Line
- Time (DateTime)
What type of sandbox should be used for quality assurance tasks like user acceptance testing, integration testing, and training?
Partial Copy
What type of sandbox should be used for performance testing, load testing, and staging?
Full Copy
Common use cases for Tooling API
- Source control integration
- Continuous integration
- Deployment of Apex classes and triggers
- Accessing a debug log
- Accessing code coverage results for an Apex class
- Committing changes to an org
*Tooling API can be used for fine-grained access to the org’s metadata. Simpler migrations should use the Metadata API.
Debug log categories
- Apex Code
- Apex Profiling
- Callout
- Database (DB)
- System
- Validation
- Visualforce
- Workflow
Debug log level options
(in order from least to most information provided)
- NONE
- ERROR
- WARN
- INFO
- DEBUG
- FINE
- FINER
- FINEST
What type of environments can you use to develop a managed package?
- Developer Edition
- Partner Developer Edition
What user is created automatically by Salesforce, where the user detail record cannot be maintained?
Some Salesforce applications automatically run their business processes as it.
Platform Integration User
When does the Platform Integration User show up in audit fields after setting up a trace flag for it?
- When an Einstein bot creates a case
- When Einstein writes prediction data to records it is evaluating
- When data is synchronized using Salesforce Integration Cloud
Capabilities of VS Code
- Test and debug Apex classes and triggers
- Run anonymous blocks of Apex on the server
- Execute SOQL queries
- Synchronize project contents with changes on the server
- Deploy metadata components from on Salesforce org to another
- Projects can work in online or offline modes
When should a scratch org be used?
- To perform automated testing
- To work on a single feature or update
How do you use the “@isTest” and “@TestSetup” annotations?
- Use @TestSetup in a test class to create test data that the rest of the methods in the class will use. Changes made by each method to the test data reset after every method iteration so the different methods are not accessing changes made by each other. @TestSetup cannot explicitly be called by another class.
- @isTest is used to define classes and methods that only contain code used for testing your application. Classes defined as @isTest must be top-level classes. Classes and methods defined as @isTest can either be private or public.
Why would you use @isTest(SeeAllData=true)?
- Use this to grant test classes and individual test methods access to all data in the org, including pre-existing data that the test class didn’t create.
- If the containing class uses @isTest(SeeAllData=true) then every method in the class inherits that access, even if a method is specifically annotated with @isTest(SeeAllData=false). Conversely, if the containing class is annotated with @isTest(SeeAllData=false), any method within the class can override that access level by using @isTest(SeeAllData=true)
Why would you use @isTest(isParallel=true)?
- Use this annotation to indicate test classes that can run in parallel. Default limits on number of concurrent tests do not apply to these test classes. This annotation makes the execution of test classes more efficient because more tests can be run in parallel.
- @isTest(SeeAllData=true) and @isTest(isParallel=true) annotations cannot be used together on the same test method.
How can you make @TestSetup data from one test class visible to another test class?
You can’t call @TestSetup explicitly from another test class as it is a system function. @TestSetup is only available to the methods in the class where it’s defined.
However, you can create an @TestSetup method and then call that method from within another @TestSetup method of another class.
EXAMPLE: TestDataFactory is the class that contains the test data we want. The test data in that class is stored in a @TestSetup annotated method called dataFactorySetup().
In a separate test class, TestFunctionalClass, use a method annotated with @TestSetup, prepareData(), to call the dataFactorySetup() method from the TestDataFactory class.
public class FunctionalClass {
//logic that needs to be tested
}
@IsTest
public class TestFunctionalClass {
@TestSetup static void prepareData()
{
TestDataFactory.setup();
}
static testMethod void validateData()
{
//unit tests that test FunctionClass logic
//query for data that is setup in TestDataFactory.class
}
}
@IsTest
public class TestDataFactory {
static void setup() {
//insert test data
}
}
Apex Governor Limits: Maximum number of asynchronous Apex method executions per 24-hour period
250,000 OR the number of user licenses in your org multiplied by 200, whichever is greater
Apex Governor Limits: Total heap size
6 MB, or 12MB asynchronously
Apex Governor Limits: Maximum CPU time on Salesforce servers
10,000 milliseconds or 60,000 milliseconds asynchronously
Apex Governor Limits: Maximum execution time for each Apex transaction
10 minutes
Apex Governor Limits: What maximum limits can be made greater when methods are run asynchronously?
- Total number of SOQL queries issued
- Total heap size
- Maximum CPU time
