Empower Your Business with Automated Crm Software for Quality Assurance

How to create outlook signature

hello and good morning everyone thank you for joining jade global today for the webinar on how to accelerate your crm deployments by automating your end-to-end crm test cycles my name is sangeeta jash and i am the marketing manager at jade global and also your moderator today for this webinar now i would like to introduce amit iyer amit is the consulting director at jade global he heads a technology and engineering services group he is an av technologist and has a keen interest on how mobility and social is changing today's world and having a deep impact on how enterprises operate i'll hand it over to amit now who will review the agenda and continue with the presentation over to you amit thanks a lot sangeeta and thank you everyone for joining good morning good afternoon where you are um thanks for taking the time and joining our presentation today um i'd like without losing time i'd like to kick start on the presentation so i think my agenda today is to kind of brief you about the solution that we have we call it javs which is the jade automation framework i'm wanting to intending to run through its key value proposition the architecture the components the technologies that we built it upon some of the integrations the benefits i'm also going to be running a short demo and i'm also going to be talking about automation in the context of crm today so as if just as a frame as a background i wanted to kind of say that jaff is is an agnostic automation framework built on the selenium platform and we have basically extended selenium's capability to beyond web applications so traditionally selenium is limited to web applications only whereas leveraging jav you can kind of extend that to any kind of non-web application which means you can do it with your sap your erp and any of desktop applications and things like that that might be integrating to your crm applications today however today's focus of the webinar today is going to be largely around crm and how you can leverage jav for accelerating your crm deployments so angular you want to cover the participant server sure yeah we'll launch a quick poll here so our poll question is what do you aim to achieve by employing test automation in your enterprise so is it to improve go to market time or to save time and money or to increase efficiency of testers or to improve test coverage or increase test repeatability so you can see five options on your screen we would request you to click one of the options which you think is applicable to you please use one of the options displayed on your screen and submit your answer all right thank you very much for answering the question we'll close the poll now and thank you all for uh submitting your responses to the poll uh so it's looking like uh most of the responses are kind of focusing around improved go to market and increased efficiency and saving time and money so that's that's kind of the trend we notice as well so i think this is no different to some of the times we are noticing amidst our customers so before i start and kind of talk about jeff right i wanted to kind of give you a little bit a little bit of a background where jf kind of came out of right so within within my practice within within the jade technology and engineering services practice we have qa and testing as a horizontal service so it is basically a unit that services qa across all of our different lines of business across all our customers because we see quality assurance as a key part of your of your business these days uh we are changing the we are seeing changes in the way the market works today we are going into shorter agile cycles we are going into short releases we are going to be seeing multiple releases in the market whether it's your crm systems or whether any of your systems so it becomes more important for you to make sure that the software that you release into your production system is accurate and does what it meant to be doing and that's why qa becomes very important and at the same time you cannot be manually doing your qa all the time because that takes a lot of time and effort it increases the cycle in this dlc time and that's where automation plays a key world so we are seeing this as a as an increasing trend uh especially with agile customers who are adopting uh automation at the first go and and jaff kind of came out of that particular requirement or demand that we saw in the market we saw there was a lot of market demand for automation related tools however the cost of automation tools commercial automation tools from the likes of hp or ibm it was very high some of our customers used to be spending about a million dollar plus annually on some of these tools just in terms of the licensing cost so uh and and traditionally we've also seen selenium picking up a lot of market it's kind of the market leader when it comes to web-based or browser-based applications so but but there was a limitation with selenium it can only test web-based applications so what we did basically was we our test center of excellence focused i mean we invested in the rnd around this we created our own custom wrappers we created our own framework on top of the base or underlying selenium framework and basically made selenium made it extensible to work for any kind of application so whether it's a siebel crm whether it's a sfdc kind of a system on premise on cloud it can test all kind of applications even integrations so that's basically uh the the kind of uh the rationale behind kind of bringing this solution in the market and what we believe is unique about the solution is the fact that there is no other uh open source solution that can test all kind of web and non-web applications especially on with the selenium underlying platform um that uh and this is the advantage so you basically save a lot of costs just in pure licensing apart from the other benefits which i'll talk about in the later slides so as i said jaf is built on a combination of open source tools so you don't pay for licensing costs you don't pay annual maintenance fees and things like that we believe it's the industry first solution for automating web as well as non-web-based testing based on the selenium framework again uh we have integrated with it with plenty of open source test management tools continuous integration tools defect tracking tools and things like that to kind of make it automated from a test sdlc perspective then we also have automated out of box accelerators for oracle ebs and crm which we'll talk about and showcase in the next few slides then our entire approach has been based on a data driven testing scenario in which basically we try and eliminate the test data problem that many of our customers have so how do you efficiently manage your test data efficiently leverage it for your test cases and your test scenarios and don't kind of end up doing repeatedly a lot of typing on the forms and the screens and things like that so it's like a it's like a unique approach which helps you save a lot of time when you kind of do your testing cycles um before i kind of jump into further things i wanted to just kind of give a guideline around what are our typical considerations you should have when you be when you'll be kind of going towards an automation approach whether it's for a crm or whether it's for any of your enterprise systems it doesn't really matter but what we think is the ideal approach towards automation is basically on these three pillars all these four pillars so basically it's not a roi led initiative so automation is always uh an roi led initiative so you need to kind of manage how your manual testing costs pan out over the year how many releases are there how can you reduce the cycle time and how can you how can you kind of increase your efficiency so that's what that's what automation is all about it's also about optimized automation coverage which are which are your primary candidates for automation and what should be automated first which are your candidates that probably should not be automated you need to be also considering some of your business process you need to also align yourself to the program roadmap for example if your application is going to get upgraded or some of the modules might have a tremendous set of changes maybe they are not the right candidates for automation and then the core or the pillar for automation success is what are the right kind of tools and frameworks that you use for automation so coming to jaff right um the thing that that kind of differentiates jas it's it's it's is its ability out of box when it comes in the open source world and the kind of integration it offers out of the box so our motivation behind creating jf was to not just automate the business applications in question but to also automate the entire test sdlc when i mean that sdl sdlc i mean right from picking up the test cases from a test management tool all the way to raising a defect and sending out a report the entire process has to be automated so that was our major motivation towards building jaff and we have been kind of increasing the number of integrations that here as you can see in this diagram we already have it integrated with the likes of test link test trail which are major test management tools in the open source world we also have it uh integrated with the likes of jira mantis bug zilla which are very popular defect tracking tools and we also have it uh integrated with performance testing tools like apache geometer and that apart we also have integrated with the various continuous integration tools likes of jenkins and the hudsons so that the moment your your build is checked in and automation can be triggered automatically there need not be any manual intervention so right from as i said the summary here being right from picking up the test case from the test management tool all the way to raising a defect and sending out a report the entire process is automated so that is that is the core benefit of jeff and that's where i see most of our customers getting the benefit of chaff it kind of tremendously increases the cycle time so what used to be kind of running in hours and hours of manual activities can run literally an overnight cycle a couple of hour cycle and and kind of you get the results fully populated for you in the most accurate fashion a little bit more about jaff architecture okay now i'm not going to be kind of talking about every module that is built into gif and run through this complicated architecture diagram which are architects allowed to put out but my kind of the the view i say uh from an architect's perspective right is we kind of saw three major actors in an automation testing scenario uh the first one being the tester himself the second one being a acuit director or an i.t director who would want to see what's happening uh how is the how's the release testing going uh and the third being a developer who's kind of waiting for for uh for the tester to say hey all is good the code can be signed off so with these three key actors in place right uh that's that's how we kind of designed this system so what does a manual desktop needs he he needs he he doesn't want to be managing a lot of test data he doesn't want to be doing a lot of manual activities he wants to be seeing things run on its own he doesn't want automation to be done and then he's looking through a whole big report and raising defects himself so all of these things can be actually taken care by the platform itself and that's what that's how we have created and designed jeff same for the developer now what he wants to be seeing is the standard problem which we typically have in a software life cycle is a developer and a tester there is always a lot of back and forth that happens hey the the tester raises a defect developer comes back and says i cannot reproduce it standard problem and it's not it's not happening in my environment this is not an effect so this is something we hear often so how do we resolve some of these problems so what what jaff really does during the way it runs is it picks up various screenshots at various different scenarios and unit levels and it kind of gives the developer enough ammunition for him to say exactly hey this is the point at which this has failed and this was the message we got this was the logs at that point of time so the back and forth that would typically happen between a developer and a tester is kind of significantly reduced when you have all this kind of ammunition that you give to a developer and reproduction of the problem becomes easy so this kind of helps you again in reducing the cycle time again from say from a typical i.t director's perspective right his motivation or his interest rather is hey how is the whole thing going on we have a few thousand test cases how many have passed how many have failed how much it's going to take to retest the whole thing are the bugs already locked is the developer looking into it so how can he get a holistic view of all of this so we kind of built a reporting engine around it so basically all the kind of typical items that you need whether it's a reporting engine whether it's an smtp integration whether it's out of box accelerators is something that we thought through in the process over our years of experience in this domain and we kind of built it all together and bolted drawn on the underlying selenium platform which is inherently very powerful and kind of created this whole solution so in terms of a little bit about the technologies used so it's all based on java largely by large as you can see i'm not going to be naming every component here but we are we are looking at in terms of skill set you are looking for a selenium test engineer to be able to manage this for you in the longer run we have support across all the browsers most of the popular browsers today across most of the popular os today and and it can not only test web-based applications it can test desktop or non-web-based or even your mainframe applications for that matter if you have integrations with so from a crm perspective right and these are the four paradigms can that jazz can cover inherently so the problem that that most enterprises that i see is you need to they they end up having different kind of tools to test different kinds of applications so for example if you have an oracle erp system you can't really use selenium because selenium traditionally does not work with erp and then if you have an sfdc kind of a crm system that then you can obviously use selenium but then you might also have a mainframe system which does not work with any of the popular tools today so what is the solution to it how can you have a unified automation strategy how can you use the same platform to be testing all of the different problems for example if you want to be testing mobile if you want to be testing your cloud-based applications if you want to be testing security js is kind of use we've thought through that and we kind of designed through a single platform that gives the capability to be testing all of these different paradigms whether it's localization whether it's performance whether it's security whether it's mobile all of this can be tested leveraging jeff so that's really the benefit that you see so some we have seen that some of our customers want us to test the salesforce.com mobile app and that's kind of possible using jf we have seen our customers asking us to stress test their hmtc systems and we are able to do that leveraging java itself so you don't need to be looking at multiple solutions some of our customers also have legacy applications that is integrated with their crm systems including some of their fulfillment systems which are which are not really web-based but we are still able to leverage the same tool to be even testing those integrations so that's the benefit of jaff really you don't have to be buying different set of tools from the market and investing a lot in licenses and that in turn obviously adds up to your maintenance costs as well so coming coming to uh crm what we have done very beautifully is we have kind of created a set of pre-built test scripts uh business flows across the standard crm processes right from creating a target a campaign all the way to creating a code um to creating a of creating an opportunity to creating a code and and even further integrations downstream if you have a fulfillment system or if you have an erp system that integrates with your crm all of those kind of we are covered by a pre-built set of test scripts when i say pre-built set of test scripts what i mean is all of your vanilla test cases that you already kind of built and thought through it's already there out of the box it's available out of the box so it kind of accelerates your test process it kind of gives you the basic vanilla functionalities already automated out of the box to you uh to help you accelerate your testing clc then all that you need to focus above and beyond that are the customizations that is in place at your right so obviously customizations would differ from various installations at various different customer sites so that's a part that needs to be taken care of separately but it's significantly we have seen from a basic customer perspective who wants to start off from scratch for automation we have seen there is a sixty percent acceleration if you are able to leverage the job framework and some of the pre-built test accelerator suits just to also give an idea about the test accelerator suit we kind of as i said we're kind of covering all the business crucial business flows there are about over 134 test cases that we have covered um already and it's increasing so that's pre-automated verifications and validations across various modules whether it's campaign lead account opportunity contract uh various business processes within that at this point of time i'll just kind of quickly go and show you some of these test cases a little bit more in detail because we have this documented in testing so i'm going to go over the powerpoint presentation mode and just show you how it looks on a typical test link system so here is an example of our documented test cases say from a crm perspective okay of how a lead is typically configured so here is how the specifications would look like so these are all the use cases that you see typically in in a scenario in an acceptance scenario how do you kind of log in what are the test cases what are the steps so all these use cases come really handy in your practical environment and kind of accelerates you already so this is an ever growing list of test cases which our customers are able to leverage out of the box all that they need to add on to this on top of this is typically the customizations so and this kind of gives a lot of benefit sometimes we have seen our customers literally using these test cases for doing the sales training as well so there are some other benefits as well apart from automation testing i'll go back to the presentation so now that we've talked about this okay i want to talk a little bit more about how integrations are typically covered so typically you don't have standalone systems in an enterprise you want ideally enterprise applications that talk to each other uh we want a machine to machine interactions we want uh we want on-premise and on-cloud integrations so how how does it work right so how can you have a unified automation strategy so if you have an sap kind of a system an oracle ebs or any other eba system that interacts with your crm or any other custom apps for example you might have a fulfillment system as an example one of our customers has as a rental system that he wants integrated with with his crm system so how can you have a single automation solution that can cater to your integrations scatter through all of this multiple touch points that you have in your enterprise and that's why jas comes handy jaf is not only a crm solution it can also help you integrate so if something kind of flows in from your crm system to your ebs system or otherwise or through your fulfillment systems you can just simply use this tool and kind of run through it so that there's a lot of benefit that comes out of it you can literally test your entire enterprise business flows leveraging an automation tool and that kind of is it's very significant manual effort typically i would say between doing things manually and between using a framework like js you would at least save 90 of the time that's that's what is the minimum that we are seeing at our customers because that's how fast this runs we also benchmark this against some of the very popular tools so we use hpqtp which is a very very popular and very very expensive tool to be doing automation testing and we kind of ran it through various parameters and benchmarked this against it picked up all the best quality features that you would get out of box on hp and kind of build the equivalent in the open source world so basically hp has integrations with their quality center as part of the alm suit and we have kind of integrated that with wrestling in the test trail which are very very popular open source test management tools that are available in the market to kind of that's the one i showed it in the previous browser then we can even help you migrate from your hp qtp infrastructure to the test link we have created automated scripts for doing that so the biggest difference however is obviously the licensing and annual maintenance fees so there is zero licensing cost as far as jaff is concerned whereas with hp you kind of end up not just buying server-side licenses agents but you need to be also investing on a lot of plug-ins so if you're having siebel or if you're having a particular yeah or a kalibia system you need to be buying the equivalent plugins as well so the cost is kind of incremental with every system that you plan to be using and the amount of testers obviously also further increase the cost because it's all user based a licensing model but as with jf there is no licensing model whatsoever it's all free um it's all deployed at your premise uh there is a cloud version of jeff that's going to be coming out soon we are kind of in the final stages of finalizing that so we'll be kind of doing a follow-up webinar to discuss around jaff on the cloud but at the moment we support an on-premise deployment model the other major difference that i see with qtp especially is the amount of hardware that that's required so because this is based on the underlying selenium framework which is pretty lightweight and java it's quick it doesn't need hardware it doesn't need the kind of hardware and servers that is typically required now in case of a tool like qtp so we are talking about literally desktop grid pcs that can literally run your automation testing scenarios uh in many cases our customers simply use vms to kind of deploy we have situations where we are able to kind of distribute the load across various vms and kind of do a lot of concurrent execution whereas in a qtp typically the execution is serial or need to kind of but buying in a lot of license to kind of running things concurrently um again we have a customized reporting engine whereas quality center has its own build dashboard so we kind of created the equivalent in the in the java scenario so all in all to kind of conclude on this slide i would say we have kind of built the equivalent of an hp qtp at a much much slower and cost effective model leveraging the basic selenium framework which is one of the most popular industries when it anyways comes to web-based testing and we kind of extended that to non-web-based and desktop-based applications and things like that so from here i would like to move to a short sfdc demo that i have with me uh it's basically a recording that kind of goes through various scenarios that i have i'm going to run through this recording uh at places this recording is going to go really fast because automation runs fast and we have kind of slowed it down just so that you can look at it so what you're seeing on your screen is a test management tool wherein your test cases are usually scripted we kind of recommend we like this link a lot so we kind of recommend that because it's it's really easy to kind of have everything on your uh on an online web-based portal as far as test case management goes rather than having multiple excels floating around so this is a small five scenario in which we kind of created campaigns assigning it to leads leads to account and all the way to till the court process so a typical crm scenario we also incorporated a failure scenario just to show you if something fails what happens next so this is this is really the beauty of jeff it's completely data-driven which means all of the data that you see in the forms need not be entered manually it can be directly picked up from either an excel or a database and across various modules that you would have in your crm system you can host in a lot of data it's a one-time effort to kind of compile this data and put it here and every time you run like an automation regression suit you can pick up data from here itself i can keep adding to the data which means you can literally run thousands of test cases across thousands of record sets and and data management becomes easy so the automation is kind of triggered here it's invoking the salesforce instance we've used salesforce as an example in this case and we kind of go through the campaigns to leads leads to accounts accounts to opportunity and opportunity to quote kind of a process here so it's picking up data from the excel that you previously saw and it kind of executes it automatically as you say we've kind of slowed this down a little bit but it's still pretty fast as you would recognize so that's how the power of automation is you can literally run thousands of test cases in matters of hours which traditionally in the manual world will take a lot lot more time and as you can see the framework can handle all the components that sfdc can typically throw at you whether it's pop-ups drop-downs calendars text boxes all different kinds of fields that will typically inquire kind of come across in a typical automation scenario so we're converting the lead into an account so basically what what what what what what i mean by the demo is your entire business process can be completely automated and tested so every time you are having changes made to your salesforce.com system you can literally run the regression through that can tell you hey what's working what's not working and things like that so it automatically raises the defect as well which you'll be seeing further downstream in the demo so here is a new opportunity you can see different types of speeds getting invoked um and from here it kind of moves into a the creation of the opportunity you can create both positive and negative test case scenarios whether it's across any of these modules across multiple data sets this is a typical opportunity to code process so we see that some of our customers use customized processes so that is absolutely not a problem we can kind of customize it if you have added newer fields you can kind of use that and customize the automation script at the same time kind of significantly saves time and bandwidth when it just comes to testing the platform in place so this is the opportunity creation and from here i think it's proceeding to code creation yeah so if you have integrated systems this can also work across integrated system we had we had done a separate webinar previously in which we had shown an ebs to a crm integration scenario so even that is available on the internet if you look at the gate global's youtube channel you'll be able to see that as well this is a negative scenario in which we kind of simulated a negative test case and we kind of automatically raise a defect for that negative test case so this is just to give an example um so the automation run is now complete you get an automatic email report that says what your tests where what how many pass all the 13 test cases 12 passed the one that we purposefully failed and it's a defect raised against it and there's a detailed html report that comes out that has a tree kind of navigation we can customize this report to however we want some of our customers want their logos and backgrounds as per how they want it so we can completely customize it to the look and feel of our um to how how you would desire here it also picks up screenshots at different stages so that it gives a developer enough ammunition to kind of tell him here at what stage it has it actually failed so the developer can literally do a step-by-step debugging so that's really a great help so especially in a failure scenario you can see what really failed so in this case it was the account didn't exist in the account table because we didn't put that in so that's how it works and and the other beauty is all of these results that you see in all of these test cases that you run they get all automatically updated back into the test link so you get past fail scenarios for clear auditing results you get you get the defects that are raised you get traceability back so if you if you want to be looking at a regression test suit that you ran three months back you can always go back to the build and check you have the whole documentation ready you don't need to do documentation manually again so this is this is the bug that was created for the failure scenario the bug was we use bugzilla as a defect tracking system many of our customers use different kinds of uh uh defect tracking tools so we can integrate with any of those tools so that's one of the other benefits of automation you can kind of literally automate the entire test is dlc leveraging the apis that we have already built across any any tool for that matter it doesn't really matter which tool you use uh in this case you use bugzilla so this this was a short demo we were kind of show so what you really saw here was all the way from uh from uh from seeing the uh test the test cases picked up from the test management tools all the way to raising a defect and seeing the report uh you saw the whole thing uh as part of it single flow so you kind of automated the entire test as dlc per se i'll again go back to the powerpoint mode and kind of continue to what is kind of my last slide here so what are the business benefits um so what did we what do we kind of see what why is any different compared to conventional tools so compared to selenium there's a big difference it can test non-web-based entities so there are really no industry tools that can test non-web-based systems so if you have a crm or sfdc kind of system integrated to a mainframe or integrated to your fulfillment system that is built on age-old technologies or non-web technologies you can test it using a unified automation solution so you don't need to have a disparate automation strategy for you you can just use one tool to solve all your problems it's customizable it's scalable framework it has the out of box accelerators for your crm and ebs instances it comes with integrations with defect and test management tools and continuous integration tools which makes which makes everything automated so the manual tester does not even need to raise a defect it's automatically raised for him then it comes with customized html reporting so you get a detailed report at the end of it so if you're running a few thousand test cases imagine yourself getting a mail overnight and the automation running all by itself with no manual intervention whatsoever and kind of giving you a report saying there were a thousand test cases that ran 998 passed two of the test cases failed and for the two failed test cases you already have defects raised in your system that your developer can come in and look and he already has all the information to fix the problem because he has all the screenshots he should know where to look into and there is no kind of back and forth that typically happens in in a testing environment so what we see the benefits here clearly is there's a reduced cycle software cycle time crm systems are typically used by your sales teams who bring in the revenue to you so it's important for them to be having the latest and the most stable platform and that's what automation kind of helps and and many of your teams would be using different kind of browsers so cross browser support is not a problem whether they're using a mozilla or a chrome or an ie it doesn't really matter somebody's using a macbook a safari we can run it we can run all of these browsers and test the same applications concurrently the other finally i would add to the part that it's completely data driven in its approach so uh you saw how we have designed the uh for the application to pick up data from the xls itself that kind of simplifies a developer's test management problem so these are some of the things that we kind of put into place while designing jaff and and and we believe there is no other solution in the market that kind of caters to something like this in the open source world so it's something that we're really proud of when we kind of designed the solution and and this is what we see as a clear benefit and the customers are kind of reaping the benefits out of it in some cases just purely out of license cost savings we are helping our customers save about a million dollars in licensing cost savings and obviously the time to market becomes very crucial for them when they come and see some of these out of box accelerators for them it typically accelerates your project cycle by at least 60 percent so 60 of your work is already done what just remains is the customizations part the framework can be deployed in weeks and in days literally this this it's it's not a long life cycle when it comes to our automation testing tool uh all of the software and hardware that's required here is is kind of literally out of box it's open source it can be installed in it the kind of skill set that you would require to maintain some of this is is really available very easily in the market java skills are very common so it's not going to cost you a lot of money to kind of maintain it in the long run as well maintenance costs are only limited to the costs of the changes that you make to the application so for example if you added a field or added a new step to your process the equivalent changes in the automation scripts need to be made so that's how i see jeff helping our customers so you can call us on the numbers displaying on a screen right now or you can also email us at marketing at jadeglobal.com we'll help out with any query you have and thank you once again very much for attending the webinar have a wonderful day