Dinakar
Hello and hello everyone and welcome to yet another exciting webinar from the change leader series Break Free uh today we will be looking at
Dinakar
Why and how to build a test platform the new realism my name is Danica and I'll be the host for today before we get
Dinakar
Started I would like to go to a few housekeeping rules your line is currently muted however you can submit your questions during the webinar
Dinakar
Through the chat option at the bottom of the screen we will answer your questions as part of the Q a session at the end
Dinakar
Of the webinar please note that this webinar is being recorded and we will send out the link of the recording to share with your
Dinakar
Colleagues later with that said let me quickly share a bit about the series
Dinakar
Now Break Free was an idea that birthed out of the need for change in the testing domain we have seen the testing industry evolve
Dinakar
Over the decades as a few change leaders took the risk and embraced change however we believe that this change can be accelerated at a
Dinakar
Much faster pace and so we took the liberty of identifying and inviting a few change leaders who are breaking the mold and embracing change
Dinakar
To see the QA industry evolve and that became what is now Break Free a change leader series you know our hope is that these
Dinakar
Sessions would spark ideas in each of you to be the change in the QA industry for the better and with that let me welcome
Dinakar
Our change leader for today asmita is the head of QE Consulting and advisory team for USD product engineering she carries over 17 plus years
Dinakar
Of Rich experience in the quality engineering domain she's uh she believes in continuous learning and loves to build new capabilities to boost the quality
Dinakar
And functionality of products for customers customers she takes much pride in her team and enjoys collaborating and trading knowledge perspective and experiences that each
Dinakar
One of our team members brings to the table apart from her day-to-day work at USD she enjoys exploring her creative site and has a
Dinakar
Good-handed creating miniatures most of our weekends go into spending quality time with doing different crafts with her daughter now without further Ado let me
Asmita
Hand it over to our speaker asmita thank you thank you dinakar uh appreciate you know the introduction that you did and also uh this
Asmita
Entire initiative this is especially this community initiative by clip Pcloudy and you know I'm glad to be contributing to it as well uh
Asmita
So good afternoon everyone and happy navratri and thank you for joining this session with me here today so my intention for today is to
Asmita
Cover uh basically you know why uh do we need test platform what is a test platform um and how do we uh you know
Asmita
Build a test platform uh also you know via this test platform how can we achieve you know the objectives like digital happiness or you
Asmita
Know being responsive to business as well as you know having this all at speed for our customers basically right uh we'll take a look
Asmita
At you know quickly at the holistic testing as well as you know what does the test platform look like um I would you know
Asmita
Definitely look forward to this session uh you know acting as a string board for each one of you so that you know you can
Asmita
Have good enough takeaways go back and discuss with your teams as well as organizations and you know implement it as well all right so
Asmita
Let's uh you know move on to the next slide so uh you know with uh you know uh basically you know just to set
Asmita
The context right uh I'm sure you know in uh in the recent times you have uh you must have definitely you know realized that
Asmita
Acceleration in quality engineering is visible right we are transforming from being an independent function to being now an integral as well as an inclusive
Asmita
Part of the entire software delivery team right and our responsibilities are Beyond just testing these days or finding bugs we are now in charge
Asmita
Of enabling the entire team right to be uh to in order to achieve their quality objectives bring in the best best practices across the
Asmita
Cycle as well as you know bringing in the modern techniques to achieve the same right so in this talk uh I would be you
Asmita
Know covering what are the primary objectives of testing as perceived especially you know by our stakeholders
Asmita
So that you know we end up focusing on you know what really matters right so uh for this a particular uh section right what
Asmita
I would do is I would be basing the entire context on uh the 13th edition of world quality report uh so so you know
Asmita
Let me you know before I move on right I would just quickly like to take a pause and you know hear from you how
Asmita
Many of you you know have heard uh about a world quality report or you know consumed it and feel free to you know type
Asmita
It in the chat as well I'll be able to however you know I think uh if yes like if your answer is yes uh
Asmita
You know I'm not able to see the chat however if your answer is yes and I'm glad that you know um we are as a
Asmita
Community consuming this report however you know if you haven't I would you know definitely recommend that you make it a calendar event to you
Asmita
Know go through this report uh every year and you know chalk out uh what are the key takeaways for you as well as for
Asmita
Your team and your organization all right so with this you know let's take a look at um uh you know basically what is it
Asmita
That we need to you know look for so um 63 of the respondents so basically you know in this report what uh how you
Asmita
Know capgemini or how they you know encounter they take this uh report ahead is they uh you know they go ahead and meet all
Asmita
Cios they have their own questionnaire and with that survey they come up with their own intelligence so uh 63 of the respondents said that
Asmita
Enhancing the end-to-end customer experience is one of the most important factors of their test IIT test it strategy rather all right so as I
Asmita
Said right agile and devops is you know continuing they're they're their adoption is definitely continuing and with this there is an increased attention given
Asmita
To QE right um so so let's see you know with respect to this ask of our cios that you know we need to enhance the
Asmita
End-to-end customer experience what is it that you know we can look for
Asmita
So organizations definitely you know are Keen uh to achieve the digital transformation right um and in this right in order to you know stress more
Asmita
Upon digital transformation I would like to you know particularly quote um one of the statements from a Gartner research that was published recently that
Asmita
Never like for especially in context you know digital transformation never consider digital to be the outcome right so for example you know if I
Asmita
Take an example that you know we if we have a e-commerce website and say we you know enable that website you know by a
Asmita
Cloud transformation or you know we take it to Cloud right so the emphasis is not that you know we have now taken the website
Asmita
Or the entire uh you know ecosystem to Cloud but the emphasis is on benefit with respect to you know the efficiency flexibility and the
Asmita
Entire customer experience that we have enhanced with this move and customer experience if I have to you know elaborate on it it will be
Asmita
More around what is the customer satisfaction level what is the joy every visitor experiences when they you know come to our website as well
Asmita
As applications because you know with so much of competition around right customer experience is the battlefield for all the brands right so with respect
Asmita
To that how is it that you know as uh you know as a QE team we can uh you know contribute to right so
Asmita
A you know adherence to the functional requirements so basically you know uh ensuring that you know what we are promising to our customers or
Asmita
What uh the domain demands uh so having you know completely domain-centric approach and adhering to the functional requirements is you know one of the
Asmita
Objectives or key objectives that we as QV team will have to fulfill we'll have to also test and assure an omni Channel experience so
Asmita
If you uh you know just you know imagine these days you know at times we shop from our mobiles we can we then also
Asmita
Continue say you know shopping from web over our laptops Etc and we expect to you know continue from where we left right so ensuring
Asmita
An omni Channel experience and keeping that in mind when we test right is again going to be you know one of the key asks
Asmita
Uh or a key consideration that we as a community will have to keep in mind the third thing is usability because a you know
Asmita
Adhering to functional requirements definitely is easy because you know there is a requirement written all we'll have to do is understand the requirement and
Asmita
Ensure you know the application uh you know is in line with it or not however usability is a lot beyond that right usability is
Asmita
That you know what is it that the consumer expects right uh while adhering to the functionality but what is what is the ease that
Asmita
The consumer expects what is the journey that the consumer would be taking so entire product side of it and this is again you know
Asmita
A good area of upskilling that you know we all as a QV Community can have that you know how we can you know think
Asmita
About usability uh so that you know we can not only raise defects uh which are non-confirming to the functionality but we can do also
Asmita
Raise suggestions and recommendations to make our applications better right and also from the while these are you know more around the functionality and the
Asmita
Functional side of it from the non-functional side of it how is it you know that we can you know focus on the end user
Asmita
Performance how our websites are loading uh you know how how is the entire like you know are we are there any compliance needs by
Asmita
Our applications are we you know making our applications accessible as well as inclusive can uh can I have a specially able to you know
Asmita
Um user of mine still use the application as seamlessly you know as any other customer right so how do we bring in the digital
Asmita
Inclusion uh so these are also some aspects that you know we as the QE Community can look into all right so let's move on
Asmita
To the next uh requirement so with respect to business Assurance right 61 percent of uh the respondents said that being responsive to business demands
Asmita
Is another you know important factor in their I.T strategy right whenever they are designing any product or any ecosystem right so with respect to
Asmita
This right um what is it that we can look for in any application so for example if we at times you know what happens
Asmita
Is when we test our applications we test for today right uh but what happens if tomorrow like you know we see on uh you
Asmita
Know there's this big festival fashion Festival going on or if you know uh say you know come tomorrow Thanksgiving and there are sales coming
Asmita
On so are we real are we ready or are we you know have do we have applications which are ready to scale scale up
Asmita
Scale out I mean there are so many you know methods in which this can be designed but how is it that you know are
Asmita
They you know on the go really scaling up uh also you know what happens one year down the line is the design flexible enough
Asmita
You know to help us to take our applications ahead right so from that perspective scalability is going to pay play a very uh in
Asmita
A crucial role um in order to in order to you know from the future perspective similarly you know one thing is about scaling however
Asmita
You know uh with respect to our products and applications right every second equates to revenue right it's it's you know well there must be
Asmita
So many statistics that you know you all must have read that you know one second of downtime can cost the organizations a lot of
Asmita
Money so with respect to that how resilient are our applications how available are our applications is something that we'll have to think about ask
Asmita
Questions um and also at the end of the day test them security another is definitely because you know while this is a part of a
Asmita
Consumer customer experience as well uh again from the business perspective of our reputation perspective uh the brand perspective these are the security is again
Asmita
You know a key aspect uh it it has now you know started to become a differentiator within the brands uh it is important to
Asmita
You know assure our consumers that you know your data is safe and that we value your privacy right so um so this basically is
Asmita
You know what um is you know that we can look for uh with respect to being business uh irresponsive to basically you know uh
Asmita
Business demands now moving on right uh uh 61 percent like time to Market if is you know another key because you know again with
Asmita
The competition right so 61 percent of the respondents say that quality at speed um basically is again one of the primary goals of a
Asmita
Quality assurance in any organization right and to drive this point home right let me um you know quickly take a look um uh or
Asmita
Rather you know quote uh so there's a there's a good quote you know that I came across in the same Depot uh by Mr
Asmita
Brandy uh Fritz Patrick so he's the VP with the Fifth Third Bank and you know he says and I'm sure you know it will
Asmita
Resonate with you with each one of you that uh just in our daily lives right where we want and expect next day or at
Asmita
Times you know a same day you know order fulfillment right be it with respect to food um and any other materialistic aspect right similarly
Asmita
In business people want their code to be delivered immediately and that has to be good to go right so it means that you know
Asmita
The delivery or the code delivery as well as you know the quality has to be at speed right so from that uh perspective right
Asmita
What is it that we can you know improvise on so we can definitely you know bring in process optimization and by that this you
Asmita
Know I'm not uh going to get into say you know the Matrix and all however you know um like you know what we test
Asmita
Right rather than testing uh you know everything and anything and at times at two Atomic level can we test you know what is valuable
Asmita
We'll definitely have to bring in automation because uh you know it's not possible like you know we have the entire devops pipeline but QB
Asmita
Stays manual right so we'll have to definitely automate and by automation uh you know I have specifically not written test automation because it's not
Asmita
Only about automating your functional require a functional side of testing but how we can automate you know the entire non-functional side of it and
Asmita
Everything that we do what is it uh that we can do to you know digitize is and also you know with quality and automating
Asmita
You know what's valuable rather than you know again as I said anything and everything right and definitely you know the industry is Keen uh
Asmita
For automation uh but what is also important is they they would want uh we can you know definitely take an intelligent approach as well
Asmita
With the you know amount of data that we are churning out as a part of testing
Asmita
We can certainly bring in a lot of you know analytics uh that can help us in predictions that can that can help us to
Asmita
You know draw actionable insights so that the analysis itself is a automated and secondly we can take some you know quick actions all right
Asmita
So I hope uh you know you're with me so you know before I move on right to the next section where we discuss uh
Asmita
Basically you know that what is you know a test platform and how you know Break by break we can build it uh I would
Asmita
Like each one of you to you know think over the significance of these numbers that I showcased right so we saw that you know
Asmita
63 of the respondents said about the customer a customer experience similarly 60 percent around said that you know this being responsive to business demand
Asmita
And over here also you know we see that 61 percent you know say that quality of speed is important so you know just you
Asmita
Know as basically you know as we are traversing through the digital transformation and as it is gaining momentum what I would want to highlight
Asmita
Via these numbers is that you know each of this Factor you know is you know basically weighing or you know carrying the same weightage
Asmita
To these cios so you know which means that there is nothing less important or more important we'll have to concentrate and we'll have to
Asmita
You know as a team ensure that you know each and every factor of you know the expectations is delivered all right so basically let's
Asmita
You know see everything in similar light and move on so um so so much you know for this section for sure right so let's
Asmita
You know quickly move on so this basically you know is our um stlc uh quickly you know if I you know I would not
Asmita
Much dwell into the sdlc but you know uh I think a cycle that you know any product goes to whether there is requirements the
Asmita
Developers developing at their end and then you know we bring all the blocks together and build uh the ecosystem take it to staging and
Asmita
Then you know the production right so from this perspective right let me ask you a question and again you know you can feel free
Asmita
Um to drop your comments in the uh you know chat box so where do you think you know the test team should get involved
Asmita
Where is it that you know you would want the test team uh or where is it that you feel that the you know test
Asmita
Team should get involved so uh you know just so that you know I don't delay this discussion so quickly you know in fact the
Asmita
Quality begins right for from requirements uh phase in fact you know uh um they say that you know it's it begins right from the
Asmita
Vision itself of the product where you know there is a lot of research done and which you know in turn maybe you know we
Asmita
It's not that the quality team does it but you know there is a lot um of you know background work that happens uh you
Asmita
Know which you know can help us and lead to good products right so with respect to this right let's take a look at you
Asmita
Know how the code progresses and how we can you know um contribute to testing right
Asmita
So while you know uh as the you know Sprint moves on as the developers you know uh if I take you know view of
Asmita
One Sprint at a time and as a developer works on his or her you know user story right so functional testing is inevitable right
Asmita
So we'll have to you know with uh you know taking each user story if I take it as a break we'll have to ensure
Asmita
That you know we perform functional testing because you know if we if I just correlate it with the context setting that we did it
Asmita
Directly equates to you know um one of the important factors towards the customer experience right and if I have to cater to the third
Asmita
Uh factor which is quality at speed that's where you know the test automation comes into picture right so let's dwell into detail that you
Asmita
Know if it is about test automation then what are our key considerations what is it that you know we have to keep in mind
Asmita
Uh that it's not just you know you take selenium selected language and just you know run with it right there are a lot of
Asmita
Consideration a lot of Designing that we'll have to do so first of all you know um uh you know one of the consideration and
Asmita
One of the key consideration which is one of the foundation uh towards any test automation approach is something that is you know let's be
Asmita
Technology uh agnostic and rather you know rather than technology or agnostic let's cater to all Technologies but also be on way to you know
Asmita
Put forward this point so with this you know what I mean is um when you design your Frameworks have the flexibility while either selecting
Asmita
The tool or the library or you know the basis of which your test automation is going to be and let's ensure that you know
Asmita
We take a language agnostic you know approach we can you know definitely build a framework in say in a particular language or be ready
Asmita
For tomorrow and build it in multiple languages so that you know we talk in the language same as the developer and the test automation
Asmita
Adds to the value right one of the other one of the important pointers we saw when we were discussing customer experience was Omni Channel
Asmita
Channel Assurance right the experience only Channel experience would be you know seamless right so from that perspective as well your test automation will have
Asmita
To cater to the API layer the web layer the mobile layer and if at all any if there is any thick client so it
Asmita
It has to be in a single project uh these components have to talk to each other so that when you when you design and
Asmita
Automate end-to-end scenarios these uh you know building blocks can talk to each other and you can navigate VIA your application as well um via automation
Asmita
All right so let's ensure we have multi-linguistic as well as you know multi-tier approach
Asmita
Second thing is you know uh one thing you know that I would like to highlight is uh you know uh it as the saying
Asmita
Goes right doing things right is you know what we are doing but uh doing right things sorry is what we are doing but you
Asmita
Know we'll have to also do uh you know things right so you know I will so that's where you know a right test automation
Asmita
Strategy and basically overall you know the strategy is going to um you know play a key role wherein you know it's going to be
Asmita
Very important that um as I had mentioned let's automate what is valuable so what uh what is it that we are automating um what
Asmita
Is it you know uh taking care of only today or you know we are thinking ahead of the time and accordingly design that designing
Asmita
The test scenarios are we considering the user experience or the journeys which the customer would or consumers would take an accordingly designing our workflows
Asmita
Is again you know going to be uh important right uh similarly you know uh and definitely I think you know organizations these days are
Asmita
Here really Keen towards test approach but what the demand says is that they would also you know want for a smart approach uh otherwise
Asmita
You know the then you know the there is no end to the workload when it comes to test automation so what's going to be
Asmita
Also important is uh that you know we apply a smart approach towards it uh test data uh definitely is you know going to play
Asmita
A crucial role in any desktop automation Venture because um your automation has to be you know flexible enough to work on multiple uh environments
Asmita
It has to be you know you will have to design independent tests and self-sufficient tests um of course you know there are many strategies
Asmita
Available within the test data space you can generate your own data you can you know take the production data mask it or you know
Asmita
Generate synthetic data I think you know and to each uh their own right you know whatever is the strategy that you know um supports
Asmita
Our ecosystem I would recommend you know let's go ahead with it however over this has to be one of the as long as it's
Asmita
A key consideration and you're designing your automation considering this pointer uh I think you know we should be uh well you know taken care
Asmita
Of from the future perspective also why you know another reason why test data is you know going to be important is uh so that
Asmita
You know you don't run your tests with the same data because it's uh you know it's as they say the pested side a paradox
Asmita
Right if you test your application with the same data again and again there are chances that you know we may miss out on a
Asmita
Certain defects because we didn't you know let the situation vary right so hence you know I would say that you know in fact concentrating
Asmita
On test data and having a strategy around it is going to play a very uh key role uh as I said right analytics especially
Asmita
You know from actionable insights perspective is going to be the key because as people are adopting test automation they would also want it to
Asmita
Become intelligent and uh comprehensive right so from here so whenever you execute tester automation right there is so much of data that it gathers
Asmita
Um for each run that we perform right so what are the analytics you know like can can I quickly because you know I'm sure
Asmita
The Estates out here would you know resonate with me that uh there's a lot of time that we spend on analyzing you know each
Asmita
And every report that we get each and every result that we get right so how is it that you know I can say inner
Asmita
View get all the failures that we have uh how can we uh how can we you know predict that you know uh quickly you
Asmita
Know from with respect to is it you know my script that is an issue or is this uh you know an application issue because
Asmita
You know these are the aspects where a lot of time uh a manual on manual intervention is needed right so how can we you
Asmita
Know reduce on this um again you know uh as they say right if we don't leverage test automation it'll be just you know your
Asmita
Porsche part and uh the parking right so how do we you know so it's going to be very important that we not only automate
Asmita
But leverage our tests so from that perspective execution plays the key role so you can you know definitely execute on cloud and leverage you
Asmita
Know Solutions like pre-claude exit on uh so that you know we can quickly execute On Demand on you know whichever platform or uh you
Asmita
Know browser or any other configuration that we want and you know get our results similarly for in-house you can definitely you know leverage Solutions
Asmita
Such as Docker um you know you can design the containers uh that you want or images that you want and um you know quickly
Asmita
Spin up what uh you know the uh Docker images and move on and you know execute so that you know basically the intent is
Asmita
Leveraging our scripts as much you know as possible and also with respect to leveraging AI right so uh the report specifically mentioned right that
Asmita
The uh AI you know as we say is not in future it is very much here and now especially in the QE perspective as
Asmita
Well so how we can you know um and of course you know it's maturing so I'm not going to um say that you know
Asmita
We are there and uh so there's a lot of improvisations that still you know are in on the way and could be done however
Asmita
You know what whatever is available in the industry right let's start adopting it so let's you know learn you know how we can you
Asmita
Know say for example to begin with have self-healing in our test automation so that you know uh the test coverage that we are assuring
Asmita
How it can you know still be um you know uh conserved there are so many use cases within the entire or across QE as well
Asmita
You know that are coming up like say as simple as optimizing our regression suits because as you know the time moves on right our
Asmita
Regression suit keeps 5 filing up so how you can you know have Smart methodologies you know applied or smart you know techniques applied here
Asmita
So that you can you know get a concise uh you know list of what is it that I need to test my application on
Asmita
And take this quick decisions and that's where you know definitely AI is going to um you know help us
Asmita
So while this is you know about test Automation and what considerations we need to take let's move on and quickly check you know so
Asmita
This is you know part of the you know shift left side of it right so let's quickly take a look at you know once
Asmita
You know the codes is ready and we have progressed right and start integrating uh the applications what is it that you know we'll have
Asmita
To take care of so uh so regression definitely you know is a key you know as we bring different blocks Together made by you
Asmita
Know different teams it's very important that we keep in touch with the application and ensure that you know nothing is regressed and we are
Asmita
Moving ahead and the functionalities that were you know working and are supposed to be working uh do not break right so regression um definitely
Asmita
Again you know either via functional as well as from the test automation perspective has to continue uh performance engineering mandatory you know in fact
Asmita
You know performance engineering has to shift left so it has to begin um when you know the developers you know start building the components
Asmita
But if not then at least you know in the integration perspective it has to be one of the key aspects that we account for
Asmita
So from that perspective of course you know there are so many tools available uh these days open source Solutions like you know jmeter k6
Asmita
Or Locust depending upon the ecosystem that we have right depending upon the technology the uh the nature of the application the domain the user
Asmita
Base that we cater to right uh there are going to be a lot of deciding factors that would lead us to choosing the tool
Asmita
However you know having the right approach is going to be the key right so a few pointers around performance engineering that you know I
Asmita
Would like to highlight is basically let's you know monitor that are we designing developing testing and monitoring for performance right and especially uh you
Asmita
Know if we if we take a step back and uh you know take a quick look with this pandemic right we went on to
Asmita
You know say video conferencing teleconsultation um online shopping more than you know the physical shopping right so with this we are in midst of a
Asmita
Exponential surge in you know user base and uh people you know uh going online right so there has to so there has to be
Asmita
A way basically there is a way in which um the businesses have changed uh their operating model and hence you know we'll have to
Asmita
Uh you know uh ensure that the change happens seamlessly right so we'll have to you know understand these growing needs uh anticipate and basically
Asmita
You know learn so from that perspective you know I would like to highlight that you know I'll be designing for tomorrow today and tomorrow
Asmita
Similarly from the development perspective testing and uh the monitoring side of it and will dwell more in you know into the details uh with
Asmita
Respect to scalability and responsive just as you know I had mentioned earlier that RR you know is our application you know scalable not only
Asmita
For today but for tomorrow and you know with respect to wheat you know the server side of it or the front-end side of it
Asmita
Is it you know responsive enough um to our you know needs different situations different network conditions
Asmita
Etc so there could be so many permutations within the performance space which is again where you know we'll have to wear the hat of
Asmita
Customer experience that you know what what is it or where is it that my consumer is and am I you know catering to you
Asmita
Know each and every situation or different situations that my you know consumer would be in right
Asmita
So while you know we are talking about this which is which you know we might still be in the dev or the integration uh
Asmita
You know environment uh performance engineering has a key role to play you know while in production as well uh where you know from uh
Asmita
From the production perspective testing for basically High availability and resiliency is going to be the key because this is where you know it's all
Asmita
About brand our reputation and you know in turn uh definitely you know their revenue as well right so so from that perspective uh this
Asmita
You know is called as shift right in uh testing right so and with respect to the prom delivery that is you know the bottom
Asmita
Line and expectations from each one of us shift left and right is you know very much here and something that you know will have
Asmita
To push uh going ahead for uh in order to you know cater to the speed aspect right so with this with respect to this
Asmita
Application continuous rather you know continuous application performance monitoring is going to be the key the reason why you know I'm bringing these Point points
Asmita
Up is so that you know we can go back and you know question ourselves our teams as well as the ecosystem that you know
Asmita
Where is you know our application performance monitoring are we actively doing it you know what are the tools that are useful and how we
Asmita
Can you know again leverage AI in order to anticipate you know what are the issues um that you know uh anticipate early that you
Asmita
Know what is it that can go wrong you know is my CPU mutage usage shooting up or in other memory leaks what is it
Asmita
You know that I need to cater to so that you know I don't realize these issues after the downtime but how much I how
Asmita
I can you know prevent the downtime of my application right uh these analytics especially you know when we um gather on production can help
Asmita
Us in understanding the user behaviors as well where is it that the user you know Journeys uh or you know what are the frequent
Asmita
Lanes uh that you know uh there is you know frequent user Journey taken and how is it that you know we can um either
Asmita
You know improvise it are we you know having uh customers who end the cycle with us or are they dropping and if they are
Asmita
How can we enhance the customer a customer customer experience so that you know it goes better so there are a lot of analytics that
Asmita
We can draw out of you know these uh metrics and tools as well similarly you know chaos so from resiliency perspective right so there
Asmita
Are so many uh open source uh you know Solutions uh available so chaos engineering specifically is a solution brought to us binetrics but there
Asmita
Are you know a lot of tools uh that have you know now emerged uh the Chino Enterprise or open source with respect to you
Asmita
Know assuring uh basically resiliency or application or making on applications resilient right so that again you know as we saw the availability aspect you
Asmita
Know is taken care of so again you know there are a lot of tools that we can um you know explore and add to
Asmita
Our you know test pipeline basically or later while you know these are uh the performance side of it uh another you know as we
Asmita
Go to staging and this is where you know the entire application of product you know has come together um this is where you know we'll
Asmita
Have to stress upon usability because now uh you know we know uh you know we we know we have we have a basically look
Asmita
Of how the you know product is spanning together how it is shaping up so how we can you know take care of the accessibility
Asmita
Needs how we can you know ensure that you know our application if it is catering to multiple geographies or locals is it you know
Asmita
Tuned to multiple you know Geographic than local uh do we have seamless experience say you know if I open Amazon either from India or
Asmita
From us uh you know do I still you know get to get have the same experience and the uh functionalities right so so these
Asmita
Again you know are going to be the key uh aspects and as well you know you can augment it from the um perspective of
Asmita
You know measuring end user performance if your application is say catering to a consumer facing like if it is b2c you can definitely you
Asmita
Know look into that you know are there any other best practices and there are tools which give you a score of what your best
Asmita
Practices are what are what is your SEO score how how can you improvise it so that at in turn right your hits or you
Asmita
Know your reach to your consumers increase right and there are definitely you know again a lot of libraries and tools available which you can
Asmita
Uh you know adopt all right and last but not the least you know uh security Assurance um as we said right privacy is you know
Asmita
Very dear to each one of us today and assuring that um is going to be you know again one of the make break you know
Asmita
Kind of a decision so uh so a few key considerations from security perspective is so I would not only say that you know uh
Asmita
Say you know zap or you know where error code and tools like that is the answer but let's you know shift left here uh
Asmita
Basically or you know there's a queer there's a good term coming up uh towards the end you know of this particular section so uh
Asmita
Attack intelligence so you know initi so I'm sure you know you must have um heard about threat modeling uh where you know you anticipate
Asmita
The risks where is it that you can be you know uh compromised which are the detections from which you can be compromised from this
Asmita
And that right so there's this new concept of attack intelligence also that has come up which is similar to threat modeling but uh you
Asmita
Know what's a threat modeling you know answered the question as to you know what could happen to me right whereas attack intelligence is being
Asmita
Of course anticipating what could go wrong or what could you know happen to me um so by me I'm saying you know as a
Asmita
Consumer or as the product right but also what is happening to me so not only you know uh ensuring that you know I have
Asmita
Tested the not only saying that I have tested for security but being vigilant of you know our various layers be the application servers networks
Asmita
Um even devices uh since you know we are getting so much into iot this and how we can be vigilant of you know our entire
Asmita
Ecosystem and gauge the that you know what is it that could happen what is it that could be happening to me and also what
Asmita
Is it that is happening to you know the ecosystem similar to me learn from them and come back and incorporate those security practices back
Asmita
Home right so there is a lot of consideration again that you know and studies tools um you know and the entire um you know
Asmita
Support system that is coming up from the security perspective as well and um definitely you know we'll have to be inquisite about it and
Asmita
Uh you know learn about it um again you know as a in pursuit to shift left you know we can definitely ensure that you
Asmita
Know we as a team as well as you know our development team is aware of the secure because you know these are like the
Asmita
Preventive aspects that we can take care of performing a static code analysis uh code analysis as well as the dynamic analysis and testing so
Asmita
I understand say probably you know secure code analysis or static code analysis um quote reviews of our development code this may be out of
Asmita
Our purview however you know we could as a QE team be vigilant of that is a is my team following it uh we can
Asmita
You know ask these questions to the development team and ensure that you know as a team we follow you know these practices Dynamic analysis
Asmita
Definitely you know would be in our code where we uh you know perform the entire vulnerability assessment um check uh you know what the
Asmita
Results are read out any false positives and then you know from the high vulnerabilities or you know the threats that we find how we
Asmita
Can you know have now penetration testing done and check you know what are you know an actual you know vulnerabilities remedy them and then
Asmita
You know the cycle continues so again you know security is not going to be you know a one-time event uh by test automation what
Asmita
I mean is how uh you know security you know could be tested via these tools how it could be tied back to test automation
Asmita
So that it's so that you know testing in smaller pieces but testing frequently uh and that too you know for all aspects is taken
Asmita
Care of right be with respect to functionality via test automation or you know the non-functional requirement as good as security uh via you know
Asmita
Automating the entire security flow right and shift everywhere is the term so you know uh so I think safe shift left has definitely been
Asmita
For a long time and we can see that you know the shift right like basically being vigilant and testing in production is here so
Asmita
With security you know shift everywhere is again you know going to be the key and the terminology you know that we'll have to get
Asmita
Used to and the idea that we'll have to get used to um shift every uh shift everywhere test you know in chunks but continuously
Asmita
All right so these are the considerations that we'll have to take care from the security perspective and ensure that you know we you know
Asmita
Have them so with respect to test platform right now let's see so now that you know we saw the importance of each type of
Asmita
Testing when do we introduce what are the features that you know we'll have to ensure that each one has so for example you know
Asmita
I may you know test usability but you know can I uh you know have a tool based approach which in turn can be you
Asmita
Can talk to the test automation framework or be driven by test automation framework can I you know integrate my security testing with that test
Asmita
Automation framework so that you know when I when as I developed it and as I bring these pieces together how can I you know
Asmita
Trigger my pipeline in such a way that I may have gated checks like if my test automation Works clearly let's go and test for
Asmita
Performance uh if you know performance gives me a green signal can I you know now test the other aspects like usability security
Asmita
Etc right application performance monitoring you know that's why you know it's a standalone piece it would you know be continuously something that we would
Asmita
Be you know looking into and come continuously on uh similarly you know the uh testing um something like you know Excellency right so how
Asmita
We can have you know automation of all this and how it can be enabled by the entire devsec Ops you know pipeline is going
Asmita
To be the key and is you know the test platform that we can you know have so so I think you know with this
Asmita
You know what I would definitely want to stress upon is um that you know let's build these uh you know um building blocks or uh
Asmita
You know these components in our uh you know in our day-to-day uh basically you know um approach that we WE tv take you know
Asmita
For our um uh you know um testing and enable it by devsecops and have a platformer for our owns okay
Asmita
So with this you know I would like to say that you know I would like to you know definitely I understand you know this
Asmita
Information could you know feel a bit overwhelming uh because there's a definitely a lot to do so Rome wasn't built in a day and
Asmita
I would like to extend on the saying also by uh you know that Rome wasn't built in a day and by one person right
Asmita
So we'll have to come together as a team give it a time uh and watch for our uh you know platforms to uh or
Asmita
Our you know approach to you know um slowly move towards a platform and take a shape of a platform right so we'll have to
Asmita
Gradually uh you know get there however the intent you know has to be you know definitely with us um and that's something that you
Asmita
Know my uh all that is something that you know I wanted to um you know share with you all today um and you know
Asmita
One interesting part which you know uh it's a bit sensitive and that's something you know I didn't highlight in my um in my uh
Asmita
You know pressing earlier is one of the asks from the cios you know is also about having the right testing Talent at the right
Asmita
Time so from this perspective right and in order to you know quickly summarize like you know if I quickly summarize um customer happiness or
Asmita
Digital happiness as they see ensuring business and all of this has speed definitely is our you know are our key objectives and something that
Asmita
You know we'll have to definitely you know adhere to and ensure that you know we enable however also it's you know incumbent on all
Asmita
Of us that you know we invest into uh or we are in line with the industry we invest in knowledge we maintain this entire
Asmita
Momentum so that you know the comeback of QE that we have seen recently it continues on its course all right so with this you
Asmita
Know I would it come to uh you know the end of my presentation and if there are any question and answers you know I'm
Dinakar
Open to it are there any questions okay I'm not able to see the chat
Dinakar
Yeah I'm just waiting for a few minutes so that people have enough time to type in their questions and send them across
Dinakar
Okay uh here are a few questions um this question by Varun you know what is your opinion on low code or scriptlist test automation
Asmita
Okay so uh I mean definitely you know when I say that you know so when we highlight it on test automation right um so
Asmita
Uh you know as the industry I I understand you know where the industry is heading to um we are definitely you know heading uh
Asmita
Towards you know adopting uh these low code and no code platforms you know that's definitely you know it's in and uh you know we
Asmita
Are I'm very I'm a proponent of it however my only submission uh you know to these Solutions is that um it has to be you
Asmita
Know I would like to quote from what I said that you know it has to be done right right so um although it's a
Asmita
Scriptless um you know Solutions uh that we are adhering to how we could you know still you know apply all automation principles best practices um
Asmita
That you know we have uh uh been using right um uh in our traditional uh test automation Frameworks right how we could you know
Asmita
Uh still apply those uh and still apply that mindset is going to you know again play a very key role then again and Varun
Asmita
I think I hope I answered the question um few more questions
Dinakar
Okay uh this one is more about a preference but yeah is there any uh this is by a question from Diana is there any
Dinakar
Language or preference for these tools that you're talking about
Asmita
What I would say is that you know at times you know it happens that you know we tend to uh go by you know
Asmita
The language that you know we as a QA are comfortable with however you know uh with the traditional approach of test automation what I
Asmita
Recommend to my teams is speak the same language as your developer I think uh so that you know it again becomes an inclusive activity
Asmita
Also because I think we also have a responsibility towards the inclusion right so we'll have to basically uh talk the same language as the
Asmita
Developers so that uh so that's my only asked so and that's why I said that you know be ready for a multilingual test automation
Asmita
Or you know um be ready to learn multilingual you know test automation uh so that you know you can cater to different um products
Dinakar
And ecosystems right right yeah just a couple more questions uh um
Dinakar
So this one is in terms of use case okay can you elaborate a few use cases of AI in testing uh this is a
Asmita
Question from use cases we are in testing right right so um so from that perspective right you know from what I have seen and
Asmita
I think you know uh this is something that you know we are also dwelling into a lot these days that you know how AI
Asmita
Could be applied in QE so uh so of course you know the tools that have come up right all the tools uh they have
Asmita
You know quickly um you know adopted so right now we may not be even leveraging AI but at least uh the smart algorithms you
Asmita
Know are have been you know definitely applied so uh you know having um self-healing or even self-healing of testing is one of the application
Asmita
If I shift left or if I shift ahead right in the cycle um the example that you know I had given right that um
Asmita
We tend to write a lot of test cases uh and you know a lot of team members so so every team you know has
Asmita
A lot of members each one right test cases and over the time you know the duplication starts cropping in the redundancy starts cropping up
Asmita
Right but at the end of the day you know we'll still be left with say a huge number of test cases and since you
Asmita
Know it's a black box so it's going to be very difficult to um you know say that you know it's okay not to test
Asmita
This or you know so we still end up you know testing the duplicate flows as well right so this is where you know another
Asmita
Aspect of um you know basically how we can um you know have ai to go through our test suits and help us to find
Asmita
You know these duplicate duplicates how we can have you know AI to say find what are the duplicate defects can we start classifying the
Asmita
Defects say into you know at the nature of the defects can we can I classify automatically what must have been the root cause of
Asmita
This defect so that you know um we again you know derive some actionable insights out of these you know um these models or you
Asmita
Know solutions that we make out and again I think performance engineering um so this is the report also says said that you know performance
Asmita
Engineering again is going to be a discipline where AI you know could be applied the max so I would look forward to like you
Asmita
Know uh definitely anticipating the issues and you know user Behavior but uh I think that would be an interesting space to watch out for
Dinakar
I'm sure just one last question uh this is from Smitha um so she's asking does does performance applied to Applications meant for internal audience
Asmita
Um yeah let me repeat that question yeah applications meant for internal audience
Asmita
Right so I understand you uh and at times you know there are so many times you know where I you know we face this
Asmita
Resistance that you know I'm supposed to you know have this application only for you know uh internal audience and this and then but I
Asmita
Think you know be it the internal uh customers or your external right assuring that experience is you know going to be the key right
Asmita
Uh because you know even I'm sure right you know even if I'm uh developing something as simple as a HRM is uh but unless
Asmita
You know I give a good experience it's not going to show to my you know Associates or employees that you know I care for
Asmita
Their you know time and I care for you know their experience I think we'll still have to maybe the intensity uh might differ or
Asmita
You know the so I might you know do it at a different or a later stage than say you know uh embedding it into
Asmita
Each and every Sprint so I could regulate that but have you know not doing it at all is something that I would you know
Asmita
Not encourage and plus you know as we saw right there are so many facets to Performance it's not only about you know how it
Asmita
Handles load but is it available is it responsive this and that so there are many many areas that will still have to go ahead
Dinakar
And test right well uh thank you so much I think there are a few questions enrolling it but uh you know in the interest
Dinakar
Of time we have kind of talk those questions for a later time uh but yeah it was it was it was an honor listening
Dinakar
To uh Smitha and we really want to thank you for sharing your valuable insights and you know picking up practical examples and real world
Dinakar
Scenarios your presentation is beautifully covered all these and given us some practical pointers that we can you know work on uh through your experiences
Asmita
Thank you thank you so much thanks thanks vinegar thanks be Claudia and thanks to everyone thanks thanks for you know joining us today
Dinakar
We also want to thank uh you know each one of our participants uh for joining us on the break series uh we're sure you
Dinakar
Know asmita's insights on holistic testing has sparked a few ideas you know that you can take back and start to implement in your organizations
Dinakar
As well uh yeah so thank you once again for being such a wonderful audience and yeah have a good day
Dinakar
Thank you thanks everyone thank you
