Testing Apex
What is Test class in salesforce?
What Components needs to be tested?
Syntax of basic test class and test method Test class best practices
Introduction to Salesforce | Salesforce Tutorial for Beginners | Salesforce T...Edureka!
( Salesforce Training: https://www.edureka.co/salesforce-administrator-and-developer-training)
This tutorial will give you an introduction to the Salesforce CRM and talk tell you how & why Salesforce has emerged as one of the leading cloud computing companies today.
This video covers the following topics:
1. Salesforce:- Need & Rise
2. Features Of Salesforce
3. Demo: Salesforce In Action
The document discusses finite fields and related algebraic concepts. It begins by defining groups, rings, and fields. It then focuses on finite fields, particularly GF(p) fields consisting of integers modulo a prime p. It discusses finding multiplicative inverses in such fields using the extended Euclidean algorithm. As an example, it finds the inverse of 550 modulo 1759.
This document provides an introduction to Scrum, an agile framework for project management. It discusses the principles of agile development and Scrum, including self-organizing cross-functional teams, short sprint cycles, daily stand-ups, product backlogs and user stories, estimation techniques, and retrospectives for continuous improvement. The Scrum framework emphasizes empiricism, adaptation, transparency, inspection, and frequent delivery of working software.
This document provides an overview of the Health Insurance Portability and Accountability Act (HIPAA). It discusses the background and objectives of HIPAA in ensuring privacy of health information. It describes the key aspects of HIPAA including the Privacy Rule, Security Rule, and definitions of protected health information. It also outlines enforcement measures for non-compliance and additional regulations like HITECH that have expanded HIPAA's requirements. Challenges of ensuring HIPAA compliance are discussed as well.
This document discusses agile metrics for measuring value, flow, quality, and culture. It presents common metrics used by Scrum teams like velocity, burnup/burndown, lead time, and defects. Flow-related metrics across the development lifecycle are explained, including the differences between cycle time and lead time. The document also discusses measuring value, happiness, culture, and frameworks for metrics like SAFe. Key takeaways are that outcomes rather than activity should be measured, and that culture, collaboration, and safety are important but difficult to measure metrics.
"We'll need an Apex trigger to do that." Sound familiar? Take your advanced Admin skills to the next level by developing Apex triggers to solve complex business requirements that can't be implemented using just the configuration-driven features of Force.com. Join us to learn when and how to write your first Apex trigger, and some best practices for making them effective.
This is Seema Dhingra's presentation on the importance and significance of Test Classes at Dreamforce Global Gathering 2017 organised by New Delhi Salesforce Developer Group and Gurgaon WIT at Nagarro Gurgaon Campus.
Join us to learn the components required for building a good unit test that will keep your developers and applications from being blindsided, as well as some of the common Apex use cases like controllers and triggers. You'll also see how to handle trickier situations like HTTP callouts and asynchronous processing.
Apex code is a strongly typed, object-oriented programming language that allows developers to execute flow and transaction control statements on the Force.com platform. It provides the ability to define triggers and classes that can be initiated by user interface events as well as API calls. Apex code executes on the Force.com servers and provides a way for developers to add custom application logic to their Force.com deployments in a way that is integrated with the platform. Testing of Apex code is also supported to help ensure code quality.
Any structure expected to stand the test of time and change needs a strong foundation! Software is no exception. Engineering your code to grow in a stable and effective way is critical to your ability to rapidly meet the growing demands of users, new features, technologies, and platform capabilities. Join us to obtain architect-level design patterns for use in your Apex code to keep it well factored, easy to maintain, and in line with platform best practices. You'll follow a Force.com interpretation of Martin Fowler's Enterprise Architecture Application patterns, and the practice of Separation of Concerns.
This document provides best practices for using Apex in 2022. It discusses security practices like enforcing CRUD/FLS permissions and encrypting data. It also covers performance techniques like using Platform Cache to store reusable data. Designing for scale is addressed, including bulkifying code and using Queueables for large data volumes. The document also discusses making code reusable with trigger frameworks, and maintainable through coding standards, error logging, and writing tests.
This document provides an overview and introduction to Apex for developers. It begins with an introduction to Apex and the Salesforce platform. It then outlines the agenda which includes an overview of the platform, writing Apex classes, accessing data using SOQL and DML, writing triggers, and additional topics like Visualforce, REST APIs, and unit testing. It encourages participants to use their developer environment and provides a link to sign up. It describes what will be built in the session which is an app to manage sessions and speakers at a conference. It includes two forward-looking statements disclaimers.
The Salesforce platform offers system as well as application level security capabilities for building robust and secure applications. Join us as we introduce the system-level security features of Salesforce, like authentication and authorization mechanisms that include various Single Sign-On and OAuth flows. We'll also cover declarative application-level security features, like user profiles, roles and permissions, and how an Organization Wide Security and record-sharing model enforces a finer level of access control over the data.
These are the slides from a presentation given to the San Diego Salesforce Developer Group on September 16, 2014.
The presentation highlights why coding standards and design patterns are important parts of creating a scalable, maintainable Salesforce Enterprise Org. A series of specific implementation and architecture recommendations are outlined. Finally, models for process and governance are provided to help the viewer take steps to bring about change in their Org.
When executing something synchronously, you wait for it to finish before moving on to another task. Asynchronously, you can move on before it finishes. Future methods, Queueable Apex, and Batch Apex allow asynchronous execution in Apex. Future methods are best for long-running methods or callouts. Queueable Apex allows job chaining and passing complex types. Batch Apex is best for large data volumes processed in batches. Continuations allow asynchronous callouts from Visualforce pages.
Description:
Whether you are an experienced developer coming to Apex from another language, or an intermediate level Apex developer, this webinar will take you to the next level in programming on the Salesforce and Force.com platform. We will dive deeper into Apex, and guide you through examples of advanced design patterns and techniques, and much more related to Apex on the Salesforce1 platform!
Key Takeaways:
::Programmers familiar with object-oriented languages will be able to learn Apex easily
::Apex can perform a wide range of functions from serving as a controller for Visualforce pages to scheduled tasks in the background.
::Get a deep dive into testing and code coverage on Force.com, and learn some solid best practices and recipes for writing better tests.
Intended Audience:
::Programmers familiar with object-oriented languages, and looking for an deeper dive into Apex
This document summarizes the key aspects of Salesforce's sharing architecture discussed in a study group meeting. The sharing architecture includes:
1. Implicit sharing rules that provide access based on record ownership, such as a parent record's owner seeing related child records.
2. Organization-wide defaults that set the base level of access to records.
3. Role hierarchies that extend access to records owned by subordinates in the role hierarchy.
4. Additional layers like public groups, sharing rules, manual sharing, and team sharing provide more granular control over record access and sharing.
Queueable Apex allows developers to write asynchronous Apex that is more reliable than future methods alone. It works by storing async requests in the database, including a status field. This allows requests to be retried if they fail, preventing data issues. Developers should use Queueable Apex to build asynchronous processes that can handle failures gracefully instead of potentially leaving the system in a bad state like future methods alone.
A trigger is an Apex script that executes before or after certain events occur in DML, For example, before the object record is entered into the database or after the record has been deleted. Triggers allow you to carry out custom actions before or after changes to Salesforce records.
Episode 20 - Trigger Frameworks in SalesforceJitendra Zaa
This document discusses trigger frameworks in Salesforce and their benefits. It provides an overview of trigger execution order and common patterns for writing trigger frameworks, including the trigger handler and interface-based patterns. The document demonstrates examples using these patterns. Trigger frameworks provide benefits like consistent execution, preventing recursion, improved testability and maintainability. Choosing the right framework depends on factors like complexity, extensibility and code reusability. Resources for learning more about trigger frameworks are also provided.
The problem with Billy's code is that it will create a new Order record every time the Opportunity is updated, even if it was already closed previously.
A better approach would be to use the Trigger Pattern to check for changes to the Opportunity and only create the Order if the Opportunity changes to the closed state. This can be done using the Trigger Pattern with the State design pattern.
Some key points:
- Use Trigger Pattern to separate trigger logic from main logic
- Check for changes to Opportunity using Trigger.oldMap and Trigger.newMap
- Only process if Opportunity changes to closed state
- Use State design pattern to represent different Opportunity states
- Create Order only if state changes to "Closed"
This
Data Management and Migration in SalesforceSunil kumar
This document discusses data management and migration in Salesforce. It covers essential topics like record IDs, object relationships, modifiable system fields, using upsert to insert or update records using external IDs, and tools for data management including the Bulk API and Data Loader. The Bulk API allows high volume loading of data into Salesforce in parallel to improve throughput. The Data Loader can use either the SOAP API or Bulk API and supports functions like import, export, and deleting large numbers of records.
This document provides an overview of asynchronous processing in Salesforce using Batch Apex and Scheduled Apex. It discusses the differences between synchronous and asynchronous processing, how to structure Batch Apex jobs with start, execute, and finish methods, how to maintain state across batches, considerations for Batch Apex, how Scheduled Apex jobs work based on cron expressions, anatomy of a Scheduled Apex job, and considerations for Scheduled Apex. The document includes demos of writing basic and stateful Batch Apex jobs and a Scheduled Apex job with a cron trigger.
Governor limits in Salesforce enforce runtime limits on Apex code to ensure fair sharing of system resources among multiple tenants. The key governor limits include limits on the number of SOQL queries, records retrieved, and number of scripts executed. Governor limits are calculated based on the entry point for the Apex code, such as Apex triggers, web services, or anonymous blocks. Limits are shared across an organization and apply to all code executed within a synchronous transaction, while asynchronous code like future methods has separate limits. Developers must optimize code to avoid hitting governor limits, for example by bulkifying code, minimizing SOQL queries, and using future calls appropriately.
There are three main types of relationships in Salesforce:
1. Master-detail relationships model parent-child relationships where child records cannot exist without a parent record and parent deletion deletes children. Up to two master-detail relationships are allowed per object.
2. Lookup relationships can link objects without implications for security, deletion, or required fields. Up to 25 lookups are allowed.
3. Many-to-many relationships are modeled using a junction object with two master-detail relationships to the original objects. This allows each record to link to multiple others in both directions.
This document discusses techniques for hardening a Salesforce org against cybersecurity threats. It covers Salesforce security at the infrastructure and application levels. It also recommends best practices like using two-factor authentication, auditing permissions, and providing security training for users. The document promotes the Salesforce Toolkit and a free online cybersecurity course for further resources.
This document provides an overview of automated unit testing in PHP. It discusses what unit testing is, why it is important, what should be tested, when to test, and how to set up and run tests using PHPUnit. Key points include:
- Unit testing validates individual units of source code. Each test should test a single function or class.
- Tests should be run early and often to catch bugs early in development.
- PHPUnit is a popular PHP testing framework that allows creating and running automated tests. It provides assertions, fixtures, and other features to test code.
- Tests can be organized into test suites and run via the command line or configured via an XML file. Groups allow filtering tests to
The presentation explains the PHP unit testing framework and provides a basic training on Testing with PHPunit. It Covers fundamental of unit testing, unit testing benefits and best practices. Starting ground up from PHP unit fundamentals, features of unit testing tries to explore advanced topics like Data providers, Fuxtures, Test doubles and more...
This is Seema Dhingra's presentation on the importance and significance of Test Classes at Dreamforce Global Gathering 2017 organised by New Delhi Salesforce Developer Group and Gurgaon WIT at Nagarro Gurgaon Campus.
Join us to learn the components required for building a good unit test that will keep your developers and applications from being blindsided, as well as some of the common Apex use cases like controllers and triggers. You'll also see how to handle trickier situations like HTTP callouts and asynchronous processing.
Apex code is a strongly typed, object-oriented programming language that allows developers to execute flow and transaction control statements on the Force.com platform. It provides the ability to define triggers and classes that can be initiated by user interface events as well as API calls. Apex code executes on the Force.com servers and provides a way for developers to add custom application logic to their Force.com deployments in a way that is integrated with the platform. Testing of Apex code is also supported to help ensure code quality.
Any structure expected to stand the test of time and change needs a strong foundation! Software is no exception. Engineering your code to grow in a stable and effective way is critical to your ability to rapidly meet the growing demands of users, new features, technologies, and platform capabilities. Join us to obtain architect-level design patterns for use in your Apex code to keep it well factored, easy to maintain, and in line with platform best practices. You'll follow a Force.com interpretation of Martin Fowler's Enterprise Architecture Application patterns, and the practice of Separation of Concerns.
This document provides best practices for using Apex in 2022. It discusses security practices like enforcing CRUD/FLS permissions and encrypting data. It also covers performance techniques like using Platform Cache to store reusable data. Designing for scale is addressed, including bulkifying code and using Queueables for large data volumes. The document also discusses making code reusable with trigger frameworks, and maintainable through coding standards, error logging, and writing tests.
This document provides an overview and introduction to Apex for developers. It begins with an introduction to Apex and the Salesforce platform. It then outlines the agenda which includes an overview of the platform, writing Apex classes, accessing data using SOQL and DML, writing triggers, and additional topics like Visualforce, REST APIs, and unit testing. It encourages participants to use their developer environment and provides a link to sign up. It describes what will be built in the session which is an app to manage sessions and speakers at a conference. It includes two forward-looking statements disclaimers.
The Salesforce platform offers system as well as application level security capabilities for building robust and secure applications. Join us as we introduce the system-level security features of Salesforce, like authentication and authorization mechanisms that include various Single Sign-On and OAuth flows. We'll also cover declarative application-level security features, like user profiles, roles and permissions, and how an Organization Wide Security and record-sharing model enforces a finer level of access control over the data.
These are the slides from a presentation given to the San Diego Salesforce Developer Group on September 16, 2014.
The presentation highlights why coding standards and design patterns are important parts of creating a scalable, maintainable Salesforce Enterprise Org. A series of specific implementation and architecture recommendations are outlined. Finally, models for process and governance are provided to help the viewer take steps to bring about change in their Org.
When executing something synchronously, you wait for it to finish before moving on to another task. Asynchronously, you can move on before it finishes. Future methods, Queueable Apex, and Batch Apex allow asynchronous execution in Apex. Future methods are best for long-running methods or callouts. Queueable Apex allows job chaining and passing complex types. Batch Apex is best for large data volumes processed in batches. Continuations allow asynchronous callouts from Visualforce pages.
Description:
Whether you are an experienced developer coming to Apex from another language, or an intermediate level Apex developer, this webinar will take you to the next level in programming on the Salesforce and Force.com platform. We will dive deeper into Apex, and guide you through examples of advanced design patterns and techniques, and much more related to Apex on the Salesforce1 platform!
Key Takeaways:
::Programmers familiar with object-oriented languages will be able to learn Apex easily
::Apex can perform a wide range of functions from serving as a controller for Visualforce pages to scheduled tasks in the background.
::Get a deep dive into testing and code coverage on Force.com, and learn some solid best practices and recipes for writing better tests.
Intended Audience:
::Programmers familiar with object-oriented languages, and looking for an deeper dive into Apex
This document summarizes the key aspects of Salesforce's sharing architecture discussed in a study group meeting. The sharing architecture includes:
1. Implicit sharing rules that provide access based on record ownership, such as a parent record's owner seeing related child records.
2. Organization-wide defaults that set the base level of access to records.
3. Role hierarchies that extend access to records owned by subordinates in the role hierarchy.
4. Additional layers like public groups, sharing rules, manual sharing, and team sharing provide more granular control over record access and sharing.
Queueable Apex allows developers to write asynchronous Apex that is more reliable than future methods alone. It works by storing async requests in the database, including a status field. This allows requests to be retried if they fail, preventing data issues. Developers should use Queueable Apex to build asynchronous processes that can handle failures gracefully instead of potentially leaving the system in a bad state like future methods alone.
A trigger is an Apex script that executes before or after certain events occur in DML, For example, before the object record is entered into the database or after the record has been deleted. Triggers allow you to carry out custom actions before or after changes to Salesforce records.
Episode 20 - Trigger Frameworks in SalesforceJitendra Zaa
This document discusses trigger frameworks in Salesforce and their benefits. It provides an overview of trigger execution order and common patterns for writing trigger frameworks, including the trigger handler and interface-based patterns. The document demonstrates examples using these patterns. Trigger frameworks provide benefits like consistent execution, preventing recursion, improved testability and maintainability. Choosing the right framework depends on factors like complexity, extensibility and code reusability. Resources for learning more about trigger frameworks are also provided.
The problem with Billy's code is that it will create a new Order record every time the Opportunity is updated, even if it was already closed previously.
A better approach would be to use the Trigger Pattern to check for changes to the Opportunity and only create the Order if the Opportunity changes to the closed state. This can be done using the Trigger Pattern with the State design pattern.
Some key points:
- Use Trigger Pattern to separate trigger logic from main logic
- Check for changes to Opportunity using Trigger.oldMap and Trigger.newMap
- Only process if Opportunity changes to closed state
- Use State design pattern to represent different Opportunity states
- Create Order only if state changes to "Closed"
This
Data Management and Migration in SalesforceSunil kumar
This document discusses data management and migration in Salesforce. It covers essential topics like record IDs, object relationships, modifiable system fields, using upsert to insert or update records using external IDs, and tools for data management including the Bulk API and Data Loader. The Bulk API allows high volume loading of data into Salesforce in parallel to improve throughput. The Data Loader can use either the SOAP API or Bulk API and supports functions like import, export, and deleting large numbers of records.
This document provides an overview of asynchronous processing in Salesforce using Batch Apex and Scheduled Apex. It discusses the differences between synchronous and asynchronous processing, how to structure Batch Apex jobs with start, execute, and finish methods, how to maintain state across batches, considerations for Batch Apex, how Scheduled Apex jobs work based on cron expressions, anatomy of a Scheduled Apex job, and considerations for Scheduled Apex. The document includes demos of writing basic and stateful Batch Apex jobs and a Scheduled Apex job with a cron trigger.
Governor limits in Salesforce enforce runtime limits on Apex code to ensure fair sharing of system resources among multiple tenants. The key governor limits include limits on the number of SOQL queries, records retrieved, and number of scripts executed. Governor limits are calculated based on the entry point for the Apex code, such as Apex triggers, web services, or anonymous blocks. Limits are shared across an organization and apply to all code executed within a synchronous transaction, while asynchronous code like future methods has separate limits. Developers must optimize code to avoid hitting governor limits, for example by bulkifying code, minimizing SOQL queries, and using future calls appropriately.
There are three main types of relationships in Salesforce:
1. Master-detail relationships model parent-child relationships where child records cannot exist without a parent record and parent deletion deletes children. Up to two master-detail relationships are allowed per object.
2. Lookup relationships can link objects without implications for security, deletion, or required fields. Up to 25 lookups are allowed.
3. Many-to-many relationships are modeled using a junction object with two master-detail relationships to the original objects. This allows each record to link to multiple others in both directions.
This document discusses techniques for hardening a Salesforce org against cybersecurity threats. It covers Salesforce security at the infrastructure and application levels. It also recommends best practices like using two-factor authentication, auditing permissions, and providing security training for users. The document promotes the Salesforce Toolkit and a free online cybersecurity course for further resources.
This document provides an overview of automated unit testing in PHP. It discusses what unit testing is, why it is important, what should be tested, when to test, and how to set up and run tests using PHPUnit. Key points include:
- Unit testing validates individual units of source code. Each test should test a single function or class.
- Tests should be run early and often to catch bugs early in development.
- PHPUnit is a popular PHP testing framework that allows creating and running automated tests. It provides assertions, fixtures, and other features to test code.
- Tests can be organized into test suites and run via the command line or configured via an XML file. Groups allow filtering tests to
The presentation explains the PHP unit testing framework and provides a basic training on Testing with PHPunit. It Covers fundamental of unit testing, unit testing benefits and best practices. Starting ground up from PHP unit fundamentals, features of unit testing tries to explore advanced topics like Data providers, Fuxtures, Test doubles and more...
This document discusses best practices for writing test classes in Apex. It covers topics such as what to test, using annotations like @IsTest, the importance of assertions, utilizing Test.startTest() and Test.stopTest(), how to write test classes for different types of code, and common utilities for test data setup. Maintaining well-written test classes is important for achieving code coverage requirements during deployment.
The document discusses several automated testing tools:
- PHPUnit is a unit testing framework for PHP that allows writing and running automated tests. It helps ensure code quality and finds regressions.
- Selenium is a suite of tools for automating web application testing across browsers and platforms. It includes the Selenium IDE, RC, and Grid.
- Phing is a build system based on Apache Ant for PHP projects. It uses XML build files and PHP tasks to provide an extensible and flexible build framework.
An introduction to apex code test methods developer.forcesendmail2cherukuri
This document introduces test methods in Apex Code and discusses their importance for developing robust, error-free applications on the Force.com platform. Test methods verify that code works properly by asserting expected outcomes. They must be at least 75% covered to deploy code to production. Test methods are defined using the testMethod keyword or @isTest annotation and execute in a separate context from production code using Test.startTest() and Test.stopTest(). System.runAs() allows testing with different user contexts. Tests can be run from the UI or via the Metadata API.
Episode 5 - Writing unit tests in SalesforceJitendra Zaa
The document provides an agenda for a session on writing unit tests in Apex. It discusses why unit tests are important in Apex, how to structure test classes, best practices for testing, and resources for learning more about Apex testing. The session demonstrates executing unit tests and techniques like accessing private members, running tests within limits, and creating test data. Attendees are encouraged to ask questions during the last 15 minutes.
Automation testing uses tools to write and execute test scripts to compare actual and expected results. It can save time and costs compared to manual testing if properly planned and scoped. Popular automation testing tools include QTP, Rational Robot, and Selenium. Unit testing frameworks like JUnit help find problems early using annotations to identify test setup and methods. Assertions in test methods verify code outputs match expectations.
Unit testing involves testing individual units or components of code to ensure they work as intended. It focuses on testing small, isolated units of code to check functionality and edge cases. Benefits include faster debugging, development and regression testing. Guidelines for effective unit testing include keeping tests small, automated, independent and focused on the code's public API. Tests should cover a variety of inputs including boundaries and error conditions.
Integrate the Microsoft Unit Testing Framework into your Visual Studio 2010 projects. Learn the fundamentals of the Microsoft.VisualStudio.TestTools.UnitTesting namespace. Explore the tools for running and debugging your unit tests. Discuss general best practices for writing unit tests. Examples will be presented in C#.
Dev labs alliance top 20 testng interview questions for sdetdevlabsalliance
The document discusses 20 common TestNG interview questions for SDET roles. It covers topics like what TestNG is, advantages over JUnit, uses of testng.xml file, different annotations, execution sequence, dependencies, parameters, data providers, listeners, parallel execution, exception handling and more. The document aims to help candidates prepare for TestNG questions that may be asked during interviews for SDET positions.
Unit testing involves testing individual units or components of code to ensure they work as intended. It focuses on testing functional correctness, error handling, and input/output values. The main benefits are faster debugging, easier integration testing, and living documentation. Guidelines for effective unit testing include writing automated, independent, focused tests that cover boundaries and are easy to run and maintain.
Unit tests test individual methods, integration tests test interactions between components, functional tests verify outputs without checking internals, and end-to-end tests perform complex scenarios like payments. Acceptance tests replicate user behaviors across the entire application. Performance tests evaluate behavior under load. Smoke tests check proper functioning after deployment. Frameworks like JUnit, TestNG, Cucumber, and Mockito support different test types.
Test driven development - JUnit basics and best practicesNarendra Pathai
A presentation covering all the basics of Software Unit testing using JUnit framework. A lot of best practices, myths misconceptions are covered. Naming conventions for test methods and fundamental requirements for doing sustainable Junit testing.
TestNG is a testing framework inspired from JUnit and NUnit, which can be used as a core unit test framework for Java project.
Demo: https://github.com/bethmi/testng-demo
Running and Developing Tests with the Apache::Test Frameworkwebhostingguy
The Apache::Test framework allows running and developing tests for Apache modules and products. Key features include:
- Running existing tests through the t/TEST program
- Setting up a new testing environment by installing Apache::Test and generating a Makefile
- Developing new tests by writing Perl scripts that use Apache::Test functions and assert results
- Options for running tests individually, repeatedly without restarts, or in parallel on different ports
Unit testing involves testing individual units or components of an application to ensure they operate as expected. The UnitTest++ and HippoMocks frameworks allow writing and running unit tests in C++. UnitTest++ provides macros and functions to define tests and make assertions while HippoMocks allows mocking dependencies to isolate units during testing.
This document provides an overview of TestNG, an open source automated testing framework. It discusses TestNG annotations that can be used to identify test methods and configure test execution. It also covers TestNG XML for defining test suites, groups, parameters. The document explains how to integrate TestNG with Selenium for browser automation and how to use TestNG listeners.
This document outlines an agenda for a meetup event on CICD, DevOps, and APIOps with Azure DevOps. The agenda includes introductions, a demo presentation on the topic, Q&A, a quiz, and networking. The presentation will cover DevOps, CI/CD, APIOps, DevOps with Mulesoft, and demonstrate Azure DevOps pipelines and releases. It will also provide an overview of Jenkins.
Custom MuleSoft connector using Java SDKAmit Singh
The document summarizes a presentation on developing custom connectors for MuleSoft using the Java and XML SDKs. The presentation covered what connectors and the Mule SDK are, differences between Mule 3 and 4 SDKs, best practices for connector development, examples of existing connectors, and a live demo of a custom currency exchange connector. It included an agenda, speaker bio, and questions for a prize quiz at the end.
These days, customers are expecting a seamless customer experience - no matter if that experience consists of behind the scenes business solutions and services that reside on a single platform or across multiple off-platform hosts.
It’s this interaction between Salesforce and outside services where External Services exists
The document summarizes the agenda for a MuleSoft Meetup Group meeting on APIs. It includes introductions, a discussion of what APIs are and their history, an overview of RAML for describing APIs, and how to integrate Auth0 authorization with MuleSoft using client credentials and authorization code flows. The agenda also allocates time at the end for attendees to introduce themselves to each other and network.
The document outlines an agenda for a MuleSoft meetup on error handling in Mule 4. It includes an introduction to error handling, 3 rules for understanding error handling, a demo, and a Q&A session. Attendees are informed about opportunities to participate in a quiz to win training classes and certification exams. The content then covers error handling concepts in Mule 4 like different levels of handling, the error object, and priorities. It demonstrates error handling examples and promotes hands-on learning.
This document summarizes an agenda for a Mulesoft meetup event discussing MUnit testing. The event includes introductions, presentations on getting started with Mulesoft and MUnit testing, and a quiz with prizes. The MUnit testing presentation will cover what MUnit is, how to use it, common operations like assertions, and the new test recorder feature which can automatically generate tests. The goal is to make testing easier in Mulesoft. The event will conclude with calls for future speaker nominations and feedback.
Test setup methods in Salesforce Apex ClassAmit Singh
Hi #Trailblazer,
In this video, we are going to talk about how to work with Test Setup Methods in Salesforce Test Class. Below is the Agenda for the same
1 - @TestSetup method
2 - Advantage of @TestSetup method
3 - TestUtility Class
4 - Advantage of Utility Class
Link to Code - https://gist.github.com/amitastreait/393f234be893ff84881f00dc3ee89231
Helps you to conform the Best Practices
Simply testing and maintaining the application logic is very easy
Assure Order of Execution
Prevent the Recursion
Error handling makes very easy
Hi #Trailblazers,
In this video, you will learn all the concept of Apex Trigger Handler & Trigger Helper along with a Trigger Scenario. Below is the Agenda:-
1 - Develop a Simple Trigger
2 - Develop a trigger using Handler & Helper Class
*************** PROBLEM STATEMENT *****************
Show the Error to user while deleting any account if that account associated with any closed won opportunity.
Rollup Summary Trigger for Lookup Relationship Salesforce #Salesforce #ApexTr...Amit Singh
An Apex trigger is proposed to count the number of related contact records for an account to populate a field, since a rollup summary field cannot be used due to the lookup relationship between account and contact. The trigger would need to execute on contact record insert, update, and delete to accurately update the account field, as a process builder would fail to handle deletions. The target object for the trigger would be the account, and the trigger events would be on contact record changes.
Hi Everyone,
In this video, we will discuss how to work with apex trigger and logic building.
Below is the Agenda for the video
1 - Problem Statement
2 - Possible Solution
3 - Choosing the right solution
4 - Solution Approach
5 - Develop the Apex Trigger
Link to Video:-
https://youtu.be/0OCP3UvWx2M
Salesforce apex hours PayPal with Salesforce IntegrationAmit Singh
Purpose of Integration
What is API?
What is WebService?
Live Demo
Object Structure of the Objects involved in Demo
Walkthrough of how to setup the Integration and test API using Postman tool.
Q & A
Introduction to apex trigger context variablesAmit Singh
What are context variables?
Different Context Variables and their explanation?
Context Variable availability based on Trigger Events.
Write a trigger to verify the concept that we learned about Context Variables
What is an Apex Trigger?
When to use Apex Trigger?
What are types of Trigger?
Different between Before and After Trigger.
When to use before and When to use After Trigger?
Basic Syntax of Trigger
Write your First Trigger
1 - What is DevOps:- DevOps is a culture and a set of Process that bring development and operations teams together to complete software development.
It allows the organization to develop and improve the product in a faster way that they can do with other software development approaches.
2 - Why DevOps:-
Shorter Development Cycles, Faster Innovation
Reduced Deployment Failures, Rollbacks, and Time to Recover
Improved Communication and Collaboration
Increased Efficiencies
Why Lightning Web Component?
HTML5 Vanilla Components
4 Pillars of Web Component
How templating works in Web components
Lightning Web Components
Hello Word Components
Call Apex From LWC
Communicate with Aura Components
CBSE - Grade 8 - Science - Chemistry - Metals and Non Metals - WorksheetSritoma Majumder
Introduction
All the materials around us are made up of elements. These elements can be broadly divided into two major groups:
Metals
Non-Metals
Each group has its own unique physical and chemical properties. Let's understand them one by one.
Physical Properties
1. Appearance
Metals: Shiny (lustrous). Example: gold, silver, copper.
Non-metals: Dull appearance (except iodine, which is shiny).
2. Hardness
Metals: Generally hard. Example: iron.
Non-metals: Usually soft (except diamond, a form of carbon, which is very hard).
3. State
Metals: Mostly solids at room temperature (except mercury, which is a liquid).
Non-metals: Can be solids, liquids, or gases. Example: oxygen (gas), bromine (liquid), sulphur (solid).
4. Malleability
Metals: Can be hammered into thin sheets (malleable).
Non-metals: Not malleable. They break when hammered (brittle).
5. Ductility
Metals: Can be drawn into wires (ductile).
Non-metals: Not ductile.
6. Conductivity
Metals: Good conductors of heat and electricity.
Non-metals: Poor conductors (except graphite, which is a good conductor).
7. Sonorous Nature
Metals: Produce a ringing sound when struck.
Non-metals: Do not produce sound.
Chemical Properties
1. Reaction with Oxygen
Metals react with oxygen to form metal oxides.
These metal oxides are usually basic.
Non-metals react with oxygen to form non-metallic oxides.
These oxides are usually acidic.
2. Reaction with Water
Metals:
Some react vigorously (e.g., sodium).
Some react slowly (e.g., iron).
Some do not react at all (e.g., gold, silver).
Non-metals: Generally do not react with water.
3. Reaction with Acids
Metals react with acids to produce salt and hydrogen gas.
Non-metals: Do not react with acids.
4. Reaction with Bases
Some non-metals react with bases to form salts, but this is rare.
Metals generally do not react with bases directly (except amphoteric metals like aluminum and zinc).
Displacement Reaction
More reactive metals can displace less reactive metals from their salt solutions.
Uses of Metals
Iron: Making machines, tools, and buildings.
Aluminum: Used in aircraft, utensils.
Copper: Electrical wires.
Gold and Silver: Jewelry.
Zinc: Coating iron to prevent rusting (galvanization).
Uses of Non-Metals
Oxygen: Breathing.
Nitrogen: Fertilizers.
Chlorine: Water purification.
Carbon: Fuel (coal), steel-making (coke).
Iodine: Medicines.
Alloys
An alloy is a mixture of metals or a metal with a non-metal.
Alloys have improved properties like strength, resistance to rusting.
How to Manage Opening & Closing Controls in Odoo 17 POSCeline George
In Odoo 17 Point of Sale, the opening and closing controls are key for cash management. At the start of a shift, cashiers log in and enter the starting cash amount, marking the beginning of financial tracking. Throughout the shift, every transaction is recorded, creating an audit trail.
Odoo Inventory Rules and Routes v17 - Odoo SlidesCeline George
Odoo's inventory management system is highly flexible and powerful, allowing businesses to efficiently manage their stock operations through the use of Rules and Routes.
Understanding P–N Junction Semiconductors: A Beginner’s GuideGS Virdi
Dive into the fundamentals of P–N junctions, the heart of every diode and semiconductor device. In this concise presentation, Dr. G.S. Virdi (Former Chief Scientist, CSIR-CEERI Pilani) covers:
What Is a P–N Junction? Learn how P-type and N-type materials join to create a diode.
Depletion Region & Biasing: See how forward and reverse bias shape the voltage–current behavior.
V–I Characteristics: Understand the curve that defines diode operation.
Real-World Uses: Discover common applications in rectifiers, signal clipping, and more.
Ideal for electronics students, hobbyists, and engineers seeking a clear, practical introduction to P–N junction semiconductors.
Ultimate VMware 2V0-11.25 Exam Dumps for Exam SuccessMark Soia
Boost your chances of passing the 2V0-11.25 exam with CertsExpert reliable exam dumps. Prepare effectively and ace the VMware certification on your first try
Quality dumps. Trusted results. — Visit CertsExpert Now: https://www.certsexpert.com/2V0-11.25-pdf-questions.html
Title: A Quick and Illustrated Guide to APA Style Referencing (7th Edition)
This visual and beginner-friendly guide simplifies the APA referencing style (7th edition) for academic writing. Designed especially for commerce students and research beginners, it includes:
✅ Real examples from original research papers
✅ Color-coded diagrams for clarity
✅ Key rules for in-text citation and reference list formatting
✅ Free citation tools like Mendeley & Zotero explained
Whether you're writing a college assignment, dissertation, or academic article, this guide will help you cite your sources correctly, confidently, and consistent.
Created by: Prof. Ishika Ghosh,
Faculty.
📩 For queries or feedback: [email protected]
GDGLSPGCOER - Git and GitHub Workshop.pptxazeenhodekar
This presentation covers the fundamentals of Git and version control in a practical, beginner-friendly way. Learn key commands, the Git data model, commit workflows, and how to collaborate effectively using Git — all explained with visuals, examples, and relatable humor.
How to Set warnings for invoicing specific customers in odooCeline George
Odoo 16 offers a powerful platform for managing sales documents and invoicing efficiently. One of its standout features is the ability to set warnings and block messages for specific customers during the invoicing process.
Geography Sem II Unit 1C Correlation of Geography with other school subjectsProfDrShaikhImran
The correlation of school subjects refers to the interconnectedness and mutual reinforcement between different academic disciplines. This concept highlights how knowledge and skills in one subject can support, enhance, or overlap with learning in another. Recognizing these correlations helps in creating a more holistic and meaningful educational experience.
How to Customize Your Financial Reports & Tax Reports With Odoo 17 AccountingCeline George
The Accounting module in Odoo 17 is a complete tool designed to manage all financial aspects of a business. Odoo offers a comprehensive set of tools for generating financial and tax reports, which are crucial for managing a company's finances and ensuring compliance with tax regulations.
How to Subscribe Newsletter From Odoo 18 WebsiteCeline George
Newsletter is a powerful tool that effectively manage the email marketing . It allows us to send professional looking HTML formatted emails. Under the Mailing Lists in Email Marketing we can find all the Newsletter.
2. Agenda
❖ What is Test class in salesforce?
❖ What Components needs to be test?
❖ Syntax of basic test class and test method
❖ Test class best practices
3. What is test class in Salesforce
❖ A test class in Salesforce is also an Apex Class which is used to test the logic for Apex
trigger, Apex Class, VF Controller, VF Extensions, Batch Apex, Queueable Apex, future
apex.
❖ Test class insures that every logic is working as expected in both Positive & Negative
Testing.
❖ Test class code does not count in overall code coverage.
❖ Every Apex Class must have at least 75% code coverage before deploying into production
environment.
❖ Every Apex Trigger must need to have at least 1% code coverage.
❖ VF, VF Component, Lightning Component does not require any test class to migrate to
Production Environment.
!3
4. What component needs to be tested
❖ Apex Trigger
❖ Apex Class
❖ Batch Apex
❖ VF Controller/Extensions
❖ Future/Queueable Apex
❖ Restricted User
5. Write Basic Apex Test class
@isTest
private class MyTestClass {
@isTest static void myTest() {
// code_block
}
}
6. Test Class Best Practices
1. Use @isTest at the Top for all the test classes
2. Always put assert statements for negative and positive tests
3. Use the @testSetup method to insert the test data into Test class that will flow data all over the test class.
4. Use Utility Class to prepare the test data if same data is used in multiple test classes.
5. Always use Test.startTest() and Test.stopTest() doing this it will increase the governor limit of salesforce. We also
use this to increase the governor limit.
6. Use System.runAs() method to test the functionality in user Context.
7. Do not put (seeAllData = true) in test class otherwise, use it for exceptional cases.
8. Avoid Using Hard Coding Ids anywhere in test Class or any apex class.
9. Please make sure that each class has minimum 75% coverage and also the main functionality has been covered.
10. All class method must be tested in bulk way (for at least 200 records) and keep the real scenarios in mind.
11. Only one Test.startTest() and Test.stopTest() statement can be in a method, and no of Test.startTest() and
Test.stopTest() statement in any test class depend upon the test methods.