Support & Downloads

Quisque actraqum nunc no dolor sit ametaugue dolor. Lorem ipsum dolor sit amet, consyect etur adipiscing elit.

s f

Contact Info
198 West 21th Street, Suite 721
New York, NY 10010
+88 (0) 101 0000 000
Follow Us

Salesforce Test Automation Tag


1. The World’s first Merge Editor with conflict resolution.

2. 100+ integrations across VCS, ALMs, Test Management, Test Automation, Defect Tracking systems etc.

3. Now deploy the unsupported Metadata Types with our AutoRABIT’s framework

4. Synchronize the production data with incremental data migration

5. Circular References & Self Look-ups are handled on the fly during the complex Data Migration processes.

6. Review, Modify and Deploy Profiles across multiple sandboxes, with the exclusive Profile Manager on the planet

7. Ready to use frameworks for pre and post-deployment steps

8. Integrated check-in console – Tag changes to User Story, Pre-commit validations & Check-in.

9. Supports the highest number (15) of Version Control integrations for Salesforce CI Server: GITHub, BitBucket, GITlab, AWS-Code Commit, TFS Cloud, VS Online, TFS_GIT, Collabnet SVN, WANDisco SVN, VisualSVN, On-Prem SVN/ TFS/GIT/Perforce

10. Supports 4 types of Authentication for Version Control system: Password, SSH, OAuth, Two-Factor

11. Provides option for multi-versioned Roll Back of deployments

AutoRABIT is the only CI server that:

12. gives you turnkey adoption with Zero additional tooling and training

13. gives you lightning-ready Record & Playback Test automation on multiple browsers & Mobile Devices.

14. allows Check-in, Merge & Deploy from your chosen Version Control System

15. has dedicated VPN tunnel & support for Gov. Cloud.

16. has integrated Data Loader

DreamForce 2016 has 900+ Salesforce Customers, Architects, MVPs spending their valuable time on Salesforce release management at AutoRABIT Booth in Devzone and it was some experience !!!.
We could divide the Salesforce fraternity that visited us at the booth into three segments :

  1. Clients who were not sure where to start the whole thing and the amount of knowledge and expertise required to make the journey successful
  2. Clients who have used some tools but did not reach the level of automation or scalability to the extent they anticipated
  3. Few Architects and experts, who were able to assess the current state of Salesforce Continuous Integration and were able to visualize a wishlist for future.

With a much bigger and awe-inspiring DreamForce’16 making its way in few weeks, it was very important to assess AutoRABIT in three segments and to ensure we have a release that announces itself in such a way that answers most of the challenges from the Salesforce World with respect to CI and release management.

The result is the much awaited AutoRABIT 4.0. Considering it is a pre-cursor to DreamForce and we know the hype and expectations around it , this has been one of the biggest release ever from AutoRABIT.
The first of the AutoRABIT 4.0 blog series is to outline the thought process and the problem areas that went into the brainstorming of the release.

The unexplored territories in Salesforce Continuous Integration

  1. 360 Degrees view for Salesforce Continuous Integration – Salesforce CI is not just about deploying some changes from a GIT branch into Salesforce Sandbox using tools like Jenkins. It needs lot more support from tooling to achieve 360 degrees Salesforce CI for Check-in, Merge , Deploy seamlessly.

The following are some of the items that need to be looked at on how the current tooling is letting down the                vision of a Salesforce CI practitioner in achieving higher maturity in the company with release automation.

  1. Developers should be able to check-in their changes into a Dev Branch effortlessly without crypticness associated with a version control system.
    • Check-in mean that Developers take the entire metadata file  [ a profile or a custom object] from their Dev Sandbox using Mavensmate or Eclipse, overwrite the file into a GIT clone and push it into a common GIT Dev Branch.
    • Most developers miss out on the fact that they must check-in Layouts, Profiles etc., when they a create a custom field and just what they worked on and there is no way to detect any of these missing dependencies apart from a bug identified by QA members
    • Does any of the CI tools understand the salesforce parent-child metadata concept or the problems with Profiles or Custom Labels being the largest shared files which keeps getting modified for other changes.
    • Pushing the check-in information into ALM so that user story and metadata are associated for easy reviews and sign-offs is another challenge and release managers even today maintain large excel sheets “asking” for what the developers worked on to be maintained in a separate sheet.
  2. Release team should be able to easily cherry-pick / merge what goes into the release as all user stories may not make the cut.
    • Merge is not just about integrating two branches. There needs to a branching strategy behind it.The decision of feature branches Vs common Dev branch for the entire team needs to be discussed at depth.
    • GIT tooling support is that not great when it comes to merging a set of changes  [ group cherry-picking ] easily from a branch into another branch. It becomes a hard task for the release team to be able to cherry-pick a group of commits for completed user stories and merge them into a higher release branch.
      • GitHub, BitBucket doesn’t support cherry picking in cloud – need to install a client tool like GitHub for Windows or SourceTree or TortoiseGIT.
      • SourceTree doesn’t support grouped cherry-picking – TortoiseGIT supports it.
      • Conflict resolution – the less we talk about it, the better if I am Salesforce adminstrator.
        • The editors like SourceTree doesn’t support merge changes from both source and destination. Its either local or remote incase of a conflict block.
      • Tagging a group of commits to a release and deploying them is looked as too far dream with the tooling around.
  3. Deployment – Deployment of changes from version control to Salesforce Sandbox is not just about using an ANT script and calling a Jenkins Job. It is about lot more things in Salesforce Deployment.
    • Deploying an entire branch from GIT will inevitably result in “Too Many Files” issue due to Metadata Governor limits .
    • How this often ends up is that Salesforce teams stop committing the profiles, custom objects etc., to GIT and end up with code items which is not the right spirit of version control.
    • There should be a support for deployment from a particular baseline revision or able to deploy a hotfix commit directly from version control.
  4. Support for not just GIT – Several large enterprises use SVN, TFS , Perforce and the Salesforce CI is not just about GIT.

With AutoRABIT 4.0 , we are proud to announce 360 degrees support Salesforce Continuous Integration with its check-in editor, Merge Editor and rich deployment support.

2. Profiles, Profiles and Profiles

There has been a lot of talk and experimentation being done around managing the profiles. Administrators have tough time deploying the profiles, Governance teams have tough validating profiles and Architecture team to set rules for what should be excluded in Profile Migration and ensure they are met by the development teams.

The fact remains that Managing Profiles has been a primary challenge for Salesforce teams across the globe.

With AutoRABIT 4.0 , we are pleased to announce a Profile Designer to check-in, Compare and Deploy the profiles across multiple sandboxes that gives you full control over the Profile Management.

3. Manual Steps in Salesforce Metadata Migration

Inspite of ANT which is at best a handy tool for for migration or changesets, it is still a case of heavy manual operations post migration.
It could be items related to updating email addresses , creating groups, updating scheduled jobs or it could be items arising out of using unsupported metadata  in migration.
AutoRABIT 4.0 is the first ever tool to introduce a framework for automating pre/post migration steps in Salesforce migrations.

4. Salesforce Release Management is not just about Metadata

While Salesforce CI is often circled around metadata migration , which is only addresses a part of the challenge faced by Salesforce administrators. Setting up environments with the data of the important objects with least effort is often left as manual exercise or needs to have another set of tools doing the job.

While it is known that AutoRABIT has a rich integrated Data loader , it has just become even better with 4.0

5. Test Automation

AutoRABIT 4.0 has enhanced its Test Automation Factory model to revolutionize test automation with enhanced support lightning and Salesforce appexchange components.

6. CI Adoption and ROI justification

While Management teams invest in huge time and money for innovation and automation, a big challenge for them is to able to monitor, measure and visualize the adoption rate of automation and the ROI benefits associate with it.

AutoRABIT 4.0 has a reporting module that gives a holistic view of metadata deployments, data migration, CI results, test results etc., giving complete picture of CI adoption and ROI reports.

If you think these are the challenges that you are looking to address in your company in pursuit of Salesforce release automation, scheduled a discussion with us at , with your problem statement and we are happy to assist.

I will follow-up this blog with a detailed feature walk-through of AutoRABIT 4.0 .

Recently, I participated in an online panel discussion on the subject of CI Acceleration, as part of Continuous Discussions (#c9d9), a series of community panels about Agile, Continuous Delivery and DevOps.

You can watch a recording of the panel discussion here

#C9D9, is a community initiative by Electric Cloud, which powers many Fortune clients’ Continuous Delivery to businesses, by automating their build, test and deployment processes, essentially the same space we are in, the difference being that AutoRABIT focuses on the technologies. There were some interesting insights from the panel discussion that I wanted to share, especially from a ecosystem perspective that I am involved with.

 Defining Continuous Integration?

When you talk of Continuous Integration, a lot of discussions start off with Martin Fowler’s popular post. Several panelists talked about optimizing their infrastructure and how they are burning large budgets for running builds and automated tests. If you consider examples of CI at any social networking companies (Facebook, Twitter, etc.), they are aiming for Continuous Deployment or Continuous Delivery and not just merely Continuous Integration (CI), since a few mistakes are fine. It justifies the time-to-market acceleration and instant feedback from their users is critical. The testament to this is many issues/bugs that surface for new features in sites such as Facebook, Tumbler, SnapChat, etc.

I wanted to give the perspective of a cloud-based technologist, specifically In the ecosystem that we work, clients are satisfied with automation of basic development tasks and rudimentary tooling, which is a Herculean process for a relatively new technology. For most of my clients, CI is a journey they are starting and version control enablement is the first step. In a typical team, they have around 15-20 members, though there are larger teams, but I would focus on the average customer (a typical implementation).

Builds: Tips and Tricks

Most of our client code base is not huge, and the major challenge is release management, accelerating the release cycles and reacting faster to the business needs. This is critical for a business-centric and a revenue-generating software like

In this ecosystem, a developer would typically spend about 30% of his time managing his/her code. There is a lot of impedance, since the environment is in a multi-tenant cloud and the related restrictions, called governor limits, prohibits one organization (tenant) or one team from monopolizing the shared infrastructure. The typical limits/restrictions are SOQL queries, heap size, data transfer, and session time-out – essentially anything that burdens the infrastructure.

There are workarounds, but most of them are expensive and need extensive tooling and superior DevOps skills, which are rare to find. Typically, most of the implementations aim for starting a mainline code, a version control, deployment automation, a branching strategy and then later (mostly Phase-II) build automation, test automation (Regression), code coverage and deployment automation.


Everyone understands the importance of testing and the need to get budgets. But, the effort to showcase the benefits and ROI stops them from securing the budgets. Managers should understand and make the case for testing resources and budgets. The key is data; once managers start collecting data and take the report at the ‘appropriate’ time, it’s a no-brainer most of the time. (You can add/extrapolate standard ROI templates available online)

For implementations that are more evolved, we suggest categorizing the test cases as ‘gold’, ‘silver’ and ‘bronze’ and using voting for each test case. So, when a test case comes in, the admin knows which ones to use as default, the frequency, the environments, and the test cases that need to be used. In addition, breaking down test cases and having a test plan helps optimize resources. Ultimately, it’s about ‘weight’ in terms of your infrastructure and speed.

From a build management process, one of the key elements is to have a build management strategy. At any given point of time, it’s a process of an evolving document, and so it is with testing, too. The leader or the manager should have a test planning strategy in terms of his budgets, infrastructure usage, and the kind of new processes and new tools that are acquired. He/she needs to understand that every new process takes two or three extra months.

Last, but not the least, test analytics have come a long way and it’s one of the areas that analytics are most underutilized in. Let the algorithms predict which test cases to use, which ones to build, on which module, etc., and be able to run the appropriate test cases. Analytics are becoming mature and dependable. Spend some time and create a project around this; it has great potential, but not every company is leveraging it.

About AutoRABIT

 AutoRABIT is an end-to-end Release Management and Continuous Delivery suite, specifically designed for Salesforce applications. AutoRABIT helps Salesforce developers, Admins and Analysts with out-of-box features and automation processes. This helps organizations in achieving Salesforce Continuous Delivery. It enables, Automated Metadata Deployment and Version Control support. This includes Advanced Dataloading and Sandbox Management, end-to-end Release-Management, Defect tracking, and Test Automation for public and private clouds, but is not limited to all these.

With our unique approaches for deployment and automation, AutoRABIT can help release managers migrate both metadata and data seamlessly across environments with the click of a button.

With AutoRABIT, you will achieve higher release velocity (days instead of weeks/months) and rapidly improved time-to-market schedules.


With increased consumerization and explosion of devices, there is a need for a testing framework like AutoRABIT TAF, which helps enterprises scale up on offering superior quality products and responsive customer service. The key takeaway from TAF is lower Total Cost of Ownership (TCO) with agreed output at each milestone or partnerships, which can go granular to each test case and further to each test page/screen.


At AutoRABIT, we have seen time and again that testing and going to the gym are very similar (Salesforce Test Automation Can be Achieved NOW). It always gets postponed to the next day and rarely gets featured as something to be done for today. Testing function lags behind in enterprises today, as quality is not comprehended as a top business priority, with lack of insights on how to gain the critical competitive advantage. Though everyone understands that software testing helps enterprises enhance their product quality, the common misconception is that it demands huge investments in people and technology.

When most of the discussions start, the management teams evaluate their present/legacy testing business models and first try to maximize their current investments. This plug in the hole can be a more convenient and an easy way out, but the question is whether you are trying to save a sinking boat or trying to accelerate the boat with unconventional and progressive ideas.


There are several flexible and economical testing approaches that can stop the escalation of costs, deliver quality products and keep your profits (and your boat) not just afloat, but ensure that it gets more power to tide over the quality storms.

Testing-as-a-Service (TaaS) has gained momentum in the recent years, as it helps enterprises focus on core business areas, reap the benefits of pay-per-use, reduce infrastructure costs, and optimize the resources workflow.

Testing teams can look at several ways in which they can achieve accelerated efficiencies, i.e., non-linear returns on investments with good planning. Planning and creating a roadmap for the team can go a long way in accomplishing your strategic goals.

Related Post : Salesforce Test Automation Can be Achieved now


Organizations can opt for TaaS when there are tasks to be automated. Through outsourcing, enterprises can save not only on resource hires, but also on the costs of testing infrastructure.

Several services are offered through TaaS that include functional and non-functional testing, mobility testing, and testing of various CRM, ERP and cloud applications.


1. Saves Capex/Opex:

TaaS makes provisions for people and technology, as a part of its offering, enabling enterprises save costs/investments on infrastructure and software licensing.

2. Flexible Pricing:

Pay-per-use models help enterprises plan their test budgets based on the project requirements/demands.


  • Time & Material: Costs are calculated based on the time spent by the resources on a project.
  • Fixed Bid or Fixed Price: The project is engaged at a fixed price against agreed deliverables.
  • Test Cases: Projects are also engaged based on the complexity of test cases in number.

Things to take care of:

  • Have your goals listed: Have a clear-cut idea of your goals – whether you want to have software testing for enhancing your product quality, maximizing your current investments, or gaining a critical competitive business advantage.
  •  Evaluate your current process: The first step towards change is evaluating your current process with regard to cost, efficiency and optimization, and identifying what needs to be changed.
  • Prepare for change management: Once you have made the decision in line with your goals, go ahead and boldly embrace the change. After all, change is growth, growth is change.
  • Crawl first, then walk and run: Testing, like change, is a gradual process. Once you have decided to go for software testing, make the move gradually from non-functional to functional testing, and later to mobility testing and cloud

applications testing.

  • First get the most appropriate process and then the right tools: It is important to first understand the relevant testing process and then get hold of the right tools to execute the same.


The best of Salesforce development teams would inevitably vouch for the fact that test automation is indispensable to ensuring stability to enterprise applications in an organization. However, there is a significant gap between appreciation and adoption.

While most teams understand and appreciate test automation as the way ahead, the practice of adoption of test automation into the release management process is far from reality.

In a short survey conducted by AutoRABIT with some of its current clients, the following three distinct reasons emerged for non-adoption of test automation:

1. Test automation requires specialized test resources, which is inhibited due to budgetary constraints.

2. The test scripts, like codes, have to be frequently upgraded and maintained, without the ability to save any extra cents.

3. The data is pushed into the test script, and if you want to run the test case on a different release environment or on your staging data, you have to keep varying some property files, scripts, etc.

If you agree with the above top-three constraints in adopting test automation, then the AutoRABIT Test Automation Factory (TAF) for Salesforce is probably the solution that you should be looking out for.

AutoRABIT TAF for Salesforce has the following components that can leverage the test automation to the next level in an enterprise:

  • Curing engine for seamless test script recording and playback. Business users themselves can automate tests by themselves now.
  •  Data Extraction – Alienate data from your test script
  • Test Generation


Testing has evolved from being a full-time equivalent (FTE) driven method of working, to ‘as-a-service’ method of thinking. TaaS, which was traditionally considered as an activity, has evolved today as a framework and a unique way of approaching testing & quality assessment, independent of vendors and tools. The maturity and perceptibility of the

team and the goals articulated by the management will determine the success of these models. TaaS can benefit organizations in ensuring predictable outcomes across the lifespan of the development cycle.

We are pleased to announce AutoRABIT 3.9 GA, the first GA release after Dreamforce’15, wrapping up most of the awesome feedback received during the event. Here is an update on the new features that will be made available for our customers over the weekend release scheduled for 17th Jan, 2016:

1. Salesforce Metadata Deployments:

a.Back-up and Rollback – You can now take a back-up of the destination metadata before deploying. The deployment can also be rolled-back in case of any functional issues.
b.Smart Profile Deployments – You can now deploy profiles with an option to Skip Visibility settings for the metadata members that are missing in the destination.
c.Metadata API Support for the Winter’16 release components .

2. Salesforce Data Migration Enhancements:

a.AutoRABIT Advanced Data Loader Pro has become more powerful with its comprehensive circular reference resolution algorithm. The Sandbox environment set up can be a breeze now with the records of an object along with the parent-child relationships transferred all at a time.
b.Filters on Record Types are provided to give more flexibility in restricting what records can be transferred to the destination.
c.Incremental Migration to ensure that you can synchronize your environments by migrating the delta of records on a schedule.
d.Chatter Data Migration support.

3.Version Control

a.Thin Client for TFS – Salesforce Teams can now check-in to Team Foundation Server, Register Repositories , Create Branches in addition to deployments right from AutoRABIT .
b.Thin Client for Perforce – Salesforce Teams can now check-in to Perforce, Register Repositories , Create Branches in addition to deployments right from AutoRABIT .

4.ALM Integration – “ No Deployment” Theme supported for Jira

a.Automated deployments can now be scheduled into multiple environments based on the Jira User Story Status with AutoRABIT
b.Attach the metadata changes to Jira tickets for User Story-based deployments .

5.Test Automation Factory

a.Special Automation Templates to automate manual steps with Orchestra CMS deployments, Apptus and Skuid

6.Administration Enhancements
a.Org Level ACL’s – Org Administrators can now set access control levels for various operations in AutoRABIT at the Salesforce Org level for team members .
b.User Profiles – Users logged into AutoRABIT can now map their Salesforce Org user and their SCM user details making it easier for Administrators in Salesforce Org Mapping step.

Please write to for more information and detailed discussion on the Release features.

Agenda: 5 Essentials for Salesforce Release Management and Continuous Integration

Description: The meet up would essentially detail the finest solutions towards the challenges faced by the salesforcedotcom teams around release management and showcasing the best practices for Release Automation & Continuous Integration to achieve higher Release Velocity and faster Time to Market . (TTM)

The demonstration will be performed using AutoRABIT, wherever necessary.

Essentials for Salesforce Release Management & Continuous Integration:

Version Control Management
• Branching strategy for releases

• Repository models

• Merges & Conflicts

Deployment Automation(CI)

• Continuous Integration

• Change sets, Validate Deploy

• Selective Deployment

• Profile & Permission set deployments

Sandbox Management

• Org Synchronization and Management

• Org Differences and Audits Back ups

Test Automation

All Automated, No Manual step

Complex Data migration and set up

• Regular clean-up of data

• How to handle multi object and relationship matrix of the data

• Data Synchronization across Orgs

And much more that we would talking and presenting, in case you want to set up one to one sessions to understand how other teams achieved release automation, please reach out to our team at the meet up venue and we will connect for further developments.

AutoRABIT has its 3.6 release on Thanksgiving weekend with an aim to bring more joy and happiness to Salesforce Release Management teams across the globe.
Here are brief release highlights .

1. Enriching Salesforce Continuous Integration

In addition to being the only tool that supports all the major version control systems including Subversion , GIT, Perforce and TFS – AutoRABIT also has increased the support for version control deployments in AutoRABIT 3.6 .

  • Deploying a particular revision in version control system
  • User based Auto-commits

Deployment Using Version Control Revision Number

You can now deploy Salesforce objects, based on your version control revision number. During a deployment, give a revision number of the GIT repository, and you can deploy the metadata members belonging to a particular revision number. This is especially helpful during deployment of hot fixes.

User Based Auto-Commits

With AutoRABIT , the development team can continue working with sandboxes, while AutoRABIT runs the entire version control operation in the background with User Based Auto Commits.

Here are the steps to achieve the same:

Step 1: Mapping Salesforce Orgs with Version Control System

Map your Salesforce orgs with a source control system.

Step 2: User Mapping

After version control mappings, the users need to be mapped. With user mapping, metadata would be committed to a version control system. Map Salesforce Org user and AutoRABIT users.

Once a build is triggered, all the changes are fetched from the Salesforce org and based on user mapping, a particular user’s changes will commit to their version control system, as shown below:

2. Salesforce Deployment Enhancements

Validate Your Salesforce Deployments

With Validate Deployment, you can check if your Salesforce metadata deployment would be completed successfully.

After you select metadata types for deployment, click Validate Deployment. Now you can see all the metadata members of Source and Destination Orgs. It shows the metadata members that can cause a deployment to fail, and the corresponding error.
Now you have an option to deselect the error-prone metadata members and ensure that you have predictable deployments.

Enhanced Full profile Deployment

For Full Profile Deployments, AutoRABIT can optionally, remove any components that do not have visibility settings in the destination Org, which can otherwise cause your profile deployments to fail.

Pre-Loaded Salesforce Test Automation Templates for Orchestra CMS and Service Max

If you are using Orchestra CMS for your website publishing or Service Max for field service tracking , AutoRABIT has some great stuff in this release with pre-loaded Test Automation Templates, with which you can get rid of a lot of manual steps that are part of the implementation with those managed packages.

There is always one thing in common with Test Automation and going to the gym … they always get postponed!!

Salesforce Test Automation has always been on the wish list of most enterprises with applications who are looking for maturity and predictability within their application’s change management and delivery process. It is also known fact the Continuous Integration and Continuous Delivery journey is not sustainable if there is no regression test bed set up for the applications .

However, the reality is – Test Automation charter always gets pushed to the ‘next’ release …

Related Post : Automating Your Test Automation  (Testing-as-a-Service)

What is the Problem?

As part of the Continuous Delivery audit process we conduct with our Salesforce clients, the audit results of test automation has produced the following top-3 hurdles for Test Automation.

  1. Test Automation needs specialized knowledge and teams
  2. Over a period of time, the complexity of the test scripts grows and maintainability is an issue
  3. Test data setup for Test Automation is difficult [especially, if third-party apps are involved due to their complex relationship mappings]

What is Our Approach?

While working with the Salesforce ecosystem, like development teams, partners and architects, we constantly try to add innovation by addressing these hurdles.

The result of understanding the hurdles is the development of our ‘Selenium Curing Engine’ for the Salesforce Platform. This is the core foundation of our Test Automation Factory that accelerates the testing process and provides real-time automation for testing salesforce applications.

How Does AutoRABIT Address the hurdles?

With AutoRABIT’s Curing Engine, Salesforce Test Automation can be accomplished easily as below :

  1. Record your test scenario with the click of a button

[With your standard selenium IDE]

  1. Upload the file into AutoRABIT
  2. Enjoy seamless play-back of your recorded tests across your release environments.

Test Automation is really that simple and seamless with AutoRABIT.

What About Setting Up Test Data?

AutoRABIT’s Advanced Data Loader Pro pulls data from an object, including dependencies along with muli-level parent and child relationships, after which you can migrate this data into destination sandbox in with just the click of a button.

For instance, using AutoRABIT Data Loader Pro, you can pull all contacts and accounts related to an opportunity from Staging and migrate them into QA and UAT seamlessly.

The test data step can be included in the Continuous Integration process. This provides users with the power to package and deploy metadata, migration of test data and then execute automated tests seamlessly as a single process with just the click of a button.

With AutoRABIT, Test Automation Can be Achieved NOW . 

Try it, experience it, and believe it

With AutoRABIT – you can now choose your sandbox, choose your Apex Tests or selenium Tests to run and run them to get real-time log reports and the code coverage report . This can significantly improve your speed of testing since you need not run the entire test classes or functional tests in case of a reported bug or test failure.
As seen below, one can select the tests to run , choose the browsers to run the tests [in case of functional testing] , select the code coverage option if needed and you can mark the selected the test classes to run on a schedule as well .

Salesforce Test Automation can be accelerated to a much higher level with 3-step Test Automation Factory in AutoRABIT.

  • Test Transformation: Record the tests with utilities like Selenium IDE , upload them to AutoRABIT. AutoRABIT has its all-powerful curing engine that can fix playback problems on the fly and transforms the test case into a standard automated test which can play back seamlessly on multiple release environments .
  • Test Mapping: The uploaded test can be mapped to your test plans like QA or UAT or can be added to your Continuous Integration Jobs . You can also categorize your tests as platinum, gold etc., so that you can run a particular set tests alone if needed.
  • Test Execution: The Mapped test cases can be scheduled to execute along with Salesforce Continuous Integration Jobs that package deploy and tests as well as run just a set of selected tests alone when needed.

The selected test execution gives a perfect dashboard that you real-time information the tests that are in progress , the test results by category , the overall percentage , and the detailed error reports in case of any failures as seen below.

For the Apex Classes that are run in this iteration , the Code Coverage report is also generated . The Code Coverage gives detailed report of Class Coverage and Test Coverage as seen below .

Salesforce Test Automation has never been so easy with the simplest form of record-and-play back doing the work addressing the traditional hurdles of test automation requiring specialized teams and complex code maintainability.

For more technical details about AutoRABIT Test Automation Factory , please reach out to , if you wish to play with our Test Automation Factory for accelerated Salesforce Test Automation , please write to

The AutoRABIT Team will be present at DreamForce 2015 in the DevZone. We are all set to showcase the effort-less way to accomplish Salesforce Release Management and Salesforce Continuous Integration. Completely automated and out of box in AutoRABIT .

While No software is the Salesforce Mantra , No deployments for Salesforce is AutoRABIT’s magic wand .

Looking forward to seeing you there folks …

Contact us for questions or demo at