Casestudy Template

Case study: Project Name


Case studies should speak to your target client. Choose a project that aligns with your ideal client and that showcases how your product or services were effective in solving the client’s problem and reaching their goal. Give a quick summary of the story you’re about to tell, including a brief overview of the problem and how you solved it. Keep this section to 3-5 sentences.

client Name


Company Bio

Short description of the client and its main service or product. If there is more than one product, give an overview of the division or product you worked on

Key Benefits

Key benefit 1

Key benefit 2

Key benefit 3


The story you want to tell should showcase how your product or services either: provided a noteworthy solution to a particular problem, involved a well-known client, and/ or achieved outstanding results. In this section, describe the problem the client came to you with in detail. This is where you should discuss the end goal or purpose of the project. What metrics determined if the solution was a success? Were there any secondary objectives and how were those measured? What were the risks?


The client has Salesforce (SFDC) and non-SFDC applications, but no automation. Both types of applications, in addition to their APIs, need automation.
The application needs to be automated for different regions like the USA, Netherlands, Spain, Japan, Australia, and New Zealand.
Browser compatibility testing has to be performed for different regions, based on the usage.
The client follows SAFe methodology and wants to complete regression testing faster for every release.


Our team worked with product owners and manual QA of various regions and identified:
Regression test cases that needed to be included in the automation.
The application flow and data creation process of each region.
Integration areas between SFDC and non-SFDC portals.
Automation scripts were developed for SFDC objects, Pages and APIs using Provar, and for non-SFDC applications using Selenium.
New automation scripts are now identified for every sprint, and the automation suite is updated accordingly.

Tools and technologies |


  • Regression testing became faster for every release.
  • Increased browser coverage for all the regions and saved approximately 120 hrs of manual testing effort per release for each region.
  • Functional testing was done at both API and application levels.
  • 30+ regression defects were identified early in the cycle and all the automation scripts are integrated with AutoRABIT.

About Palni

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.