Episode 5 - Writing unit tests in Salesforce

Feb 2, 2019Download as PPTX, PDF0 likes1,284 views

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.

Path to Code
Begin Your Salesforce Coding Adventure

Enterprise Solutions Architect
Follow me @JigarShah189
Jigar Shah

Agenda
• Why write Unit Tests in Apex?
• Understanding Test Code Coverage
• Blueprint of a Test Class
• Executing Unit Tests
• Best Practices for Unit Testing
• Trailhead Modules
• Q&A

Some Housekeeping Rules…
• Mute your mic
• Keep adding questions in Zoom Q&A Window
• No questions are silly!
• Questions will be answered in the last 15 mins of this session

Why write Apex Unit Tests?
Validate desired behavior
Reliable & consistent
Reduce the bug fix cost
Perform Bulk tests
Introduce changes effectively

Understanding Test Code Coverage
“Unit tests must cover minimum 75%
of Apex code on your org & all tests
must complete successfully”

What to Test?
Single Action
Bulk Actions ( >200 records)
Positive Behavior (Expected Behavior)
Negative Behavior (Unexpected Behavior)
Restricted User Access

Executing Unit Tests
• Run executions
o All unit tests
o Some or all methods of specific class
o Some or all methods of a set of classes
o Predefined suite of classes – Test Suite
• How to run?
o Salesforce user interface
o Force.com IDE
o Lightning Platform Dev Console
o API

Becoming a Pro at Unit Tests
• Accessing Private Data Members in a Test Class
• @Testvisible
• Running Test Code within Limits
• Test.startTest()
• Test.stopTest()
• Creating Test Data without Code
• Test.loadData()
• Impersonating Users in Unit Tests
• System.runAs()

Best Practices for Testing
 Test for Use case & not Code Coverage
 Check for all scenarios – valid, invalid, bulk and restricted User
 Use System.assert to prove the code behaves properly
 Create your Test Data
 Create test data before Test.startTest
 State the assumptions the tester made about the data, the
expected outcome etc. in code comments
 Never test your entire application in a single test.
•

Resources
 Testing Apex
 Running Unit Test Methods
 Building a Mock Framework with Stub API

Trailhead Modules
Apex Testing Unit Testing on Lightning Platform

The document discusses implementing advanced triggers in Apex using a trigger handler pattern. It begins with an agenda that includes challenges with triggers, trigger patterns, anatomy of a handler pattern, implementing an advanced pattern, and order of execution. It then discusses challenges like maintenance, non-deterministic execution, and infinite loops. The handler pattern is presented as a solution that enforces best practices, promotes clean code and reusability, and prevents issues. A demo is provided of implementing the pattern. Resources on triggers, patterns, and order of execution are listed along with Trailhead modules on the topic.

Episode 3 – Classes, Inheritance, Abstract Class, and InterfacesJitendra Zaa

This document provides an overview of key object-oriented programming concepts in Salesforce including classes, objects, inheritance, abstract classes, and interfaces. It discusses how classes define objects, how to instantiate objects, access specifiers, static methods, inheritance which allows extending existing classes, abstract classes which define common methods, and interfaces which enforce method signatures. Code examples are provided to demonstrate these concepts. The document also recommends books for learning Apex at different skill levels and includes an agenda and rules for the session.

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.

Episode 1 - PathToCode.comJitendra Zaa

This document provides an overview and introduction to coding in Salesforce, including why coding is needed, the developer console, naming conventions, data types, collections, pass by value vs reference, and Trailhead modules to get started. It discusses primitive data types like Boolean, Date, Decimal, and String, as well as collections like Lists, Maps, and Sets. It also covers naming conventions like camel case and pascal case.

Episode 12 - Basics of TriggerJitendra Zaa

This document provides an overview of Apex triggers in Salesforce, including: 1. Apex triggers enable custom actions before or after changes to Salesforce records like inserts, updates, or deletions. Triggers execute based on insert, update, delete, merge, upsert, or undelete operations. 2. Context variables provide information about the trigger context like isExecuting, isInsert, and record collections like new, newMap, old, and oldMap. 3. Before triggers are used to update or validate record values before they are saved, while after triggers can access system-set field values and affect other records through logging or asynchronous events. Records in after triggers are read-only.

Episode 23 - Design Pattern 3Jitendra Zaa

This document discusses a design pattern called the Facade Pattern. It summarizes that the Facade Pattern encapsulates complex systems and provides a simpler interface. It gives an example where a facade pattern is used to handle a credit card transaction in a standardized way without changing existing code. It then discusses how the Strategy Pattern could be used to support different payment types like debit cards or PayPal by deciding the payment algorithm at runtime. The document ends with announcing the next episode will be an open Q&A.

Episode 18 - Asynchronous ApexJitendra Zaa

This document discusses asynchronous Apex in Salesforce, including future methods and queueable Apex. It provides an overview of asynchronous Apex, why it is used, different asynchronous Apex approaches, and compares future methods and queueable Apex. The agenda includes explaining asynchronous Apex, reasons for using it like avoiding governor limits and allowing callouts from triggers, asynchronous governor limits, future methods, queueable Apex, and a demo.

Episode 22 - Design Pattern 2Jitendra Zaa

This document summarizes a presentation on design patterns in Salesforce development. It discusses the Singleton and Factory Method creational design patterns. It provides code examples demonstrating how to implement these patterns to solve common problems like automatically populating a field based on another field. It also discusses how to choose design patterns to optimize performance by reducing queries. The presentation concludes with reminding attendees of the next session and thanking them for their time.

Episode 2 conditional flows & loopsJitendra Zaa

Episode 17 - Handling Events in Lightning Web ComponentJitendra Zaa

This document outlines an agenda for an event on communicating between Lightning Web Components in Salesforce. It will introduce the Salesforce Playground, demonstrate communication between parent and child components and between sibling components, have a Q&A session, and provide references. The speaker is a Salesforce MVP with 23 certifications who will guide attendees through demos and answer questions to help beginners start their Salesforce coding adventure using events in Lightning Web Components.

Episode 15 - Basics of JavascriptJitendra Zaa

This document provides an overview and agenda for a session on JavaScript basics. It introduces concepts like hoisting, differences between var, let and const, arrow functions, recursion, arguments.callee, memoization, and promises. It also briefly discusses the history of JavaScript, from its creation in 1995 and renaming to JavaScript in 1996 to the introduction of EcmaScript to standardize the language. The agenda outlines explanations and demonstrations of these JavaScript fundamentals concepts.

Episode 24 - Live Q&A for getting started with SalesforceJitendra Zaa

Agile test-management-test-rail-lastestOnur Baskirt

5 Considerations When Adopting Automated TestingBhupesh Dahal

Most organizations have realized the benefits of and need for test automation—but is your investment being wisely utilized? Are you unknowingly building a test automation suite that will end up costing more than your actual product? Are you building a legacy test automation framework that may be ready to retire before you reap the benefits? This presentation will discuss five points of consideration that will help your organization answer these questions and mitigate risks that they bring into light.

Learn Key Insights from The State of Web Application Testing Research ReportSencha

In a recent study by Dimensional Research of 1,011 development and QA professionals, almost every survey respondent cited that application quality is important, with 84% believing it is very or critically important. Despite this, findings revealed that 94% of teams still face challenges when it comes to conducting adequate QA. View the presentation to learn why organizations must prioritize automated testing and QA practices to deliver high-quality applications and increase customer satisfaction.

Test Automation99pillar

Automation testing replaces or supplements manual testing by using test programs to simulate user actions. It reduces testing time and costs by running tests consistently and repeatedly. While it has upfront costs, automation saves substantially over multiple product releases. Not everything can be automated, like visual references, so some tasks still require manual testing. Tests should be automated if they are repeatable and important to run regularly, even if automation has some initial costs. The document provides an example of test automation using Quick Test Pro 8.0 for modular scripting and version control with reporting in Excel.

Sencha Roadshow 2017: Sencha Upgrades - The Good. The Bad. The Ugly - Eva Luc...Sencha

Sencha Roadshow 2017: What's New in Sencha TestSencha

Test automation engineerSadaaki Emura

This document provides an overview of test automation from the perspective of a test automation engineer. It discusses key topics like the test automation pyramid, reporting, design considerations, and deployment. The test automation pyramid emphasizes unit testing, integration testing, and end-to-end testing from the bottom to top. Reporting and metrics are important for understanding test results and efficiency. Design focuses on aspects like data-driven testing, robustness, and repeatability. Deployment involves piloting automation, maintaining scripts, and supporting evolving environments. The goal is to improve testing in areas like coverage, speed, and cost while maintaining quality.

j meteraakar gupte

The document provides an overview of JMeter, an open source tool used for load and performance testing web applications. It discusses that JMeter allows tracking performance of individual pages and objects more easily compared to manual testing. It also highlights that JMeter is easy to use, supports headless testing, and can test performance of web apps, APIs and databases. The document outlines the agenda which includes explaining what JMeter is, why it should be used, how to prepare a test plan, running tests practically and analyzing test results. It also describes different performance testing types and features of JMeter like being 100% Java based, supporting multithreading, caching results for offline analysis.

ISTQB Advanced Test Manager TrainingHiraQureshi22

This document provides information about an ISTQB Advanced Test Manager training course. The 4-day course will cover: (1) ISTQB Certified Tester Advanced Level certification and test processes; (2) test life cycles like V-Model and agile and activities like reviews and defect reporting; (3) team composition; and (4) defect management and test process improvement. The course is intended for test engineers, software engineers, testers, and quality assurance professionals seeking ISTQB Advanced Test Manager certification.

Agile Mumbai 2020 Conference | How to get the best ROI on Your Test Automati...AgileNetwork

- Writing automated tests takes a significant amount of time and effort, often resulting in test code that is twice or three times the size of the actual code being tested. This occurs because tests are written in isolation and dependencies must be mocked. - A better approach is to write tests that focus on behaviors and public interfaces rather than implementation details. Tests should not break when implementation details change, only when public behaviors change. This allows for easier refactoring of code without breaking tests. - Rather than focusing solely on unit tests, more effort should be put into system level testing which typically finds twice as many bugs. Tests can also be improved by designing them more formally and moving assertions directly into the code being tested.

Test Automation Architecture That Works by Bhupesh DahalQA or the Highway

The document discusses test automation architecture and provides recommendations for building an effective architecture. It recommends prioritizing unit testing and API/service layer testing over GUI testing to create a testing pyramid. Unit tests should be isolated and test small pieces of code, while API tests can test application logic through service calls. GUI tests should be limited in number and used to test broad end-to-end scenarios, not every small scenario. The goal is to have fewer, more stable automated tests rather than many fragile tests. Following best practices like testing different layers, prioritizing types of tests, and continuous refactoring can help create a maintainable and effective test automation architecture.

Introduction to Test Driven DevelopmentSarah Dutkiewicz

Test automation lessonSadaaki Emura

This document discusses test automation, including the purpose of test automation, the test automation process, and the test automation pyramid. The key points are: 1. Test automation aims to improve test efficiency, provide wider test coverage, reduce costs, and speed up testing. 2. The test automation process involves defining the test scope, designing tests, coding tests, setting up the test environment, running tests, and maintaining automation over time. 3. The test automation pyramid illustrates that unit tests should form the base, as they are quick to write and run, while user interface tests are at the top as they are more complex and time-consuming.

Test automation within a scrum processKushan Shalindra Amarasiri - Technical QE Specialist

This document discusses test automation within a Scrum process. It begins by providing background on the author and defining test automation. It then discusses how to start with automation, including using frameworks and learning programming skills. It describes how to plan test automation in a Scrum process, including when to automate, criteria for choosing what to automate, and how to plan the automation work. The document then discusses automating test cases, executing automation scripts, and delivering the automation work in a Scrum process. Finally, it briefly discusses some newer trends in test automation.

Test Driven Developmentdcsunu

Test-driven development (TDD) is a software development process that employs short cycles of writing a test, making it fail, then writing code to pass the test. This helps improve code design and reduces defects. Each new feature starts with writing a test case, then coding just enough to pass the test, and refactoring the code without changing external behavior. TDD produces test code documentation and allows reversible changes by starting over from the last stable state if new code causes errors.

How We Build Confidence with Continuous Integration and Automated TestingGareth Marland

Continuous integration and automated front end testing provide a small development team confidence in their work without a dedicated testing team. The solution involves running unit tests and automated front end tests on every code check-in through a continuous integration process managed across three servers for building, testing, and staging. This allows any new features to be constantly tested as they are added, catching issues early and providing confidence that changes did not break existing functionality.

Unit testing in Force.com platformChamil Madusanka

Level Up Your Salesforce Unit TestingGordon Bockus

More Related Content

What's hot (20)

Episode 2 conditional flows & loopsJitendra Zaa

Episode 17 - Handling Events in Lightning Web ComponentJitendra Zaa

Episode 15 - Basics of JavascriptJitendra Zaa

Episode 24 - Live Q&A for getting started with SalesforceJitendra Zaa

Agile test-management-test-rail-lastestOnur Baskirt

5 Considerations When Adopting Automated TestingBhupesh Dahal

Learn Key Insights from The State of Web Application Testing Research ReportSencha

Test Automation99pillar

Sencha Roadshow 2017: Sencha Upgrades - The Good. The Bad. The Ugly - Eva Luc...Sencha

Sencha Roadshow 2017: What's New in Sencha TestSencha

Test automation engineerSadaaki Emura

j meteraakar gupte

ISTQB Advanced Test Manager TrainingHiraQureshi22

Agile Mumbai 2020 Conference | How to get the best ROI on Your Test Automati...AgileNetwork

Test Automation Architecture That Works by Bhupesh DahalQA or the Highway

Introduction to Test Driven DevelopmentSarah Dutkiewicz

Test automation lessonSadaaki Emura

Test automation within a scrum processKushan Shalindra Amarasiri - Technical QE Specialist

Test Driven Developmentdcsunu

How We Build Confidence with Continuous Integration and Automated TestingGareth Marland

Episode 2 conditional flows & loopsJitendra Zaa

Episode 17 - Handling Events in Lightning Web ComponentJitendra Zaa

Episode 15 - Basics of JavascriptJitendra Zaa

Episode 24 - Live Q&A for getting started with SalesforceJitendra Zaa

Agile test-management-test-rail-lastestOnur Baskirt

5 Considerations When Adopting Automated TestingBhupesh Dahal

Learn Key Insights from The State of Web Application Testing Research ReportSencha

Test Automation99pillar

Sencha Roadshow 2017: Sencha Upgrades - The Good. The Bad. The Ugly - Eva Luc...Sencha

Sencha Roadshow 2017: What's New in Sencha TestSencha

Test automation engineerSadaaki Emura

j meteraakar gupte

ISTQB Advanced Test Manager TrainingHiraQureshi22

Agile Mumbai 2020 Conference | How to get the best ROI on Your Test Automati...AgileNetwork

Test Automation Architecture That Works by Bhupesh DahalQA or the Highway

Introduction to Test Driven DevelopmentSarah Dutkiewicz

Test automation lessonSadaaki Emura

Test automation within a scrum processKushan Shalindra Amarasiri - Technical QE Specialist

Test Driven Developmentdcsunu

How We Build Confidence with Continuous Integration and Automated TestingGareth Marland

Similar to Episode 5 - Writing unit tests in Salesforce (20)

Unit testing in Force.com platformChamil Madusanka

Level Up Your Salesforce Unit TestingGordon Bockus

Database Unit Testing Made Easy with VSTSSanil Mhatre

This document discusses database unit testing using Visual Studio Team System (VSTS). It begins with an overview of software testing basics and unit testing principles. It then covers database unit testing terminology, principles of isolation and independence, and testable interfaces of stored procedures. The document outlines different levels of unit testing and factors to consider. It demonstrates implementing database unit testing in VSTS 2010 and new features in VSTS 2012. The goal is to show how VSTS can be used to test database code and improve quality.

An Introduction to Unit TestingSahar Nofal

Unit testing involves writing automated tests to test code. Automated tests are repeatable and help catch bugs before deploying code. The main benefits of unit testing are that it allows developers to test code frequently and in less time, catch bugs before deploying, deploy with confidence, reduce bugs in production, and refactor code with confidence. There are different types of tests including unit tests, integration tests, and end-to-end tests. Unit tests isolate a unit of code without external dependencies and execute fast but provide less confidence. Integration tests involve external dependencies and provide more confidence but take longer. End-to-end tests drive the application through its UI and provide great confidence but are slow. Good unit tests

Beginners overview of automated testing with Rspecjeffrey1ross

The document provides an overview of automated testing for beginning developers, covering testing basics like unit tests and code coverage, popular Ruby testing tools and techniques like RSpec and Capybara, the benefits of automated testing like improved code quality and efficiency, and strategies for testing models, controllers, and views. It also discusses testing patterns and principles like the inverted testing pyramid, page object pattern, and single responsibility principle.

Test Driven DevelopmentSergey Aganezov

The document outlines an upcoming programming workshop that will cover various JetBrains IDEs like PyCharm, IntelliJ IDEA, and PhpStorm. It then discusses Test Driven Development (TDD), including what TDD is, the development cycle used in TDD, and benefits like encouraging simple designs and confidence. Different types of software tests are also listed like unit tests, integration tests, acceptance tests, and others. Specific testing techniques like unit testing, integration testing using bottom-up and top-down approaches, and acceptance testing are then explained at a high level. Finally, some important notes on testing like trusting tests and prioritizing maintainability are provided.

Software TestingKLabCyscorpions-TechBlog

This document provides an overview of software testing, including why testing is important to avoid crashes and help write better code. It describes different testing strategies like automated, manual, and exploratory testing. It also outlines different types of tests like unit, integration, and functional testing. Test cases are defined as activities with expected and actual results. Black box and white box testing approaches are mentioned. The document also provides details on XCTest, a testing framework for iOS and OS X, including its features like test navigation, filtering failures, and running tests.

Testing AngularLilia Sfaxi

Unit testing and end-to-end testing are important for Angular applications. The document discusses various types of tests, including unit tests, integration tests, and end-to-end tests. It also covers tools for testing Angular applications, such as Jasmine for writing unit tests, Karma as a test runner, Protractor for end-to-end tests, and Angular testing utilities. The document provides recommendations on testing components and services, including how to set up tests and write tests with dependencies.

Tdd for phpABDEL RAHMAN KARIM

This document discusses test-driven development (TDD) using PHP. It explains that unit testing is important for testing business logic and APIs to avoid defects and keep code well-designed and loosely coupled. Unit tests should confirm the functionality of small units of code. An effective test infrastructure includes a unit test runner, unit tests, test libraries, and the source code being tested. Tests for a stars API that returns asterisks based on a number passed in should include tests for negative numbers returning errors, zero printing no stars, and positive numbers printing the correct number of stars. Unit tests should consume public APIs, be in a separate project, run repeatably and independently in any order, start with easy cases first, and have one

An Introduction to Unit Test Using NUnitweili_at_slideshare

This document provides an introduction to unit testing using the NUnit framework. It defines unit testing as developer tests that validate code works as expected. Unit tests are part of the construction cycle and sit between technical design and QA testing in the software development lifecycle. Benefits of unit testing include early defect detection, better code design, regression protection, and learning new APIs. The document then describes NUnit attributes that mark test fixtures and methods. It also covers NUnit assertions for verification. Examples are provided of test-driven development and using NUnit for continuous integration.

Get Testing with tSQLt - SQL In The City Workshop 2014Red Gate Software

Microsoft Fakes, Unit Testing the (almost) Untestable CodeAleksandar Bozinovski

Unit Tests with Microsoft FakesAleksandar Bozinovski

This document discusses unit testing and the Microsoft Fakes framework. It begins with an overview of different types of software tests like unit tests, integration tests, and user acceptance tests. It then discusses why unit tests are important and some conventions for writing unit tests. Dependencies and coupling are mentioned as challenges for unit testing. The document introduces Microsoft Fakes as a framework that helps isolate code for testing by replacing dependencies with stubs or shims. It provides examples of how to generate and use stubs and shims. In the end, it summarizes when to use stubs versus shims and takes questions from the audience.

May: Automated Developer Testing: Achievements and ChallengesTriTAUG

Developer testing, a common step in software development, involves generating sufficient test inputs and checking the behavior of the program under test during the execution of the test inputs. Complicated logics inside a method make generating appropriate arguments difficult. In testing object-oriented programs, generating method sequences to put the receiver object or argument objects into appropriate states further complicates test-input generation. After the generated test inputs are executed, program crashes or uncaught exceptions can be used to indicate program problems, especially robustness problems. However, some program problems such as producing wrong program outputs do not crash the program. In this talk, the speaker will present an overview of achievements and challenges in improving automation in developer testing, especially on test-input generation (i.e., generating sufficient test inputs) and test oracles (i.e., checking the behavior of the program under test). About the speaker: Tao Xie is an Associate Professor in the Department of Computer Science of the College of Engineering at North Carolina State University. He received his Ph.D. in Computer Science from the University of Washington in 2005. Before that, he received an M.S. in Computer Science from the University of Washington in 2002, an M.S. in Computer Science from Peking University in 2000, and a B.S. in Computer Science from Fudan University in 1997. He worked as a visiting researcher at Microsoft Research Redmond and Microsoft Research Asia. His research interests are in software engineering, focusing on automated software testing and mining software engineering data. He has published more than 100 research papers in refereed journals and conference proceedings in the area of software engineering. Besides doing research, he has contributed to understanding the software engineering research community. He has served as the ACM SIGSOFT History Liaison in the SIGSOFT Executive Committee as well as serving in the ACM History Committee. He received a National Science Foundation Faculty Early Career Development (CAREER) Award in 2009. He received 2008, 2009, and 2010 IBM Faculty Awards and a 2008 IBM Jazz Innovation Award. He received 2010 North Carolina State University Sigma Xi Faculty Research Award. He received the ASE 2009 Best Paper Award and an ACM SIGSOFT Distinguished Paper Award. He was Program Co-Chair of 2009 IEEE International Conference on Software Maintenance (ICSM) and is Program Co-Chair of 2011 and 2012 International Working Conference on Mining Software Repositories (MSR).

Agile Acceptance testing with FitnesseClareMcLennan

Tools for Software TestingMohammed Moishin

Testing JavaScriptdhtml

This document discusses testing in JavaScript and XP methodologies. It defines different types of testing like unit testing and acceptance testing. It explains that testing verifies systems work as intended. There are internal qualities like ease of maintenance and external qualities like fulfilling requirements. Benefits of testing include facilitating change, ensuring all code paths work, and leading to cleaner code. Challenges include the hard work of testing and requiring team commitment. Examples of test cases and suites are provided along with tools for testing.

Test Driven DevelopmentZendCon

End-end tests as first class citizens - SeleniumConf 2020Abhijeet Vaikar

Agile Software Testing the Agilogy WayJordi Pradel

At Agilogy we have a curated way of testing software. In these slides we share basic Principles, Patterns and Strategies to test software in Hexagonal Architectures. Defying the typical test pyramid, we focus our testing strategy on testing the whole domain. To do so, we avoid the abuse of mocks and stubs and, instead, we use hand-crafted test fakes that behave like their production counterparts. We make sure they actually do so by testing both the production driven adapters and their fakes with the very same test suite.

Unit testing in Force.com platformChamil Madusanka

Level Up Your Salesforce Unit TestingGordon Bockus

Database Unit Testing Made Easy with VSTSSanil Mhatre

An Introduction to Unit TestingSahar Nofal

Beginners overview of automated testing with Rspecjeffrey1ross

Test Driven DevelopmentSergey Aganezov

Software TestingKLabCyscorpions-TechBlog

Testing AngularLilia Sfaxi

Tdd for phpABDEL RAHMAN KARIM

An Introduction to Unit Test Using NUnitweili_at_slideshare

Get Testing with tSQLt - SQL In The City Workshop 2014Red Gate Software

Microsoft Fakes, Unit Testing the (almost) Untestable CodeAleksandar Bozinovski

Unit Tests with Microsoft FakesAleksandar Bozinovski

May: Automated Developer Testing: Achievements and ChallengesTriTAUG

Agile Acceptance testing with FitnesseClareMcLennan

Tools for Software TestingMohammed Moishin

Testing JavaScriptdhtml

Test Driven DevelopmentZendCon

End-end tests as first class citizens - SeleniumConf 2020Abhijeet Vaikar

Agile Software Testing the Agilogy WayJordi Pradel

More from Jitendra Zaa (18)

Episode 21 - Design Pattern 1Jitendra Zaa

The document provides an overview of design patterns and principles for software development. It discusses the SOLID principles of open/closed, single responsibility, Liskov substitution, interface segregation and dependency inversion. It defines design patterns as common solutions to recurring problems in software design. The Gang of Four are introduced as authors of a seminal book on design patterns, categorizing 23 patterns into creational, structural and behavioral groups. The session concludes with soliciting questions and announcing the next topic.

Episode 19 - Asynchronous Apex - Batch apex & schedulersJitendra Zaa

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.

Episode 16 - Introduction to LWCJitendra Zaa

The document provides an agenda and overview for an introduction to Lightning Web Components (LWC) presentation. It discusses the pillars of modern web development, why LWC was developed, the development tools needed for LWC, the anatomy of an LWC, the LWC lifecycle methods, decorators used in LWC, includes demos of creating an LWC and a Hello World component, compares LWC to Aura components, and lists additional resources. The presentation aims to give attendees an understanding of LWC fundamentals.

Introduction to mulesoft - Alpharetta Developer Group MeetJitendra Zaa

This document provides an introduction and overview of Mulesoft. It discusses Mulesoft's history, from its founding in 2006 to its acquisition by Salesforce in 2018. It also outlines Mulesoft's API-led approach to integration and its deployment models, including runtime manager to cloudhub, cloud console to your own servers in a hybrid model, and on-premises console to on-premises deployment. The agenda includes presentations on Mulesoft history, API-led connectivity, deployment models, demos, and a Q&A session.

Episode 11 building & exposing rest api in salesforce v1.0Jitendra Zaa

Episode 10 - External Services in SalesforceJitendra Zaa

This document provides an overview and agenda for setting up and using external services in Salesforce Flow (Visual Workflow). It begins with introducing external services as a way to consume APIs without code. It then outlines the steps to set up a named credential and register an external service. This is followed by a live demo of how to use external services in a Flow. Resources for learning more about external services on Trailhead are provided at the end.

Episode 14 - Basics of HTML for SalesforceJitendra Zaa

This document provides an agenda and overview for an introduction to HTML coding basics. It includes 3 sentences: The document outlines an agenda to cover introduction to HTML tags, text formatting, headings, paragraphs, comments, images, links, lists, forms, tables, cascading style sheets (CSS), and various CSS properties. It provides examples of common HTML elements and tags as well as how to structure an HTML page and insert different types of content. The session will conclude with allowing time for questions and answers.

South East Dreamin 2019Jitendra Zaa

This document discusses setting up Continuous Integration using SalesforceDX and Jenkins. It covers: 1. The problem of long, complex builds and the need to reduce time from development to production. 2. An overview of Jenkins and why it is used for Continuous Integration, including that it is open source and has over 1000 plugins. 3. The history and evolution of Jenkins from its origins in Hudson to becoming the dominant CI tool today. 4. The concepts of Continuous Integration, Continuous Delivery, and Continuous Deployment and how branching strategies fit in. 5. A demo of setting up Jenkins and SFDX for Continuous Integration, including creating certificates, connected apps, environment variables, and Jenkins projects

Episode 9 - Building soap integrations in salesforceJitendra Zaa

Episode 8 - Path To Code - Integrate Salesforce with external system using R...Jitendra Zaa

Episode 6 - DML, Transaction and Error handling in SalesforceJitendra Zaa

This document provides an agenda and overview for a session on performing data manipulation language (DML) operations and handling errors in Salesforce. It discusses how to insert, update, delete, upsert, undelete, and merge records using DML. It also covers bulk DML, database methods for DML, transaction control using savepoints and rollbacks, and handling errors. The session aims to teach attendees how to manipulate records and handle errors when working with data in Salesforce.

Lightning Web Component in SalesforceJitendra Zaa

1. Lightning Web Components introduce a new programming model built on modern web standards that provides enhanced productivity, performance, and compatibility. 2. They allow more code to be executed by the browser instead of JavaScript abstractions for improved performance. 3. Lightning Web Components can coexist and interoperate with existing Lightning components and can be composed with clicks or code.

Episode 4 - Introduction to SOQL in SalesforceJitendra Zaa

SOQL is used to query records from the Salesforce database. It includes clauses like SELECT, FROM, WHERE, GROUP BY, HAVING, ORDER BY, and LIMIT. The WHERE clause restricts rows returned using conditions, operators like equal, not equal, less than and logical operators. Relationship and aggregate functions can also be used. SOQL in Apex allows querying records in batches of 200 using for loops. SOSL performs full text searches across objects and includes clauses like FIND, IN, and RETURNING.

Build sfdx plugin in 15 minutesJitendra Zaa

The document discusses how to build a Salesforce DX plugin in 15 minutes. It provides an overview of Salesforce DX and the Salesforce CLI. Salesforce DX allows developers to create custom plugins on top of the Salesforce CLI. The presenters demonstrate how to generate a basic Salesforce DX plugin using the plugin generator. It requires knowledge of Node.js, TypeScript, and using Yarn for dependency management. The plugin can then connect to Salesforce orgs and use the REST API. Resources are provided to learn more about Salesforce DX, the CLI, and creating custom plugins.

Salesforce Org lifecycle management : empowering adminsJitendra Zaa

Salesforce Lightning Data ServiceJitendra Zaa

Lightning Data Service allows developers to build custom components that can access and manipulate standard and custom object data without writing any Apex code. It provides a standard controller that handles data retrieval, caching, offline access, and notifications of record changes for custom components. Developers simply add the <force:recordData> component to their custom components to access and display record data. Current limitations include lack of support for some standard objects and formatted field values. The roadmap includes general availability in Winter '18 along with additional features like bulk data support and server-side triggers.

Connecticut Salesforce Developer Group - Jan 2017Jitendra Zaa

This document summarizes a meetup for the Connecticut Salesforce Developer Group that covered new features in Winter '17 and Spring '17. The agenda included networking, guest speakers, demonstrations of the composite REST API, reCAPTCHA for spam prevention in Web-to-Lead, and features like TLS 1.0 disabling and utility bars being added to Lightning. It also mentioned changes for Omni-Channel, developing Lightning components, monitoring Apex batch jobs, and allowing test setup methods and callouts from queueable jobs in Apex.

Salesforce winter 16 releaseJitendra Zaa

Salesforce Winter 16 release includes several new features such as: - The Lightning App builder allows editing Record pages in pilot release. - Process builders now allow scheduling multiple actions and are bulkified to improve performance. - Lookup fields can now be added to Activity objects. - Files uploaded via Chatter are available in a related list on records. - Global picklists allow reusing a single picklist across objects.

Episode 21 - Design Pattern 1Jitendra Zaa

Episode 19 - Asynchronous Apex - Batch apex & schedulersJitendra Zaa

Episode 16 - Introduction to LWCJitendra Zaa

Introduction to mulesoft - Alpharetta Developer Group MeetJitendra Zaa

Episode 11 building & exposing rest api in salesforce v1.0Jitendra Zaa

Episode 10 - External Services in SalesforceJitendra Zaa

Episode 14 - Basics of HTML for SalesforceJitendra Zaa

South East Dreamin 2019Jitendra Zaa

Episode 9 - Building soap integrations in salesforceJitendra Zaa

Episode 8 - Path To Code - Integrate Salesforce with external system using R...Jitendra Zaa

Episode 6 - DML, Transaction and Error handling in SalesforceJitendra Zaa

Lightning Web Component in SalesforceJitendra Zaa

Episode 4 - Introduction to SOQL in SalesforceJitendra Zaa

Build sfdx plugin in 15 minutesJitendra Zaa

Salesforce Org lifecycle management : empowering adminsJitendra Zaa

Salesforce Lightning Data ServiceJitendra Zaa

Connecticut Salesforce Developer Group - Jan 2017Jitendra Zaa

Salesforce winter 16 releaseJitendra Zaa

Recently uploaded (20)

Unit 6_Introduction_Phishing_Password Cracking.pdfKanchanPatil34

Exploring-Substances-Acidic-Basic-and-Neutral.pdfSandeep Swamy

Exploring Substances: Acidic, Basic, and Neutral Welcome to the fascinating world of acids and bases! Join siblings Ashwin and Keerthi as they explore the colorful world of substances at their school's National Science Day fair. Their adventure begins with a mysterious white paper that reveals hidden messages when sprayed with a special liquid. In this presentation, we'll discover how different substances can be classified as acidic, basic, or neutral. We'll explore natural indicators like litmus, red rose extract, and turmeric that help us identify these substances through color changes. We'll also learn about neutralization reactions and their applications in our daily lives. by sandeep swamy

Social Problem-Unemployment .pptx notes for Physiotherapy StudentsDrNidhiAgarwal

Unemployment is a major social problem, by which not only rural population have suffered but also urban population are suffered while they are literate having good qualification.The evil consequences like poverty, frustration, revolution result in crimes and social disorganization. Therefore, it is necessary that all efforts be made to have maximum. employment facilities. The Government of India has already announced that the question of payment of unemployment allowance cannot be considered in India

Introduction to Vibe Coding and Vibe EngineeringDamian T. Gordon

World war-1(Causes & impacts at a glance) PPT by Simanchala Sarab(BABed,sem-4...larencebapu132

Niamh Lucey, Mary Dunne. Health Sciences Libraries Group (LAI). Lighting the ...Library Association of Ireland

Ultimate VMware 2V0-11.25 Exam Dumps for Exam SuccessMark Soia

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.

YSPH VMOC Special Report - Measles Outbreak Southwest US 4-30-2025.pptxYale School of Public Health - The Virtual Medical Operations Center (VMOC)

A measles outbreak originating in West Texas has been linked to confirmed cases in New Mexico, with additional cases reported in Oklahoma and Kansas. The current case count is 795 from Texas, New Mexico, Oklahoma, and Kansas. 95 individuals have required hospitalization, and 3 deaths, 2 children in Texas and one adult in New Mexico. These fatalities mark the first measles-related deaths in the United States since 2015 and the first pediatric measles death since 2003. The YSPH Virtual Medical Operations Center Briefs (VMOC) were created as a service-learning project by faculty and graduate students at the Yale School of Public Health in response to the 2010 Haiti Earthquake. Each year, the VMOC Briefs are produced by students enrolled in Environmental Health Science Course 581 - Public Health Emergencies: Disaster Planning and Response. These briefs compile diverse information sources – including status reports, maps, news articles, and web content– into a single, easily digestible document that can be widely shared and used interactively. Key features of this report include: - Comprehensive Overview: Provides situation updates, maps, relevant news, and web resources. - Accessibility: Designed for easy reading, wide distribution, and interactive use. - Collaboration: The “unlocked" format enables other responders to share, copy, and adapt seamlessly. The students learn by doing, quickly discovering how and where to find critical information and presenting it in an easily understood manner.

Phoenix – A Collaborative Renewal of Children’s and Young People’s Services C...Library Association of Ireland

Operations Management (Dr. Abdulfatah Salem).pdfArab Academy for Science, Technology and Maritime Transport

How to Subscribe Newsletter From Odoo 18 WebsiteCeline George

Biophysics Chapter 3 Methods of Studying Macromolecules.pdfPKLI-Institute of Nursing and Allied Health Sciences Lahore , Pakistan.

This chapter provides an in-depth overview of the viscosity of macromolecules, an essential concept in biophysics and medical sciences, especially in understanding fluid behavior like blood flow in the human body. Key concepts covered include: ✅ Definition and Types of Viscosity: Dynamic vs. Kinematic viscosity, cohesion, and adhesion. ⚙️ Methods of Measuring Viscosity: Rotary Viscometer Vibrational Viscometer Falling Object Method Capillary Viscometer 🌡️ Factors Affecting Viscosity: Temperature, composition, flow rate. 🩺 Clinical Relevance: Impact of blood viscosity in cardiovascular health. 🌊 Fluid Dynamics: Laminar vs. turbulent flow, Reynolds number. 🔬 Extension Techniques: Chromatography (adsorption, partition, TLC, etc.) Electrophoresis (protein/DNA separation) Sedimentation and Centrifugation methods.

How to Manage Opening & Closing Controls in Odoo 17 POSCeline George

How to Customize Your Financial Reports & Tax Reports With Odoo 17 AccountingCeline George

Presentation of the MIPLM subject matter expert Erdem KayaMIPLM

Metamorphosis: Life's Transformative JourneyArshad Shaikh

One Hot encoding a revolution in Machine learningmomer9505

UNIT 3 NATIONAL HEALTH PROGRAMMEE. SOCIAL AND PREVENTIVE PHARMACYDR.PRISCILLA MARY J

Geography Sem II Unit 1C Correlation of Geography with other school subjectsProfDrShaikhImran