Moderator
Good morning and good evening to everyone and welcome to the Pcloudy webinar series the topic for today's webinar is lifecycle automation for multi-channel
Moderator
Testing with cloud-based LAN this is a joint webinar presented by Pcloudy and our partner hexa where before I introduce our speakers a couple
Moderator
Of housekeeping notes the audience will be in mute mode for the duration of the webinar however please do send in your questions in the
Moderator
Chat window and we will address them at the end of the session all right let me introduce our first speaker for today our first
Moderator
Speaker is Nagendra BS he is the associate vice president digital assurance practice and solutions at hexa where our second speaker is Nilesh Rowley he's
Moderator
The vice president pre-sales and operations at Pcloudy with
Moderator
That let me hand over the session to Nagano Nagano all yours
Nagendra
Thank you
Nagendra
We really have two parcels webinar first part is their meeting run you through
Nagendra
DJs in the solution that we talked about multi-channel testing and second part is where we will have more discussion specific to their platform from
Nagendra
Now you are seeing that in past life in the next 45 to 15 minutes we plan to wrap it up where you want to
Nagendra
Cover the following things where we will start with in terms of how do we actually achieve quality with speed and what are the key
Nagendra
Drivers for this and then there's something which we have been talking about and people who have some of the previous webinars it could be
Nagendra
More of a kneecap and then we were most respect to the multicam testing specific challenges looking to some of the key challenges
Nagendra
Then we will get into the solution how do we apply the lifecycle automation right now how do we deliver the molecular automation for the
Nagendra
Multi-channel testing we look at more in terms of the architecture what we actually have built for our customers and also we go through a
Nagendra
Demo specifically taken to the nuts and bolts of the solution and lastly we would have only English from the glory talked about key features
Nagendra
Of the cloud mr. Bergner now moving on I think there's something which we as practitioners have been seeing day in and day out where
Nagendra
Quality with speed is more of a given now the earlier old-school wherein one has to compromise between speed and quality right that's no more
Nagendra
Acceptable not just for customers even for ourselves right as practitioners will be in business for a while now that's something which is
Nagendra
Hygiene if you ask me negatively and if you look at in terms of what options we have to address this quality with speed with
Nagendra
Ease a need of the hour especially considering a gel and digital transformation between the drivers of the Riven xx speed now but when we
Nagendra
Have an organization started looking at how do we achieve this quality with speed what are the options that we have and what are believers
Nagendra
That we can actually bring in so firstly what we did was we took a look at in terms of if we have a deliver
Nagendra
Quality with speed given everything what we'll have today automation is something which is a biggest newer purse to deliver quality the screen and for
Nagendra
That we start looking at in terms of if we are doing enough automation why are we not able to achieve quality will speak to
Nagendra
Me right and that's when we spend little more time in analyzing where the effort is going and as a practitioner you look at the
Nagendra
Effort that goes in any of the testing projects right or any of the testing programs it was pretty off whether it's waterfall a day
Nagendra
Or a night waiting metrology there are four key activities that against which we consume our effort was one of the corresponding dollars and ninety
Nagendra
Percent of this effort goes into primarily the design where we how to write test cases agree not the test cases and report the test
Nagendra
Cases I am talking about very broadly now within that they were all mostly full percentage that gets between strict between design and in terms
Nagendra
Of the execution now if you look at the focus of a traditional automation primarily has been on penetration wherein we have a relationship that
Nagendra
We identify for our release contries testing and we try to identify what about about about test cases and go and automate that and that
Nagendra
Is more of it post facto now that's where we saw that next step if customers spending $100 will probably all 16 dollars is effort
Nagendra
Against which we are trying to optimize and we have white says that actually we can impress across design not just in terms of bringing
Nagendra
In the automation for the test case design but also trying to bring in auto machine even for a provision system when we say program
Nagendra
Testing it's more in terms of instant automation I haven't when the new switches are built how do we actually test them no automation the
Nagendra
Last part is more often reporting and how do we bring in an integration between all this and the solution that we have come out
Nagendra
With I will talk about in detail that's more in terms of looking at what are the drivers are speed quality now if you look
Nagendra
At there is a different aspect that we'll also have to keep in mind when we try to address this from the digital transmission point
Nagendra
Of view when you say digital transformation it's the way we engage with our customers using different digital channels right it could be more in
Nagendra
Terms of the current browser based where web becomes the primary channel second it could be mobile where everything go hide there are different options
Nagendra
That which you can engage it could be a gate a browser based or a native app or it could be any other channels that
Nagendra
We actually use to interact with our customers now the moment we get into the multi-channel where customers try to increase they reach to their
Nagendra
Customers using different channels it brings me all together different challenges right be it in terms of looking at how do we ensure that whatever
Nagendra
Functionality that I am offering to my end customers is performing consistently across all the different channels and that becomes more practical especially with different
Nagendra
Form factor of devices with operating systems and the different OEMs now adding to that would be in terms of assuming that I have to
Nagendra
Support all these channels how do i optimize our i you tested for one channel and that itself was time consuming now I have to
Nagendra
Support your former channels how do we optimize the testing effort across all channels third even if I decide to have some approach to optimize
Nagendra
There is I am going to invest in the tag to do or having the right kind of infrastructure right that's where we have to
Nagendra
Look at how do we make sure that we keep in pace with the ever-changing market in terms of the kind of devices that actually
Nagendra
Prefer it at the same time how do I address the maintenance part of me and finally in terms of these are things that more
Nagendra
In terms of the interest child regardless but however we also optimized the testing through automation having a platform which enables us to test all
Nagendra
The different channels with all reason right so there are some things which we have tried to address both from the lifecycle automation part of
Nagendra
Me and also from the multi-channel testing for us now getting on to the specific solution that we talked about in today's webinar we have
Nagendra
Built a platform called integrated design to institution I need to be in shock which enables us to look at automation across the testing and
Nagendra
Thinking starting to test case design wherein we leverage the model-based testing tools to generate the test cases now on top of that we also
Nagendra
Have built-in integration between model-based testing tools and the automation framework in this case we have built a multi-channel automation framework called Talos wherein it
Nagendra
Supports different channels in terms of the web in terms of desktop there's applications or it could be mobilised application chatbots and different technologies where
Nagendra
We can leverage the automation approach even for the traditional sdse ah more of a BDD or tv/dvd given is DMC right so that's where
Nagendra
The automation framework is capable of supporting all the different sdsu type and also all the different channels now what we have done is we
Nagendra
Have worked with our path work in this case confirming who provides us the primary platform for the model-based testing and we worked with them
Nagendra
To build what is called as a connector or the publisher by virtue of which we can actually not only generate the manual test cases
Nagendra
The one the item number one the casing on the screen but also generate the corresponding automation scripts and the third key important part is
Nagendra
We not only generate the automation scripts for one channel we also generate the automation scripts for different channels wearing using a single model which
Nagendra
I'm going to talk about in detail we can generate automation scripts or it could be for a mobile application which could be for for
Nagendra
A desktop application or it could be ever browser-based application and there are different combinations that we can have within a mobile application now finally
Nagendra
What is that we're trying to achieve we are trying to the integration between design execution and the last component is our reporting where in
Nagendra
All the results that gets executed or automatically uploaded onto the test madmen - it could be in here with this language goes in the
Nagendra
Market and make it seamless between design execution and reporting and finally what is that you want to achieve one how do we ensure the
Nagendra
Productivity improvement faster time-to-market with a reduced cost right and we will have more details of this through the demo in the next few minutes
Nagendra
Let me start demo and this demo would be for around five to seven minutes and overall round is another 10-15 minutes going through in
Nagendra
Detail right so what we've done is we have taken a simple scenario wherein we want to test a given functionality for example booking a
Nagendra
Flight which all of us are familiar with for different channels right where we could use this functionality on Android app or it could be
Nagendra
On a browser-based desktop web or it could be a mobile web and the tools that finally we actually use are one is the model-based
Nagendra
Testing tool which I talked about before with an integration with our Talos which is a multi-channel automation platform and the last component of this
Nagendra
Solution is the Pcloudy device form which enables us actually in providing the required devices as well as the browser combinations on demand
Nagendra
So we'll go through the workflow and the simple workflow that we have taken for your understanding where you could see that the starting point
Nagendra
Can be the same for all the channels but the path that you take would be different now how do we do it now lot
Nagendra
Of these systems will approach wherein you represent the behavior of the application in the tool and there are different tools in the market today
Nagendra
And this with your market mouth unlike with five years before where there was so much of effort with were to build a model and
Nagendra
The skills required for building model was different on together from the skills that you acquire today now coming to their way the model is
Nagendra
Built in the model system to that we have chosen basically if you imagine a screen right imagine is three wearing you would have different
Nagendra
Controls or objects and these controls are bound together by a business logic now the tool allows you can represent the behavior of the application
Nagendra
First by capturing the different controls on the screen and through the what they call is in structure diagram and then I have the business
Nagendra
Logic built between these controls by having an activity diagram now that's something which will talk in terms of how we did it but before
Nagendra
We actually do that first thing that I have to decide is what is the output that I want from the nodding right and that's
Nagendra
Where I choose and the two thing that we are choosing here are one we are saying that I need a XS which is the
Nagendra
Manual test cases that I need generate and secondly what you're observing is at a low scripter and this is an exclusive stik-tek which are
Nagendra
The connector that have been built in collaboration with a pasta for our automation framework right so with this I will choose what kind of
Nagendra
Output I would want once I have chosen output I were born I want to represent the behavior of the application in the two and
Nagendra
The first thing I do is I create the common structure diagram because this is something which we take a call based on the kind
Nagendra
Of application right finally if I can actually represent all the controls across the different channels there is a lot of reason if I can
Nagendra
Bring him by having this controls being reused across different channels that's where I have a common structure diagram to represent the application behavior and
Nagendra
Therefore the controls in terms of the business process right the business logic each of the channels might implement in a different way right and
Nagendra
Again depends on the charming and the strategy that each of the customers adapt in terms of how they want to have a workflow for
Nagendra
Each of the channels depending on that we can decide whether I would have a separate activity diagrams for each of your channels or I
Nagendra
Can have a single activity diagram for all the channels if you see in this case we have three separate activity diagrams get it for
Nagendra
One for Android native app mobile web as well as desktop web the good part is there are almost 70% of these ability across all
Nagendra
Of this actually diagrams varying you have a common structure diagram so once I do this I will have to review the Aqua diagram for
Nagendra
Me does this logic point of view and who does this if you created me a business user other business analyst instead of reading the
Nagendra
Test cases the focus should be on reviewing the model which is more simple and more intuitive compared to the traditional approach now once I
Nagendra
Do that using my connector or descriptor I will be able to generate automation scripts now what you are seeing is this is where again
Nagendra
The connector comes into picture where I can decide which channel I need to actually build the automation scripts now there are different channels that
Nagendra
Are supported in this case we have Android native as one channel lobokoff another channel and as well as got there's a mono channel now
Nagendra
Once I choose this with a click of a button I will be able to generate the manual test cases as well as the corresponding
Nagendra
Automation scripts now this is a process wherein one has to load the model it is more of a compilation and then I generate test
Nagendra
Cases now you can see on the left hand side you could see that there is a folder that has come up talos right and
Nagendra
This is where we have worked with our partner to map the controls as well as in terms of the different actions of the tool
Nagendra
Model-based testing tool with our automation platform which enables us to generate the scripts which I will work in little more detail and I will
Nagendra
Be able to use them by importing these scripts seamlessly onto the platform so similarly I adopt an approach for different channels today I have
Nagendra
Only changes coming in one channel then I can only choose that specific channel and go real good in this case we are choosing different
Nagendra
Channels for example we saw generating the automation scripts for native app similarly we have out generating the automation scripts even for the desktop web
Nagendra
Right and moving on you can also see that we also generate the corresponding automation scripts even for any browser business application so what what
Nagendra
This provides is flexibility where any I will be able to choose dynamically channel against which I need to build automation scripts and make sure
Nagendra
That I have the required connectivity also enabled as part of this whole integrated design exhibition which I'll talk about in terms of the device
Nagendra
Infrastructure so this is where you saw in terms of how simple or seamless it is to generate the manual test cases and the automation
Nagendra
Scripts we will now go through the little more details in terms of how does this look like right what you saw is we saw
Nagendra
Generating the automation scripts and manual test cases for three channels we'll just take a simple look at in terms of what each of them
Nagendra
Look like right for example manual test cases they show this is the manual test cases that we have been able to generate for the
Nagendra
Android natira we're in the tool generates the test cases which in a language processing that enables us to get the test cases assets somebody
Nagendra
Has a little money right now the manual test is what you saw and similar tests can also generate for the different channels and the
Nagendra
Tool also generates the corresponding requirement traceability matrix wherein it provides you an option to map the requirements the market level and the same gets
Nagendra
Actually implemented as part of your traceability matrix the other thing that I want to talk about automation scripts and this is the most important
Nagendra
Part of the whole solution where and if you look at as part of automation scripts we 'i'm break four or five different output friends
Nagendra
One is called as an impact analysis which actually comes in handy especially if you are doing a maintenance and when you're doing an in
Nagendra
Spring testing where the functionality is build incrementally I need to identify which other test cases our new test biessings whichever test cases are actually
Nagendra
Got modified from the previous version of each other which I've got added new are which are the money which are obviously right so the
Nagendra
Typical approach is to go manually and identify those impact analysis in this case we inherit the impact analysis feature of the tool onto the
Nagendra
Automation script and what you see is that impact analysis file which will be used by our automation platform in the backend to identify the
Nagendra
Impact of change on the model that is more in terms of the file that gets you in the backend the second one what you
Nagendra
See is the actual mapping of the components right where you see the mapping of the different components are the two modulus testing tool with
Nagendra
Our automation platform the third one is more for test data which is very important where you will be able to map the test data
Nagendra
Either at the model level or we'll be able to point it out to an external data source and the last one is in terms
Nagendra
Of the acute which actually is the test cases and object repository something which also gets graded as part of the whole exercise and one
Nagendra
Has to spend effort in updating columns in column D again we have the scanners which are built to get the object details and this
Nagendra
Also gets automatically populated thereby eliminating the need for somebody to manually write the or create the automation so certainly we saw on how a
Nagendra
Model-based testing approach is being used to build a application functionality are not present efficient behavior in the tool and generate the automation scripts in
Nagendra
The next maybe couple of minutes we are going to go through on how these scripts are getting important onto the automation platform and how
Nagendra
Scenes as the execution is and what you now is the talos screen which is our head service automation platform across all the multiple channels
Nagendra
Now it's a simple as connecting to a given project wherein one has to look at the channel against which I have to do and
Nagendra
Import the automation scripts which has been exported by the automation model-based testing tool and you will be able to see the screen where the
Nagendra
Impact analysis what you saw saying that okay so that new test data for the first time that impact analysis is passed or inherited even
Nagendra
Onto the Talos platform now the activity that will be done for execution is as simple as going to even test case and in this
Nagendra
Case I need to now execute it on the device that's what we actually have brittleness integration with our partners platform Chloe when I will
Nagendra
Be able to seamlessly go connect to the platform I would have to log in where my Liberty choose the kind of devices I have
Nagendra
And then start the execution so what you are seeing is a seamless execution of the functionality wherein there is no effort that has gone
Nagendra
In building the automation stuff manually automation scripts are getting generated directly from the model we were connected now this is what you saw for
Nagendra
One channel and it also has automation reporting from Sharkey the chili was restricted to go and look into further details about the failure or
Nagendra
Any of the screenshots again the process is very simple you import the scripts for the different challenge in this case we're importing for a
Nagendra
Know very well where you want to execute it on a iOS device right I choose a platform and then I go then to your
Nagendra
The execution and this goes on even for any of the cross-browser testing and for all social testing again we will be able to trigger
Nagendra
The concurrent execution wherein I will be able to choose different versions of the browsers different types of browsers and trigger it on multiple virtual
Nagendra
Machines on the cloud right so I will be able to achieve a seamless automation between his design execution and reporting right so that's pretty
Nagendra
Much I had probably a minute or so which is explaining in terms of the process even for the browser press devices wherein you will
Nagendra
Be able to see in terms of how we connect even for the desktop based browsers and this is again a platform by our partner
Nagendra
Called aki proud wherein I will be able to configure the connectivity between my automation platform and then connect on the cloud and there's something
Nagendra
Which we can do it for any of the customer platform and what you have done is there are cases where you have built the
Nagendra
Similar kind of connectors for our customer automation trail words invariably either customers would have their own automation framework or they would expect us to
Nagendra
Bring in our framework whenever we have an option to bring in our framework we leverage or tano's wherever customer has already invested in doing
Nagendra
Having an automation framework we build the connector which enables the seamless automation from design execution until reporting right so this pretty much we talked
Nagendra
About in terms of what the solution is where and how we are able to achieve multi-channel automation for
Nagendra
Using multi Chong automation using a model dress testing approach and the integration of the modulus testing tool with a multi-channel automation framework right so
Nagendra
With this fan bang I would now hand it over to my friend Ganesh we talked you through the platform pqe platform in little more
Nagendra
Detail 14
Nilesh
Thanks Megan drew for such a wonderful demonstration I'm pretty sure the attendees will get benefited out of this I will come all
Nilesh
Again once again and we will move on to the
Nilesh
Worthy of Pcloudy right so we'll quickly see what exactly we do at Victoria who we are so we are actually commonly known as
Nilesh
Smart software testing solutions basically known as SSDs as a short form we are a complete product based company and focusing our products on creating
Nilesh
The testing platforms so as nagaina was mentioned we have two products in our portfolio Pcloudy and aapki he has demonstrated both the things
Nilesh
In the presentation there we have 50,000 plus registered users registered on this platform recently we have 500 plus customers across the globe and when
Nilesh
I say 500 plus customers these are the customers who are you know renewing their subscription on month on month basis we have 80 plus
Nilesh
Employee strengthened which is growing day by day and we have three locations across the globe wherever data centers are located so India US and
Nilesh
Australia couple of quick recognitions and credentials at Pcloudy so I'm proud to say that you know Pcloudy is covered by Gartner in
Nilesh
One of their report in 2016-17 on market kite for mobile test automation and tools we have three provisional patents with us right now we
Nilesh
Are also but covered in g2 crowd platform we have customers from 84 different countries so it's a global platform as such and 200,000 plus
Nilesh
Hours of device testing is done on this particular platform to make it pretty rigid and tested by the customers so quickly we will see
Nilesh
What are the pain points we are actually trying to address using Pcloudy there are so many pain points but the key pain points
Nilesh
Which we have mentioned it here first and the foremost is the device infrastructure so we know that in today's mobility testing devices plays a
Nilesh
Big role right and we when we have the biggest landscape of Android and the iOS devices iOS device landscape is also growing day by
Nilesh
Day so we have to have a real physical devices spread across different geographies there may be different ways and hardware software configurations right so
Nilesh
We provide that using Pcloudy we will provide you both Android iOS devices different ways versions different hardware configurations at a single cloud the
Nilesh
Second point which we have often seen is the distributed teams you know with the current situation we have distributed teams testing team sitting maybe
Nilesh
From different geographies so if you want to give them the devices the physical real devices to test their mobile applications either we will have
Nilesh
To have a redundant devices or you will have to have certain devices with one team and certain devices with other team so collaboration between
Nilesh
The teams is a biggest challenge there because if you have a redundant devices then obviously the expense on the devices is too high if
Nilesh
You don't have redundant devices then if the team finds one certain defect by team one may not be reproduced by team two because they
Nilesh
Don't have the right set of devices of the same device which on which the device the defect was found so Pcloudy provides you
Nilesh
The access to the to your distributed teams by remotely connecting to the cloud and accessing the device remotely our emphasis is more on you
Nilesh
Know maximizing the automation and that's what the entire industry is trying to achieve the previous demonstration is also for the same thing so we
Nilesh
Can actually use Pcloudy to maximize your test automation be it for automation test creation or even for the test execution when we say
Nilesh
Test execution so we typically save whole lot of test execution time because we have a capability to execute your test automation on multiple devices
Nilesh
Parallely in order to save your total execution time and we in return to that we provide you whole lot of artifacts which will be
Nilesh
Pretty much helpful for you to you know analyze the reports so we are going to see that in a while brief about that the
Nilesh
Third one and the last one which we were talking about is the
Nilesh
This is this particular platform fits absolutely in your existing DevOps environment you know just to reduce your dev and test feedback loop so if
Nilesh
You are using already an environment where you are doing continuous deployment continuous testing you know you can use Pcloudy to execute your test
Nilesh
Automations on nightly builds all in the continuous integration testing more on the physical devices so Pcloudy will provide you the access of real
Nilesh
Physical devices remotely so let's quickly see the introduction of Pcloudy what we are what we are actually providing you through Pcloudy so
Nilesh
On ground Pcloudy is basically a mobile device cloud based platform right you can we will provide you the physical devices remotely for both
Nilesh
Android and iOS platform now what what are all applications you can test on this particular platform so you can test native applications you can
Nilesh
Test hybrid applications you can use mobile web applications to test and also you can use PW applications which is what the latest market trends
Nilesh
Are so all these applications you can test on Pcloudy devices what what what are all things you get it at Pcloudy when
Nilesh
You test this application whatever things you can do with this applications so first and foremost we provide is the device analytics right what kind
Nilesh
Of device analytics we are providing it to you will see in a subsequent slides the second thing which we can do with this platform
Nilesh
Is of course the manual testing though we are moving to your test automation but manual testing also plays a very big role so manual
Nilesh
Testing we cannot avoid so we provide the access to manual testing and you can do whole run off manual testing say in the same
Nilesh
Way as you can do with the phone in hand the third thing we provide is the test automation execution so basically we can we
Nilesh
Provide you both this automation creation and test automation execution and it's all parallel execution the last thing in this platform which we provide is
Nilesh
The infield UX testing typically the crowd testing and this is what we recommend to most of our customers say you know this is a
Nilesh
Primary case you know it's a prime importance because you get the feedback even before you launch your application in the market from the real
Nilesh
Users in the market so this is a one-stop solution where you can do all these things and you can get benefited out of this
Nilesh
Okay so this platform as it's a remote device cloud platform so you can actually access the platform through the web portals you can use
Nilesh
Any standard web browser and you can use this platform to do the to perform all the tasks which I have explained at the same
Nilesh
Time you can also access this platform using certain plugins which we have for Android studio Xcode and Jenkins basically this platform is not restricted
Nilesh
Only for the test engineers but it can also be used by the
Nilesh
Development teams right now let's see what offerings which we have at this platform so we have three offerings the first and foremost is public
Nilesh
Cloud so this is basically the cloud where we have so many devices the devices will be shared across different users one at a time
Nilesh
So the capabilities for public cloud is we have 500 plus real devices which is with the widest variety of devices available on this cloud
Nilesh
We do have devices with real operators same so in case you want to test your application with a real network with the real cellular
Nilesh
Networks you can actually use these devices to test your applications with and we have three different locations so we have our data centers located
Nilesh
In India US and Australia so basically you can use the devices from any location to test your application the second offering which we have
Nilesh
Is called private cloud as the name indicates here private cloud is absolutely private to a specific client we have seen cases where you know
Nilesh
Some of the clients they say they do not want to use the shared devices they want a dedicated device cloud they want the cloud
Nilesh
Access 24 by 7 so for such kind of cases what we do is we create an instance of the cloud which will be maintained
Nilesh
By us in our own state-of-the-art data centers and we provide the list of we provide the devices which is asked by the specific user
Nilesh
A specific client so that particular cloud with a separate dedicated URL will be accessed only by a specific client and the whole user management
Nilesh
Will be done by them so it basically it's a private cloud for that particular client alone the third offering which we have is on-premise
Nilesh
Cloud now this is further extension of private cloud at times we have seen the clans from different domains like banking your insurer insurance our
Nilesh
Rittle are even you know from the healthcare they do not want their application to go outside their premises neither they want their applications to
Nilesh
Go outside their premises now they want the devices to be you know available outside their premises they want everything within their premises they want
Nilesh
To do the testing entire testing is in their premises but they might have be having certain vendors outside who are doing their testing or
Nilesh
Their application their test engineering teams are sitting outside their premises so for such clients we actually set up a cloud we come up with
Nilesh
Our own infrastructure there and we set up that device cloud within their premises behind their firewall and to which the Klan's can you know
Nilesh
Plug in the devices which they have already invested on and create a mobile cloud like Pcloudy which can be accessed remotely by their
Nilesh
Test engineers so these are the three primary offerings which we have in a nutshell this is what Pcloudy does and the offerings are
Nilesh
Now we will quickly see what are all the parameters the capabilities which I was talking about one by one here so the first and
Nilesh
Foremost one is manual testing we'll see well what about manual testing so when I say manual testing you can actually do the manual testing
Nilesh
In the exact way as you can do with the phone in hand the only difference is the device is not in your hand it
Nilesh
Is on the Pcloudy server and you are remotely accessing the device apart from that you can virtually do each and everything what you
Nilesh
Can do with the phone in hand you can install the applications on the devices you can get the device logs next to the device
Nilesh
And the one of the key value at which we are providing while you are doing normal functional testing is we provide you the application
Nilesh
Performance you know in terms of CPU memory battery and data consumption so you you don't have to do much more than you just need
Nilesh
To keep concentrating on your functional testing and we provide you the application performance which will bring a lot of value to your normal existing
Nilesh
Functional testing you can also simulate different geographical locations for your location of where applications you can test within that different network simulation techniques you
Nilesh
Know now what is most of the applications are client-server applications so it is it is must that you test your applications with different network
Nilesh
Conditions you know by throttling different network capabilities of the existing network so we provide that simulation here and as Nagendra was pointing it out
Nilesh
Pcloudy is perhaps the only company right now in the market who provides cross browser testing for mobility right so you can actually test
Nilesh
Your application we are anyways providing you the variety of devices with different hardware and software configurations but but with the cross browser testing we
Nilesh
Are providing you different browsers like opera Firefox Mozilla then you see browser right like this we can provide you a whole lot of different
Nilesh
Browsers with different versions so you can test your application on different browsers and different versions we can get the capture the screenshots you can
Nilesh
Edit those screenshots you can collaborate using JIRA and Jenkins in case you are using Chi wrench in case you can straightaway raise the defects
Nilesh
In ceará or share the information using slack and the last but not the least is the follow me now this is again we have
Nilesh
A very unique offering we have something called follow me which is typically says you test your application manually on one device and it gets
Nilesh
Tested automatically on another two devices in order to save your testing efforts and expedite your testing needs moving on to the test automation so
Nilesh
As we have seen in the previous part Pcloudy is a multi-channel test automation platform you can test your application on different channels here
Nilesh
And when I say test automation basically we are helping you to execute a storage on multiple devices simultaneously right you can use your existing
Nilesh
Test test cases test suits to execute on multiple devices parallely and get whole lot of value-added services like here in this case we have
Nilesh
Mentioned session with you so if you are executing some test cases on some of the devices parallely we generate this session video so once
Nilesh
You realize that you know your test suit is failing on any of the device you can download the session video for that particular device
Nilesh
And see what went wrong right so you you're not going to miss anything apart from the reports and the logs you are also getting
Nilesh
The session video so in terms of logs we provide you all the different locks the device locks the framework generates generated logs and the
Nilesh
Error logs all those logs will be available there are a couple of platforms which we have closely integrated here which are open source frameworks
Nilesh
Like APM calabash espresso and monkey tests apart from that we have our internal automation studio which together was mentioning as an OP key which
Nilesh
Basically helps you to generate or create the test automation cases without writing a single line of code okay and on top of that we
Nilesh
Our API based system so you can actually integrate it with any of the test frameworks which we have moving on to the device and
Nilesh
Ethics part now what device analytics does here is you know if you want to test your application for a specific region let's say I
Nilesh
Have a application for UK region where I have to launch that a particular application so it makes more sense for me to test my
Nilesh
Application on the devices which are available in the UK market or UK region right so device analytics will give you the finite set of
Nilesh
Devices which is covering hundred percent of the market for that specific region so now you can prioritize your your device testing on a right
Nilesh
Set of devices and by doing so you are actually targeting the right market with the right testing efforts your testing efforts are absolutely channelized
Nilesh
And you are not doing any ad hoc testing on the ad hoc devices so device analytics is a very helpful feature here which will
Nilesh
Give you define that set of devices on which you should be testing your application so this will give you the Oh a solution what
Nilesh
Is the worst version used in a specific market what are the devices which is the VM and what kind of penetration in the market
Nilesh
The specific device is having so all that information will be pretty much useful for you when you are using device analytics feature the next
Nilesh
One is in field and UX testing so as the name suggests you know this is basically a crowd testing crowd testing in a real
Nilesh
World by the real user so we recommend that before you release your application in the market or before you upload it to Play Store
Nilesh
Our app store it should be tested by the real users in the real field it will help you to you know get the real
Nilesh
Feedback from the users before you upload it to the market so you can use Pcloudy to you know test your applications between different
Nilesh
Geographies and demographics you know you can have a specific set of Engineers from different geographies are spread across different geographies and test your application
Nilesh
In the real market the last point which we have is certified now we are calling it certifier basically it's a AI based parts which
Nilesh
We have at Pete Lowry which will help you to give you a quick health check of your application without your manual intubation as a
Nilesh
User you have to just submit your application and this bot will do the testing automatically on your application to give you a quick health
Nilesh
Check in terms of you know if there are any obvious crashes there will be some functional testing them and it will give you a
Nilesh
Lot of screenshots to make out you know whether there is some issue with the screen or any functionality at the same time we are
Nilesh
Also providing you the CPU memory battery and data consumption date data analytics and we will also give you a rating on a scale of
Nilesh
One to ten to tell you where exactly you stand as compared to the competitors in your domain right so we do the benchmarking there
Nilesh
And then test and give you those numbers so these are all the capabilities we have at Pcloudy now we have on the last
Nilesh
Slide just to you know summarize that you know if this can be used piccola we can be absolutely used in the DevOps and CI
Nilesh
Integrations we do have close integration with Jenkins would you have a plug in with that so you can use it in your CI setup
Nilesh
This can also be used by the developers we do have developer support so developers can debug their applications directly on the Xcode our Android
Nilesh
Studio for Android and iOS devices and in a true sense it's a collaborative collaborated platform you can use JIRA and slag to collaborate and
Nilesh
Share your information and raise the defect rate in your JIRA so in a true sense this is the unified this platform which can be
Nilesh
Used for your mobile application testing for both manual and automations so with this I would like to conclude today's webinar and I think we
Nilesh
Can move on to the question and answer session to take any questions we have thank you
Moderator
Thank you Nagendra analyst for the presentation that was great we will open the forum for Q&A now so please type in your questions in
Moderator
The chat in the questions window so that they can come through the platform
Moderator
All right so we have a question for I think this I believe is for you Nagendra
Moderator
So the question is how do you care take care of maintenance of manual test cases and automation scripts generated by your platform
Nagendra
Question in fact X as an effort that grows in creating something invariably time you end up spending more than what you have spent on
Nagendra
The maintenance and that's a very critical component of any anything that we build right it could be anything that we consume another customers or
Nagendra
It could make an extra mission as part of the automation now what
Nagendra
We have done is from the maintenance point of view if you have seen that impact analysis file that was generated by connector cuts for
Nagendra
The automation now what the model is testing tool does is it actually identifies the impact automatically there's no changes to the model and that
Nagendra
Impact analysis is something which it uses to categorize the test cases manual test cases in two different buckets and it's based on color coding
Nagendra
Where it will give you four different color ports one for identifying test cases which has got added unique compared to the previous version of
Nagendra
The model one for test cases which have got modified which have got probably absolutely because of the new just gives it has got added
Nagendra
Or modified and the last one is any change now what we have done is as part of our effort in building this connector for
Nagendra
Our automation framework we have built the technology that would inherit this impact analysis from the model-based testing tool on to our automation framework right
Nagendra
You have seen in Talos when I showed the video when we import the test cases you are seeing the one column we said the
Nagendra
Status and new that is where we will be able to identify what is the impact on the scripts as well and only take up
Nagendra
Those automation scripts for changes the impact and thank you
Moderator
Thanks thank Nagendra we have another question this one is for I would think the leash so the question is is Pcloudy having record
Moderator
Playback type automation built in
Nilesh
Yeah thanks yeah so we do have a record and playback feature in through automation studio so I was talking
Nilesh
About the automation studio so we have a feature in which you can actually record your specific workflow for your application and that gets recorded
Nilesh
And convert that recording as a part of test case and you can execute that discus using automation studio npcloud ii devices are on your
Nilesh
Locally versus if you have any we also have a facility to you know export that recording as a part of Java code and integrate
Nilesh
It with your local APM setup I hope that answered that question
Moderator
Yeah thanks delish the next question is it might be for both Mahindra in the leash but I'll pose it anyway the question is please
Moderator
Elaborate potential connection points to and from HP Ln UFT so maybe it might pertain to both the framework and Pcloudy
Nagendra
So when it comes to integration with the test management 231 there are multiple levels at which the integration happens to be one is at
Nagendra
The upstream varying requirement tools are being integrated with the model the system tool and the second is where the output of the model-based testing
Nagendra
Tool are even other automation scripts that we generate he is integrated with the s9 in tubes and in this case the question was around
Nagendra
HP so we have built in the utility which exports the test results from the Talos on to the HP ALM and similarly the model-based
Nagendra
Testing tool also has the out of the box plugin that actually enables us to export the manual test cases it has generated to the
Nagendra
HP ALM write the serve on the test management side certain parties on this your teeth now what you have seen is the Talos which
Nagendra
Is built on the open source tool underlying engineering on which this automation platform runs is selenium and happy and similarly we have the autumn
Nagendra
In return for your P equal task EFT exhibited and
Nagendra
You also have a corresponding connector for the new FK actuator from the model-based testing tool so that way this concept of the connector is
Nagendra
Something which can be extended to different automation tools primarily on the automation framework or the aggregator that would invariably be built on top of
Nagendra
The given automation to right could you PHP way of T or it could be for s complete or any other tool for that matter
Nagendra
Tonight that's a concept that we had it's need two different tools and today we have customers who use even the connectors for here as
Nagendra
Well as together yes
Nilesh
So coming to the Pcloudy part we do not have the you know out-of-the-box integration with any of the ALM
Nilesh
Tool as such but the beauty with this platform is we do have api's so in case somebody wants to you know integrate it with
Nilesh
Any specific ALM tool we can do that easily though we are thinking of having one or two pre-integrated things here right now and coming
Nilesh
To the different tools like UFT our other tools so those tools you can use you know to execute your test cases on Pcloudy
Nilesh
Devices we have a feature called device tool with which you can connect the device virtually to your local system to a virtual USB and
Nilesh
Then the way you are using that particular tool to execute your testing on device connected to your local system can be executed in the
Nilesh
Same fashion
Moderator
Thanks thanks Linda there's a question I believe for noggins this is do you need Mac OS for automating iOS device related test
Moderator
Cases creating the automation sniff the second one is in terms of the excitation of the automation spec
Nagendra
Now for the creation of automation per
Nagendra
Se there is no dependency Mac OS given for execution right until unless we will have to execute this test case or an automation script
Nagendra
Physically on the device connected to the machine instead of doing it remotely on a platform like a glory only in those instances one we
Nagendra
Have to actually use a Mac because Apple doesn't allow to connect to any other OS then Mac if you are using any platform like
Nagendra
A cloudy or any other cloud-based mobile device platform there is no necessity of hiding the Mac as a
Moderator
All right thanks Nagendra there's another question this one might be for Nilesh so the question is can Pcloudy be integrated with similar such
Moderator
Frameworks a similar such frameworks means the one which Nagendra has presented it was the question
Nilesh
Yes yeah so as I was pointing it out
Nilesh
Even earlier that you know we have Pcloudy is absolutely API based platform so we can integrate it with many such frameworks
Nilesh
Yeah I mean lot of clients are using their own frameworks also and we have done with those frameworks
Nilesh
Another have used to develop the script supporting the chat pod and
Nilesh
Our specific platforms including from Google that we use so for our my teach and testify to be in mobile and will be is there
Nilesh
This one we use selenium and IBM
Moderator
Okay okay thanks Nagendra we'll probably take a couple more questions so let's see there's one more question
Moderator
I believe it says are you leveraging a I've on the Pcloudy platform
Nilesh
Yeah yeah thanks Carrie yeah so we do leverage the AI what testing on the peek-a-ru platform as I was mentioning we have our software
Nilesh
Bots backed with the artificial intelligence and machine learning capabilities so these bots are evolving day by day and you know you you have to
Nilesh
Just upload your application to these parts and because we are using AI based parts and the which has machine learning capability so it will
Nilesh
Learn for every different applications different domains different verticals and then it will try to figure it out how many screens your application has what
Nilesh
Are the typical workflows your application has and do the testing on those applications and give you the quick results so yeah in short we
Nilesh
We are leveraging the area for our BOTS
Moderator
All right thanks de leche
Moderator
And believe this might be our last question for the day I guess the question is yep for the multi-channel testing what are the tools
Moderator
Do I need I mean do I need to have additional tools I guess that's the question
Nagendra
Of predominant today against which 80% of the work goes either application test probably based or a mobile or tablet
Nagendra
So for that there are two parts first part is money as part of the testing you need the physical devices right against which you
Nagendra
Do the testing that's where we encourage our customers to leverage a cloud-based platform like Yoda primarily because the headache of maintenance as well as
Nagendra
Procuring the devices would be actually passed on to partner who is exporting those things second is in terms of when we look at from
Nagendra
A automation point of view again it all depends on in terms of whether we are looking at automation or regression testing or whether automation
Nagendra
For regression testing difference for the recognition but either only the tools would be the ones which are the market like selenium open-source like a
Nagendra
Peer or commercial to the ERP our test complete our task of complacent ease right so
Nagendra
Execution automation automation for Monica charm testing and also extend that is there not a mission even for generating the automation script that's when we
Nagendra
Actually bring in model-based testing tools which has the capability of not just that we generate in the manual test case but also that inherent
Nagendra
In will be poor so extended even for automation in the form of connectors
Moderator
All right thanks now Kendra I think that's all we have time for today there are quite a few more questions which we will respond
Moderator
To individually through email thank you know again learn English for the webinar Thank You audience you've been great with some interesting questions and hope
Moderator
Use see you soon for our next webinar series thank you and have a good day good night
