Continuous integration of cloud based applications using a combination of technologies: Visual Force, Apex, Selenium, Jenkins, Ant, & YUI test framework
This document discusses automating Salesforce development workflows using Jenkins and Git. It provides an overview of Jenkins and the Force.com Migration Tool for versioning Salesforce metadata. The document proposes using these tools to improve upon manual folder backups by allowing for collaboration, change logging, and automation. It then demonstrates a sample nightly Jenkins job that checks out metadata from Git, downloads the latest from Salesforce using the Migration Tool, and commits the changes back to the Git repository. Code reviews can then be facilitated through the online Git hosting.
This document tells the story of how a class project evolved into a company with thousands of engineers and millions of lines of code using continuous integration practices over 15 years. It describes how the project started with manual code sharing and testing, then adopted version control and regular integration. It details how the company scaled up practices like automated builds, testing, and failure tracking to support growth from 2 people to thousands of engineers and over 200,000 tests while maintaining quality. The key takeaways are shortening feedback loops through practices like continuous integration, adopting principles like versioning everything and automating as much as possible, and having scalable solutions at each stage of growth.
The document discusses using source control and automation tools like GitHub and Ant to support team development on the Force.com platform. It covers topics like org topologies for different team structures, using Git for source control management across multiple developers and orgs, and automating deployments between orgs using the Force.com Migration Tool triggered by pushes to a GitHub repository. The presentation provides an overview of these tools and techniques and includes demonstrations of integrating a Force.com project with GitHub and automating deployments.
Continuous Integration - Software development lifecycle for Force.com projectsAldo Fernandez
Continuous integration refers to the practice of frequently integrating and testing code, rather than waiting until the end of a project or development cycle. The practice of continuous integration is a well established best practice that has been used with software development across multiple platforms and languages.
Implementing an automated continuous integration system usually involves a source code repository, used to store the code during team development, and a continuous integration tool that polls the repository for changes and automatically builds and deploys the code in a sandbox.
Automating the Impossible: End to End Team Development for ISVs (October 14, ...Salesforce Partners
This document discusses automating the development process for managed packages on the Salesforce platform. It describes how the Nonprofit Starter Pack team uses automation tools like GitHub, Jenkins, CumulusCI and Ant to implement version control, continuous integration, and frequent releases. Key benefits of this approach include improved team productivity, reduced errors, and savings of over 4,500 development hours per year. Local unmanaged packages allow development entirely in metadata and help address challenges of developing managed packages in unmanaged orgs.
This document discusses best practices for team development on the Salesforce platform. It recommends using version control, separate development environments for each developer, unit testing, and continuous integration. It describes two common development scenarios: non-package development using a shared repository and developer sandboxes, and package development using developer orgs connected to a shared repository. Key challenges include managing dependencies on managed packages and avoiding namespace prefix issues when deploying to multiple orgs. The Ant Migration Tool is recommended for automating deployments in continuous integration.
Introduction to Enterprise-Release Engineering on the Salesforce PlatformSalesforce Developers
Managing multiple release schedules, workstreams, and code versions is a critical task to ensure your salesforce.com organization maintains security, integrity, and the ability to stay flexible. Join us to learn how to set up a governing team, how to size up what goes into a release, and how to use Github, Jenkins, and the ant deployment tools. You'll leave ready to develop your own release strategy for managing enterprise-level deployments and improvements.
Join us to learn how the Force.com Migration Tool is a powerful instrument for deploying code and configuring salesfoce.com. The Ant-based tool offers the ability to take a snapshot of your code and configuration, which you can then store in any source code management system such as Git. These snapshots can be used to restore, in part or in whole, your org to a previous state. In addition to recovery, if we stack these snapshots we can use them for forensic purposes to find when a Salesforce environment changed.
Dreamforce 13 developer session: Git for Force.com developersJohn Stevenson
Git is a powerful version control tool and this presentation shows how Force.com developers can make use of Git in their projects.
Including tips and tricks, this presentation covers the core commands you need to know to use Git effectively. We also cover using Git from the Force.com IDE.
This document provides an overview of using Git for Force.com development. It discusses the value of Git for managing code changes over time, experimenting with branching, and collaborating easily. It then covers basic Git commands like init, add, commit, status, diff and push. It shows how to set up a Git repository with the Force.com IDE and walks through a sample project of creating an Apex class and committing it locally and to GitHub for collaboration. It provides tips for naming projects, committing changes, and driving all changes through Git.
This document discusses Salesforce's approach to Selenium testing at scale. Some key points:
- Salesforce runs over 1 million browser tests per day across thousands of VMs.
- They use WebDriver to test against a live application across many browser and OS combinations.
- Proper use of page objects is important to encapsulate Selenium and allow tests to scale.
- Challenges include assigning failures, non-deterministic tests, browser and Selenium version upgrades.
Join us for an overview of behavior-driven development and test automation, which aided in the production of a Visualforce/JavaScript application for an enterprise client. Using Cucumber JVM, Selenium, Jenkins, and Git - the team was able to catch regression errors during development. We'll provide an overview of the solution used and how it worked in a real-world environment.
Triggers for Admins: A Five-step Framework for Creating TriggersSalesforce Developers
Have you felt intimidated by the thought of writing code? Are you an experienced Salesforce Administrator and would like to take the leap into writing your own Apex triggers? Join us to gain the tools and confidence to write your first trigger. Using specific examples and real-life scenarios, we'll walk through a concrete framework to approach the process of planning, designing, and coding a trigger.
This document discusses using branch orgs and continuous integration to address challenges with namespace collisions when multiple developers work in the same Salesforce org. Branch orgs allow sharing the same namespace across orgs, simplifying development. Webpack is mentioned as a way to bundle JavaScript to avoid collisions. The document also covers strategies for managing CSS collisions when components share the DOM. Branch orgs are currently in pilot with general availability planned for Summer 2016.
This document summarizes a webinar on Continuous Integration (CI) and Continuous Deployment (CD) on Salesforce. It introduces CI/CD, their importance and challenges. It outlines best practices for implementing CI/CD on Salesforce, including using version control, frequent small commits, quick smoke tests, staging environments, and deployment tools like Force Migration Tool (ANT). The webinar presenters then demonstrate the CI/CD process and implementation using ANT build files, source control, and a build server.
Salesforce API Series: Release Management with the Metadata API webinarSalesforce Developers
The Metadata API allows you to make changes to your Salesforce instance and then deploy those changes through sandboxes to production. There are many tools, both Salesforce-provided or community developed, that allow you to interact with the Metadata API. The API is a fundamental part of release management but actually managing the “change” is what literally makes or breaks an implementation. This webinar focuses on building automation into your release management process using commonly available enterprise tools.
Key Takeaways
:: Learn about the Metadata API and some common API calls
:: Explore the tools built on top of the API
:: Learn how to leverage a version control system manage multiple development streams
:: Build deployment pipelines with automated testing
Intended Audience
:: Force.com Developers / Quality Assurance, Technical Leads, Architects, Application Directors
Make testing easier and more productive by applying test-driven development strategies to the world of iOS and Objective-C. Join us to learn about the tools that are available, and hear strategies for writing more testable code and robust tests. You'll be ready to take the next step and integrate these strategies into your daily workflow.
Even the most successful projects can be derailed by a poor deployment. Join us as we discuss the plans, tools, and strategies that are critical to a successful deployment. We'll also review common mistakes that administrators, developers, and project managers make that can doom a deployment before it's even begun. We'll demonstrate deployment with both point and click tools such as Change Sets, as well as developer tools like Eclipse and Ant.
Techniques and Tools to Improve the Salesforce Development CycleSalesforce Developers
The document discusses techniques and tools to improve the Salesforce development cycle. It covers establishing reusable development organizations, managing source code with version control, implementing automated testing, developing features in isolation, and integrating continuous integration practices. Reusable orgs allow multiple developers to work independently. Version control with branching enables collaborative development. Automated testing validates code changes. Isolated feature development prevents conflicts. Continuous integration merges and deploys changes across environments.
5 Essentials for Simplifiied Release Management and Continuous DeliverySalesforce Developers
Having a smooth product release cycle is critical in today's World of software development. Join this session to learn about the essentials of Continuous Delivery which will include Version Control Integration, Deployment Automation,Test Automation and Data Migration.
Testing CRM from a 360 View - extremeCRM Rome 2013Wael Hamze
Learn how to test different aspects of your dynamics CRM deployment. Starting from unit tests for plug-ins, custom workflow activities, JavaScript and then moving to integration testing and UI level testing.
With the new Lightning Editions of Salesforce, everyone now has plenty of sandboxes available to put together a robust change/release management process. Join us as we talk about how to maximize the use of your sandboxes, including refresh cycles, Sandbox templates, Change Set & Package flow between environments, Single Sign-on through Environment Hub, and more.
See the video of this presentation here: https://www.salesforce.com/video/306450/
and more details here:
https://success.salesforce.com/Sessions?eventId=a1Q3000000qQOd9#/session/a2q3A000000LBfmQAG
Webinar: From Sandbox to Production: Demystifying Force.com Release Managemen...Salesforce Developers
Ever wonder how to plan to customize your production org? Do you know when to use a developer sandbox? Stumped on how to reliably move changes around? We'll show you how in this webinar. Learn the best practices from the pros.
Salesforce gives you the ability to create copies of your production org in a separate sandbox environment for a variety of purposes like testing and training without compromising the data and applications in your Salesforce production organization. Learn some of the key considerations that lead to effective Release Management.
Key Takeaways
:: Understand how to move code and configuration utilizing change sets.
:: Best practices for org management/governance.
Intended Audience
:: This webinar is geared towards all Force.com developers.
:: Not scoped to ISV developers.
:: Tailored toward customers with one sandbox, small dev team, and limited number of customization projects.
Leverage Team Foundation to focus on application development, decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle.
Continuous Delivery with TFS msbuild msdeployPeter Gfader
This document discusses automating software deployments using tools like msbuild and msdeploy to enable continuous deployment and delivery. It outlines the pain points of manual deployments and goals of automating deployments. It provides guidance on setting up continuous integration, automated testing, packaging, and configuration for both new systems and existing environments. It also lists best practices like deploying early, having rollback plans, logging builds, and automating as much as possible.
This document discusses DevOps practices at Salesforce, including:
- Using continuous delivery pipelines to plan, build, test, release, deploy and monitor code changes.
- Organizing teams using a Scrum model with sprints every two weeks and an average size of 7 engineers per team.
- Maintaining sandbox environments like development, test, UAT and production for each project.
- Following a branching strategy in version control and using continuous integration to test and deploy code changes.
Salesforce Developer Workshop for GDF Suez HackathonPeter Chittum
This document provides an agenda and overview for a GDF Suez Hackathon Workshop on the Salesforce platform. The agenda covers platform basics, Apex, Visualforce, reports, integration, and Salesforce1. It discusses concepts like multi-tenancy, declarative vs. programmatic development, the data model, APIs, and recommends exercises and resources for learning more.
Dreamforce 13 developer session: Git for Force.com developersJohn Stevenson
Git is a powerful version control tool and this presentation shows how Force.com developers can make use of Git in their projects.
Including tips and tricks, this presentation covers the core commands you need to know to use Git effectively. We also cover using Git from the Force.com IDE.
This document provides an overview of using Git for Force.com development. It discusses the value of Git for managing code changes over time, experimenting with branching, and collaborating easily. It then covers basic Git commands like init, add, commit, status, diff and push. It shows how to set up a Git repository with the Force.com IDE and walks through a sample project of creating an Apex class and committing it locally and to GitHub for collaboration. It provides tips for naming projects, committing changes, and driving all changes through Git.
This document discusses Salesforce's approach to Selenium testing at scale. Some key points:
- Salesforce runs over 1 million browser tests per day across thousands of VMs.
- They use WebDriver to test against a live application across many browser and OS combinations.
- Proper use of page objects is important to encapsulate Selenium and allow tests to scale.
- Challenges include assigning failures, non-deterministic tests, browser and Selenium version upgrades.
Join us for an overview of behavior-driven development and test automation, which aided in the production of a Visualforce/JavaScript application for an enterprise client. Using Cucumber JVM, Selenium, Jenkins, and Git - the team was able to catch regression errors during development. We'll provide an overview of the solution used and how it worked in a real-world environment.
Triggers for Admins: A Five-step Framework for Creating TriggersSalesforce Developers
Have you felt intimidated by the thought of writing code? Are you an experienced Salesforce Administrator and would like to take the leap into writing your own Apex triggers? Join us to gain the tools and confidence to write your first trigger. Using specific examples and real-life scenarios, we'll walk through a concrete framework to approach the process of planning, designing, and coding a trigger.
This document discusses using branch orgs and continuous integration to address challenges with namespace collisions when multiple developers work in the same Salesforce org. Branch orgs allow sharing the same namespace across orgs, simplifying development. Webpack is mentioned as a way to bundle JavaScript to avoid collisions. The document also covers strategies for managing CSS collisions when components share the DOM. Branch orgs are currently in pilot with general availability planned for Summer 2016.
This document summarizes a webinar on Continuous Integration (CI) and Continuous Deployment (CD) on Salesforce. It introduces CI/CD, their importance and challenges. It outlines best practices for implementing CI/CD on Salesforce, including using version control, frequent small commits, quick smoke tests, staging environments, and deployment tools like Force Migration Tool (ANT). The webinar presenters then demonstrate the CI/CD process and implementation using ANT build files, source control, and a build server.
Salesforce API Series: Release Management with the Metadata API webinarSalesforce Developers
The Metadata API allows you to make changes to your Salesforce instance and then deploy those changes through sandboxes to production. There are many tools, both Salesforce-provided or community developed, that allow you to interact with the Metadata API. The API is a fundamental part of release management but actually managing the “change” is what literally makes or breaks an implementation. This webinar focuses on building automation into your release management process using commonly available enterprise tools.
Key Takeaways
:: Learn about the Metadata API and some common API calls
:: Explore the tools built on top of the API
:: Learn how to leverage a version control system manage multiple development streams
:: Build deployment pipelines with automated testing
Intended Audience
:: Force.com Developers / Quality Assurance, Technical Leads, Architects, Application Directors
Make testing easier and more productive by applying test-driven development strategies to the world of iOS and Objective-C. Join us to learn about the tools that are available, and hear strategies for writing more testable code and robust tests. You'll be ready to take the next step and integrate these strategies into your daily workflow.
Even the most successful projects can be derailed by a poor deployment. Join us as we discuss the plans, tools, and strategies that are critical to a successful deployment. We'll also review common mistakes that administrators, developers, and project managers make that can doom a deployment before it's even begun. We'll demonstrate deployment with both point and click tools such as Change Sets, as well as developer tools like Eclipse and Ant.
Techniques and Tools to Improve the Salesforce Development CycleSalesforce Developers
The document discusses techniques and tools to improve the Salesforce development cycle. It covers establishing reusable development organizations, managing source code with version control, implementing automated testing, developing features in isolation, and integrating continuous integration practices. Reusable orgs allow multiple developers to work independently. Version control with branching enables collaborative development. Automated testing validates code changes. Isolated feature development prevents conflicts. Continuous integration merges and deploys changes across environments.
5 Essentials for Simplifiied Release Management and Continuous DeliverySalesforce Developers
Having a smooth product release cycle is critical in today's World of software development. Join this session to learn about the essentials of Continuous Delivery which will include Version Control Integration, Deployment Automation,Test Automation and Data Migration.
Testing CRM from a 360 View - extremeCRM Rome 2013Wael Hamze
Learn how to test different aspects of your dynamics CRM deployment. Starting from unit tests for plug-ins, custom workflow activities, JavaScript and then moving to integration testing and UI level testing.
With the new Lightning Editions of Salesforce, everyone now has plenty of sandboxes available to put together a robust change/release management process. Join us as we talk about how to maximize the use of your sandboxes, including refresh cycles, Sandbox templates, Change Set & Package flow between environments, Single Sign-on through Environment Hub, and more.
See the video of this presentation here: https://www.salesforce.com/video/306450/
and more details here:
https://success.salesforce.com/Sessions?eventId=a1Q3000000qQOd9#/session/a2q3A000000LBfmQAG
Webinar: From Sandbox to Production: Demystifying Force.com Release Managemen...Salesforce Developers
Ever wonder how to plan to customize your production org? Do you know when to use a developer sandbox? Stumped on how to reliably move changes around? We'll show you how in this webinar. Learn the best practices from the pros.
Salesforce gives you the ability to create copies of your production org in a separate sandbox environment for a variety of purposes like testing and training without compromising the data and applications in your Salesforce production organization. Learn some of the key considerations that lead to effective Release Management.
Key Takeaways
:: Understand how to move code and configuration utilizing change sets.
:: Best practices for org management/governance.
Intended Audience
:: This webinar is geared towards all Force.com developers.
:: Not scoped to ISV developers.
:: Tailored toward customers with one sandbox, small dev team, and limited number of customization projects.
Leverage Team Foundation to focus on application development, decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle.
Continuous Delivery with TFS msbuild msdeployPeter Gfader
This document discusses automating software deployments using tools like msbuild and msdeploy to enable continuous deployment and delivery. It outlines the pain points of manual deployments and goals of automating deployments. It provides guidance on setting up continuous integration, automated testing, packaging, and configuration for both new systems and existing environments. It also lists best practices like deploying early, having rollback plans, logging builds, and automating as much as possible.
This document discusses DevOps practices at Salesforce, including:
- Using continuous delivery pipelines to plan, build, test, release, deploy and monitor code changes.
- Organizing teams using a Scrum model with sprints every two weeks and an average size of 7 engineers per team.
- Maintaining sandbox environments like development, test, UAT and production for each project.
- Following a branching strategy in version control and using continuous integration to test and deploy code changes.
Salesforce Developer Workshop for GDF Suez HackathonPeter Chittum
This document provides an agenda and overview for a GDF Suez Hackathon Workshop on the Salesforce platform. The agenda covers platform basics, Apex, Visualforce, reports, integration, and Salesforce1. It discusses concepts like multi-tenancy, declarative vs. programmatic development, the data model, APIs, and recommends exercises and resources for learning more.
The document provides an introduction to Apex, the programming language of the Salesforce1 Platform. Apex code can be used to extend functionality when configuration is not enough, including building Visualforce controllers, database triggers, custom web services, and scheduled/batched tasks. An example use case is given of using a trigger to keep a Contact's address in sync with its related Account. The document outlines some key features of Apex, such as its Java-like syntax, object orientation, strong typing, and built-in testing framework. It encourages attendees to try Apex development themselves and provides resources for learning more.
This document provides an overview of Visualforce pages in Salesforce, which allow users to build custom user interfaces for Salesforce data. Visualforce follows the model-view-controller pattern, with standard and custom objects as the model, Apex code as the controller logic, and Visualforce tags as the interface view. Visualforce tags have a prefix indicating the component library and attributes like value and name to pass data to the component. The document demonstrates the anatomy of a Visualforce tag and discusses using over 140 standard tags or creating custom reusable components. It encourages users to try Visualforce and provides developer resources for help and learning.
New to Force.com and needing a quick orientation to bring you up to speed? Join us for this series of brief introductory sessions on Force.com, the world’s leading cloud platform that lets you build apps rapidly using configuration-driven development and powerful programmatic logic.
Each Friday one of our experts will walk you through one of the core elements of the Force.com platform and cover the basics you need to build your first app in the cloud. Each session is 30 minutes long.
This document summarizes a Salesforce developer session on leveraging StandardSetController in Apex and Visualforce to build a custom "Add to Campaigns" application. It discusses using StandardSetController with list view filters to retrieve campaign records, and an Apex controller extension to integrate this with a Visualforce page. It allows users to select multiple campaigns to add a contact or lead to using checkboxes, while leveraging existing platform functionality and custom settings for customization. Code samples demonstrate the controller, wrappers, and custom setting used.
This document introduces Visualforce, Salesforce's framework for building custom user interfaces that are hosted natively on Force.com. Visualforce uses the model-view-controller (MVC) pattern and allows developers to leverage standard and custom components, controllers written in Apex, and integration with other web technologies. Visualforce pages can be used to build custom applications, extend and customize Salesforce functionality, and develop for different devices.
Out of the box, the Force.com Platform can automatically generate user interfaces, but in some cases you might want to build a more custom UI. Join us to learn about Visualforce, the component-based UI framework that lets you build attractive, dynamic, reusable user interfaces.
This webinar is tailored for beginner developers as well as Salesforce administrators.
Watch this webinar to learn about:
:: Common use cases
:: Leveraging Apex code on the server side
:: Debugging techniques
:: Best practices for efficient and responsive pages
Force.com can automatically generate user interfaces, but in some cases you might want to build a more custom UI. Join us to learn about Visualforce, the component-based UI framework that lets you build attractive, dynamic, reusable user interfaces. We'll cover code walk-throughs, common use cases, leveraging Apex on the server side, debugging techniques, and how to utilize the component framework to make your code portable and maintainable.
Continuous Integration and Orchestration: Putting the AppDev in DevOpsCA Technologies
This session will illustrate the new challenges faced by agile development of mobile- and Web-based apps that require access to an enterprise’s system of record, in most cases, a mainframe—and how application development tools can be integrated into the application delivery process to provide collaboration and orchestration between development and operations.
For more information on DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
Randy DeFauw and Charlie McLouth of Perforce Software discuss how the company uses Salesforce and DevOps principles to manage their Salesforce configuration. They demonstrate how they version all Salesforce metadata and plugins to enable restoring the entire Salesforce deployment to previous configurations. Perforce treats Salesforce as critical infrastructure and applies the same DevOps practices they use for other systems. The presentation encourages organizations to have a configuration management plan for Salesforce and not pretend it does not need DevOps practices just because it is software as a service (SaaS).
If you are familiar with object-oriented languages like Java or C#, Apex may be the language you already almost know. Apex is the cloud-based programming language used on the Salesforce1 Platform to take your enterprise applications to the next level. In this webinar, get an introduction to how Apex is similar to other languages, how you can start coding in Apex with just a web browser, and an overview of the many functions Apex can perform for your applications and users.
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.
Automating Deployment Between Orgs Using Git & Continuous IntegrationSebastian Wagner
Updated with the deck from DF14
As a fully certified TA, I offer expert consulting services around continuous integration, practice development and governance to help customers leveraging the advantages of SFDC.
https://uk.linkedin.com/in/se6wagner/
Abstract:
Automating the deployment between environments (dev, test, prod, etc.) gives consistency, visibility, and validation to the process.This greatly speeds up deployment and provides early detection of defects. Join us as we cover the theory and best practices of this approach. You'll discover how to design your own automated processes using Continuous Integration (CI) tools and Git version control.
Presentation from full-stack agile on how you can scale your agile teams as your company grows. As your company grows your teams need to be able to adapt to change quickly.
The Open-source Eclipse Plugin for Force.com Development, Summer ‘14Salesforce Developers
The document discusses the new open-source Eclipse plugin for Salesforce development. It describes the history of the original plugin and reasons for updating it, including using the Tooling API and open sourcing the code. Developers can now contribute changes by forking the project repository on GitHub and submitting pull requests. The document reviews the different available versions and outlines the process for testing changes locally and getting updates incorporated into the main branch.
A Developer's Guide To Building Great Salesforce ConsolesEnzhen Huang
Slides for the Dreamforce '14 developer session:
A Developer's Guide To Building Great Salesforce Consoles
Sample code: https://github.com/enhuang/DF14Demo
Twitter: @ehuang
Interested in bringing the benefits of Salesforce DX into your organization but aren't quite sure where to get started?
Salesforce DX defines an entirely new way to manage and develop Salesforce apps, and lets teams build together and deliver continuously.
Come to this webinar and get an insider's view into how you can streamline your development lifecycle by adopting Salesforce DX.
In this webinar, we'll share how you can leverage the tools and best practices available to promote healthy Application Lifecycle Management.
Learn about the latest advancements we've made in our Sandbox environments, metadata API, deployments, namespaces and source control management, how the brand new Apex Debugger extends the Force.com IDE, and how these updates can be leveraged to enhance your development efforts and transformation.
Join Kevin as he shares techniques for deploying changes to Salesforce, from quick fixes to well-developed ALM strategies featuring continuous integration with automated deployments. Even in the world of No Software, engineers still need to collaborate in order to get the most out of the platform. Reflecting on his experiences over a year of speaking with developers and admins, Kevin will explain how you can work together effectively and make changes to your Salesforce organizations safely.
Description:
The Java language, tools and frameworks have been the foundation of countless enterprise systems. Here at Salesforce we fully support Java and are part of the Java community. We believe developers should be able to build quality apps using Java. Unfortunately, many of us are stuck with inefficient and painful ways of using this toolchain. It is time for enterprises to move past the sucky ways they are using the Java platform.
Based on James Ward's blog post, "Java Doesn't Suck", in this webinar James shares his views along with noted Java developer and author, Bruce Eckel, and will also walk through the suckiest parts of Java, providing recommendations for moving forward, while having spirited discussion along the way.
Join us for this awesome Salesforce developer webinar, to learn how to build better apps using Java!
Key Takeaways:
::Discover new Java tools that increase productivity.
::Learn modern practices for deploying Java applications.
Intended Audience:
This session is for Java developers that build web apps and HTTP APIs.
Recommended Resources:
https://developer.salesforce.com/events/webinars/the-java-best-practices-tools-performance-and-deployment
Triggers are procedural code that automatically execute in response to database events like record inserts, updates, or deletes. When a record is saved, various processes are run including validation rules, workflow rules, and triggers. Triggers allow developers to perform complex calculations and automatically create related records in a way that standard tools like workflow cannot. Best practice is to use triggers only when necessary since they are harder to maintain than declarative tools. Developers should thoroughly test trigger code and have at least 75% code coverage before deploying to production.
Be a Flow expert in no time! Join us to reduce the frustration of the first-time or novice flow builder by hearing hard-won knowledge and tips. No matter your skill level, we will equip you with what you wish you knew before sitting down to write your first Flow. You'll leave with knowledge you can use immediately to write better flows with less pain.
Build Together And Deliver Continuously With Salesforce DXLynette Lim
This document describes a pilot program for continuous integration with Salesforce DX. It discusses pain points with the current development process and how Salesforce DX aims to improve the developer experience. Key benefits of Salesforce DX include faster development cycles through features like scratch orgs and metadata deployment automation. The document provides an overview of Salesforce DX principles and development flow, and demonstrates how to set up continuous integration with Jenkins.
Dreamforce 2014 Mobile Theatre Session - Automated Testing for Salesforce1 Mo...Gaurav Kheterpal
My session at the Mobile Theatre in Dev Zone at Dreamforce 2014 on how to use the open source Appium framework for Salesforce1 mobile app automation testing
Elevate Madrid Essentials - Advance TrackCarolEnLaNube
This document discusses Salesforce1 Platform and the Advance - Apex Track session. It contains a safe harbor statement noting that any forward-looking statements made are subject to risks and uncertainties. It also notes that unreleased services mentioned may not be delivered or may be delivered later than expected. The document directs readers to SEC filings for additional information on risk factors.
Easy No-Code Integrations with External Services and Visual FlowSalesforce Developers
The document discusses forward-looking statements and associated risks and uncertainties. It states that any projections or statements regarding future operations, strategies, products, features or customer contracts are forward-looking. It notes risks including those associated with new functionality, products, business models, operating losses, fluctuations, outages, security, litigation, mergers and acquisitions, market immaturity, limited operating history, employee retention and growth, and larger enterprise customers. Customers should make purchase decisions based on currently available features.
Building Command-line Tools with the Tooling APIJeff Douglas
The Tooling API allows developers to build custom development tools for Salesforce. It provides similar functionality to the Metadata API but with a different execution workflow. The Tooling API can be used to automatically deploy code and metadata, keep orgs in sync, perform code analytics, manage validation rules and other metadata types, execute tests, and access debug logs and heap dumps. Developers can access the Tooling API via SOAP or REST interfaces depending on their preferred language and needs. The nforce-tooling module provides a simple Node.js wrapper for interacting with the Tooling API via REST.
Manage Development in Your Org with Salesforce Governance FrameworkSalesforce Developers
As your team creates more apps in your Salesforce Org, you're faced with a new set of challenges: managing a well-designed org. Join us to learn about using the practices defined in the Salesforce Governance framework, and the set of tools available for managing issues such as security, coding standards, decisions over declarative verses Apex apps, design standards, overall Org strategy, and change control. By applying these best practices, your team can continue to grow your apps to meet the continuing challenges of your company.
For years, Salesforce development teams have been using the App Cloud to manage sprints, code releases, and more. For the first time earlier this year, Salesforce released these tools to AppExchange in a package called Agile Accelerator so you too can manage your development efforts. Join us to get a hands-on demo of Salesforce's Agile Accelerator. Meet the team and get all of your questions answered.
Description:
In this session, we will discuss and demonstrate how to build engaging employee and customer-facing applications in JavaScript on top of the Salesforce1 Platform.
We will explore all the aspects involved in building these next generation applications including authentication, the REST APIs, mobile development options, and different integration scenarios. We will also share some inspiring examples built on the Salesforce1 Platform with leading JavaScript frameworks such as AngularJS, Ionic, BackboneJS, Ratchet and more.
Key Takeaways:
::Get an overview of the Salesforce1 Platform from a developer point of view
::Understand Salesforce OAuth Authentication
::Acquire knowledge on the Salesforce REST APIs
::Get insight on building a Single Page Application on the Salesforce1 Platform
::Explore using modern JavaScript Frameworks such as AngularJS, Ionic, Backbone, etc.
::Gain knowledge on building state-of-the art mobile apps on the Salesforce1 Platform
::Get familiar with building custom apps with Heroku and Heroku Connect
Intended Audience:
This session is for both seasoned JavaScript developers who want to learn how to build applications on top of the Salesforce1 Platform, and seasoned Salesforce developers who want to learn how to create amazing user experiences in JavaScript.
Recommended Resources:
https://developer.salesforce.com/en/events/webinars/JavaScript_Applications_Salesforce?d=70130000000lgzk
The Apple Watch is the long anticipated wearable device from Apple. It includes a striking design and innovative new interface. Developers can build apps, or specifically extensions to apps running on their iPhone, using WatchKit, Apple’s developer SDK. Now, with the latest Salesforce Wear Developer Pack developers can build apps for Apple Watch and Salesforce.com. Join this webinar to learn how to build your first Apple Watch app using Salesforce Wear Kit.
What you will learn:
:: How to use the Salesforce Wear Developer Pack to extend your iPhone apps to the Apple Watch
:: Common implementation patterns for Apple Watch development, including: notifications, glances, messaging with the Salesforce Mobile SDK of iOS delegates, and more
:: Storyboards and project targets for xCode and Apple Watch
:: Writing Swift code to work with Salesforce data
Key Takeaways
:: How to create an Apple Watch app in conjunction with the Salesforce Mobile SDK for iOS
:: Sending and receiving data from Salesforce on the Apple Watch
Intended Audience
Existing Apple iOS developers, or Salesforce Platform developers interested in getting started with iOS Development
CodeLive with Cynthia Thomas - Refactoring data dependent code.JackGuo20
Cloning data can be harder than it looks; especially if there are multiple records. In this CodeLive session, Cynthia Thomas and Kevin Poorman work to refactor and test code to elegantly clone large numbers of records. Register now to learn about handling collections of data, refactoring, and testing practices.
Intro to Apex - Salesforce Force Friday Webinar Abhinav Gupta
The document provides an introduction to Apex, the programming language of the Salesforce platform. It discusses how Apex can be used to build both the user interface and business logic layers of applications. It also summarizes key Apex concepts like triggers, interfaces, annotations, testing and deployment. Resources for learning more about Apex like Trailhead, developer guides and discussion boards are recommended.
3. Safe HarborSafe harbor statement under the Private Securities Litigation Reform Act of 1995:This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services.The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of intellectual property and other litigation, risks associated with possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-Q for the most recent fiscal quarter ended April 30, 2011. This documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site.Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
4. AgendaWhat is Continuous Integration and why do I need it?How do I set it up?How do I extend it to meet my needs in the future?
5. QuestionAre you using a form of source control such as Subversion, CVS, Perforce etc?
7. Running tests is boringSo Running tests manually is boring and you forget.Tests break and you don’t know which change broke what.The longer it takes your to discover a test failure the longer it will take to find the root cause and fix it.So if your too bored to run the tests who will?An Intern? The pointy haired boss? Or…
12. Have a robot integrate your team’s changes and run your tests to make sure they are compatible.
13. If they are compatible release the changes to a test org
14. If they are not compatible and tests fail alert the person who broke the tests and optionally the team. O.K I’m interested. Most popular Continuous Integration server in use today is called “Jenkins”.
15. Open Source with a rich set of plugin’s available to extend it’s functionality.
16. They went with the “butler” metaphor instead of “robots” in their Logo but otherwise I recommend itMoving Parts Source Control Repository (Subversion, CVS, perforce etc)force.com migration toolEmail Notification
17. Lets go ShoppingWe need to download the following:Java JDK http://www.oracle.com/technetwork/javaApache Ant http://ant.apache.orgForce.com Migration tool (via the Setup menu)Jenkins http://jenkins-ci.org/
18. What’s with all this software?You came to the cloud to get away from installing software. The good news is your actual tests will execute in the cloud using salesforce.com servers for the heavy lifting.No need for a beefy build serverProof: Win XP VM with 1 GB RAM
21. Java Script & VFWho use’s Java script in their visual force pages: frameworks, home grown, or combinations?Who’s ever had an error in their Java script?How was it found: QA, you, or a customer?
22. Java Script Testing with YUI TestHandles: dependencies upon page eventsExecution types: synchronous & asynchronous Simulation of actions: mouse & keyboard
24. Enter The YUI Tests & Visual ForceHarness the power of YUI Test on a VF page
25. Selenium to the RescueSelenium IDE – Firefox add on that allows you to easily create, run, & export test cases with test methodsSelenium RC Server – Server that allows you to run your Selenium tests especially once they’ve been converted to Java or another language
#4: Any purchase decisions customer make should be made based on currently available technology. Please visit our website sto review our Safe Harbor statement in detail.