Ensuring Quality in DevOps Culture

Video Transcript

do mobile testing submit so my name is Sagar mahindar and I am from India I hold a bachelor’s degree and uh currently working with r redet I have almost five years of experience in a quality engineer role mostly I am responsible for B task of project involvement in Sprint planning and releases also uh I automate test cases integrate it with the cicd pipeline and uh to make sure that our product is BU free uh so today I will uh share uh I would like to share one of my experience like uh when I was uh working with uh previous organization uh we used to follow waterfall methodology and uh because of this our uh development uh cycle was too long and uh we used to face uh some challenges like uh difficulties in accommodating change request because uh customer requirement requirements keep on changing with time and uh it was a difficult to accommodate uh any change request after uh after the requirement specification phase was complete also in the uh in waterfall model testing is typically done at the end of the cycle uh end of the development cycle this means that uh defect may not be discovered until late in the development process which uh which can be expensive and uh time consuming uh to fix but uh when I uh when I join rat uh where aile methodology was used I got to know why aile is important and uh why AEL is important for development and testing purposes and uh what makes it successful is De offs so let’s start with the today’s topic ensuring quality in de’s culture uh so moving to agenda for the today’s call yeah so let’s walk through from the agenda for the today’s session so we will start with the introduction for doops and their importance then uh we will learn the relationship between QV and uh doops moving further uh moving further we will discuss the role of uh QV in De offs and there is responsibilities in brief then uh we can discuss more about uh challenges that QV face while working with de and uh we will have some deep knowledge about tool chain integration and their importance at last we will discuss more about skills required for QE to work with doops and uh and then we can have a conclusion and QA session yep uh so moving to the first slide of the presentation yep here it is so what is doops doops combines a development and operations to increase the efficiency at speed and the security of uh software development and uh delivery compared to traditional processes it allows organization uh to Ser uh better uh to Ser customer better and uh compete more strongly in the market in a simple words we can say devs can be defined as alignment or development and it operation with better communication and collaboration there are few reasons that uh why Ops is necessary for modern businesses so I have listed a few of them here like a short development Cycles early error detection reduces operational cost improves customer satisfaction so we will start with the first one short development Cycles so in De offs uh deop allows uh developer to release their product much quicker because uh they know they no longer have to wait for approval from other teams instead uh they can release new version as soon as they are ready for testing in which uh which means that uh bugs can be found bugs can be caught much earlier in the process and uh fix before significant issue second is early error detection when teams work together on a project when when uh teams work uh together on projects uh there’s more opportunity for errors than uh a team working on same project but separately so in De off in De environment when one team makes an error in coding or testing another teams can detect it immediately and uh fix it before it causes any damage in introduction it leads to higher quality product and uh fewer problems uh down the road third one is uh reduces operational cost so it’s hard for businesses to keep up with the pace of technology today if you are not keeping up you might as well close up shop because your competitors will leave you in the dust one of the biggest reason uh why doops is important it’s because it helps companies lower operational cost by increasing efficiency uh which means uh they can spend less on servers support staff and other resources while maintaining their competitive age so last one here it is uh improv customer satisfaction one of the important aspect of any business is keeping your customers happy there is no better uh way to do this than by providing Excellence customer service which can be difficult for some companies doops can help make this e easier for you and uh your team uh by integrating uh by integrating it uh by integrating your development team with your operation uh teams can create a seamless experience for both customers and uh external employees it will increase customer satisfaction because they don’t have to wait long for their request to be answered it will also keep things running smooth within uh your organization because everyone knows what they need to do next and uh hope uh we got the basic and the importance of deop here now we can move to the next slide of our presentation yeah here it is so here we will discuss a relationship between QA QE and deop and uh where exactly uh Q fits into the world of continuous integration dominated by DS well pretty much in uh every release a quality analyst is required to assure the robustness of the product especially in the world of doops where uh the updates take place in the application almost on weekly basis with so many frequent changes taking place outages uh look to be very common but outages are supposed to break the life of the developers and the managers everyone needs to needs a quick hard fix when the service of the product goes south affecting more than the single customer but an uh immediate fix needs to be thoroughly tested before it get migrated into the production developers and product managers would want the job to be done in a V this is very uh this is where Q needs to set up and takes the responsibility of evaluating whether that immediate fix for an for One Outage does not end up affec uh affecting the any other functionality of the application so just as much as developer is needed to get the read of the outage by a quick fix a quality analyst is needed to prevent future outages to as many extent as possible uh moving forward yeah so moving to next slide challenges faced by QV teams in doops so several challenges may arise due to fundamental changes in workflow collaboration and Technology use that such as integration quality engineering and doops environment is not just about ensuring the quality of the software but also about enhancing the processes that uh lead to the development of high quality software product continuously here I will uh discuss some of the main challenges as main challenges a QE might face while working with uh doops so I have listed a few of them uh such as uh shift LIF speed versus quality tradeoff automated testing expertise keeping up the changes so we will uh walk through with the first one shift lift and uh continuous testing TS emphasizes shifting L lift which means testing early and often in the development cycle this requires the QE team to integrate testing simp ly into the daily workflow of development which can be significant change from traditional models where testing was a distance phase QB teams must adapt by developing automated test that can run effectively in every stage of the cicd pipeline second one uh speed versus uh quality tradeoff de offs prioritize speed and efficiency in delivering updates and uh new features QV teams are challenged to to maintain high standard of quality without slowing down the development and deployment process this can uh sometimes create tension as a drive or this can create us tension as the drive for Rapid releases May compromise the thoroughness of uh testing automate uh testing expertise with the emphasis on automation inops QV team must possess strong skills in automate testing this includes the the ability to write maintain and understand automate testing script and Frameworks developing the expertise require time and TR training which can be a challenging especially in the fast space environments keeping up uh with changes in a culture changes occur rapidly and frequently QV team must keep up with these changes in both the software being developed and the Technologies used to develop and test it this continuous learning and adaption can be demanding uh moving to next

slide yeah uh challenges for qwi in Mobile doops so several challenges qwi face in a mobile doops so I listed few of them uh diverse device landscape platform fragmentation specialized testing approaching variability in network condition App Store compliance so mobile devices are used in environment with the varying Network condition testing how an application performs across different networks like a 3G 5G 4G and Wi-Fi and how it handles Network transaction like uh switching from LT to Wi-Fi uh or experiencing a dropped connection is critical for QA but hard to simulate accurately per performance Ben marking uh ensuring the App application performs well under various condition like uh in the background during High CPU usage or when the battery is low performance benchmarking in a real world scenario is a significant QA challenge moving to next L and uh yeah roles and responsibilities in QA of QA inops the quality engineering role is more demanding than QA watch as it is more fundamentally focused on quality the QA role demands that uh you have expertise in all aspect of Dos which can directly or indirectly related to product quality including software testing automation testing aile processes cicd Etc uh tool chain integration so what is toolchain integration a tool chain uh is a ction of uh tools and technologies that uh enables development and operations teams to collaborate throughout the entire development uh process uh addressing key uh Dev fundamental such as continuation continuous integration uh continuous delivery Automation and collaboration tool chain integration in DS and quality engineering is crucial for achieving the seamless Automation and uh collaboration required to support rapid Reliable Software releases a well integrated tool change uh allows for continuous uh deployment testing and uh deployment uh which are the Corner Stones of the deop philosophy uh here a detail look at the importance of toolchain and uh we can go in the brief of uh tool chain integration I listed a few of the characteristics of tool CH integration uh like a streamlined workflow automation enhanced collaboration consistency and standardizing and realtime feedback so here we go with the first one uh streamline workflow automation integration of tools in the deop environment helps in creating a seamless workflow for developers operations team and the quality engineer each stage of the software deployment life cycle from uh planning and uh coding to testing deployments and monitoring can be automated this automation can reduce the manual hands off between teams and uh minimize errors and speed up the process process of the software delivery enhance collaboration tool chain integration facilate better communication and collaboration among cross functional teams uh tools such as uh chatbot integrated with issue tracking system can automate statue uh status update and alerts this keeps uh everyone in the loop and uh make it easier for team members to to quickly uh to development or uh operational issues and uh to ensure the that everyone works from a unified platform with a access to realtime data uh here we go with the third one consistency and standardizing uh standardization integrate uh integrated tools help standardizing process across the development testing and the de uh deployment faes this standardization is crucial for maintaining consistency uh consistency in how software is developed tested and uh released which in turn uh which in turn helps in managing complex system and uh reducing unexpected Behavior or disk or discrepancy in uh production environment uh real time feedback uh integrated tools uh provide continuous uh feedback and uh detail metrics about every aspect of the software development life cycle for uh instance uh dashboard tools that integrate with CI servers uh testing Frameworks and uh deployment uh tools that integrate with CI servers uh testing Frameworks and the deployment this data is vital for making informed uh decision about the product and process uh Improvement for Quality engineer uh engineering uh integration of tools like uh Source control build servers uh deployment mechanism and uh testing Frameworks means they can ensure comprehensive quality check quality check this integrated approach helps QV uh Team to implement Advanced testing uh strategies such as shift LIF uh testing uh performance testing and uh security testing as a part of of a deployment pipeline rather rather than the after thoughts like a difference between uh web doops and the mobile doops so yeah so how it differs like uh we have mobile application must be tested and optimized for the Border range of uh device and uh operating system uh unlike web application that uh can be updated in real time mobile application requ wires passing through App Store reviews which int uh introduce delay and additional planning for roll outs mobile deploy uh mobile development often requires uh Native tools and environment which can be complicate the cicd pipeline and emulators and simulators are used but uh testing on a real devices is critical uh for ensuring the real world usability Which is less of of a concern in uh web development so this was about the differences between the uh web doops and the mobile doops so now moving to next slide and uh time to get to know the skills required for testers inops yeah so some import important skills required like uh understanding software testing will enable you to spot and uh resolve software program problems quickly knowledge of the doops to uh Technologies will enable you to organize and automate the software deployment and uh testing processes uh one should have collaboration uh abilities with uh developers and other team members understanding how to automate testing and uh deploy codes if it uh deploy code updates regularly is important knowing how effectively cicd pipeline works and uh it works is better so this was the skills required for QA to work with the de but uh I know there are much skills uh much skills uh you might know but uh here I have pointed some of the skills and uh it is a major skills yeah so moving to the conclusion of this presentation and uh conclusion of the uh and the evolution of the QA the impact of uh doops on quality assurance testing strategies is transformation metric by embracing a culture of collaboration Automation and continuous testing organization can achieve the delicate balance between speed and uh quality in uh software development QA teams play a vital role in the Paradigm Shift contributing uh to the creation of a resilient uh reliable and high quality software in the dynamic deop environment as organization continues to evolve the integration of uh uh of De offs principle into QA testing strategies will be fundamental to staying competitive in the everchanging landscape of technology so uh what I think like QA should not limit to only for manual testing or automation testing but they can grow by collaborating with different teams like uh uh de team uh developers team they have to make the communication strong and uh they need to suggest the improvements in the process by this the there will be no separate teams like uh development development team QA team and the de team but we have to work as a whole team and uh although just we have to make sure our product is bug free and uh by saying this thing uh thing I would like to stop here and uh I hope you like the presentation and uh this will be a productive in your day-to-day life and uh yep thank you

okay great well excellent presentation cigar um we got a lot of questions and a lot of Engagement from the audience um and I’m glad we have enough time to hopefully answer them um so let’s start yeah let’s start with Britney um she says um mobile apps face strict rules from App Stores so how do you adapt your mobile QA and Ops process to meet those challenges yes K so basically app stores have different guidelines based on the operating system General process is like d uploads application on store then uh there is automated uh scans to check malare and the functionality issues then there is a manual scan to check usability issues and uh then developers gets the status like app is accepted or re rejected and the feedback to avoid these challenges in app store we should follow app guidelines from the scratch of the product development regularly uh test buil uh by uh we can integrate test built in cicd pipelines to address any issues Implement a beta testings to get feedback from the uh from the group of the users and uh ensure that your application application follows best practices for security including uh data encryption security uh authentication mechanism and protection against common vulnerabilities such as SQL injection and cross-side scripting wow yeah you know in your answer you mentioned a little bit about U beta testing for example as a as a practice I’d love to hear a little bit more about um you know your experience there and um maybe some learnings that you have at from from Red Hat yeah so surely so while working with a previous organization organization we were uh testing some mobile application and we Face many challenges like while testing a mobile application we have to test it on a different platform with different networks and we have we also face some challenges while uh Testing mobile uh devices like uh there we have to test mobile uh application when uh there is a connection lost or a network switch from LT to Wi-Fi so we started utilizing cross platform testing Frameworks like APM and espresso which allows us to run our script on multiple operating system also we started manual testing on real devices to test functionality and usability testings and uh also uh uh we use some simulators and emulators uh to reproduce the functionality on other devices as well yeah yeah yeah I think that’s really interesting trying to tackle those challenges of like testing across diverse mobile platforms I mean you know obviously real devices is you know we think at Caton we think that’s really an essential part of the process so I’m glad to hear um you know that that’s a practice that you guys are relying on as well um we have another question here um ashcans um sorry I think I said your name wrong apologies it says how do you handle frequent updates during mobile testing yeah so answering to that uh question like uh after each update uh we focus on regression things to check that uh new code changes have not cost any harm to the existing functionality we track all the changes in logs and communicate closely with the development team to understand the implication of each update is followed interesting okay um I see another one um another one that’s coming in uh it says uh what new trends or technology IES do you think will reshape uh mobile QA practices in the near future yeah so answering to that uh we uh we are hearing uh many things from uh related to Ai and machine learning Ai and Ma Ai and machine learning Technologies are increasingly uh being integrated into testing tools like and Frameworks to automate test case to optimize the test coverage and identify patterns in the test data for more efficient uh defect uh detection and result resolution also there is one thing like a shift LIF testing uh which involves moving testing activities earlier into the development process uh with a focus of uh with a focus on uh with a focus on preventing defects rather than just detecting them them this approach emphasizes collaboration uh between developers testers and other stakeholders to ensure quality is built into the product from the out uh outset also there is one thing uh continuous testing and uh continuous delivery so continuous testing uh extends the principle of continuous integration and continuous delivery to the testing process and enabling uh automat testing to be seamlessly integrated into the software development pipeline this allows this will allow for faster feedback loops shorter releas cycle and uh improve improved overall quality yeah one thing we talk about um at Katon a lot is how to improve people’s maturity in their processes you know around uh sort of achieving mob mobile Excellence if you were to give advice to somebody who’s in a testing organization mobile tester um maybe who has a little bit less mature processes you know than than what you’re what you’re practicing at at Red Hat what advice would you give um you know just very generally speaking for people to kind of up their their skills and improve their processes overall yeah so K I would like to advise uh before starting uh testing we should understand the requirement clearly because uh because uh this involves understanding the application functionality then we should Target the audience based on the target audience uh we should select a range of devices and operating system then detailed test plan that uh includes the scope type of testing to be performed resources needed timeline and risk assessment should be created then we should select a type of testing there can be a functional usability performance regression security many type of testing required testing types to be conducted are decided decided based on the project requirement and also we should keep the detailed records of the test case results bugs and fixes for analy and Improvement and uh to identify any bugs uh fix issues that that are not covered in the test cases uh we should use feedback and we should regularly ask for feedback from uh with the help of beta testing or we can uh create any document from which we can get a feedback from the real users or in a team members from the team members wow thank you I think that that’s like really really valuable advice to to like kind of Take it Back to Basics and start with understanding you know all those various requirements before you kind of dive in and just start um you know on the testing um so I would like to say we we really only have about a minute left I think we’ve answered um the majority of the questions that came in through the Q&A if there’s anyone out there that wants to chat in one uh real quick we could probably take one um but other than that maybe um if you have some closing or concluding thoughts yes okay this was a good experience uh to give a talk in uh mobile testing experience Summit I would like to participate many years from here as well and thank you for your uh coordination and uh cooperation oh thank you so much we really appreciate it I’m glad it was a great experience