 Here we are today on the second of the Selenium conference with the lightning tops and with the person who needs no introduction Mr. Naresh Jain is here and without any delay I hand it over to you Naresh. Thanks Subash for the introductions and wow it's a it's a bit early on a Saturday so I appreciate everyone coming in on time I see a huge number of people coming in and quite excited about hosting the lightning talks. Lightning talks are quite special at least for me and a lot of people in the Selenium community we've seen some fantastic projects actually come out of the lightning talks and I'm hoping today we would have something similar where we would be able to see some fantastic lightning talks leading to some fantastic projects from there. We have a so the process of getting people to present the lightning talks generally when we do an in-person conference we just have a board a white board where people go sign up and then they just kind of line up during the lightning talks and then go through it because this is virtual we wanted to try and you know keep it a little bit a little bit of prep is done so we announced you know the people to submit lightning talks and we caught quite a few people who submitted lightning talks out of which we have selected a subset about eight people are selected so you know they will go first and then if we have time we will be taking more people life impromptu so we'll see how that goes you know so I'm just going to quickly run through just give a little bit of a background and then run through some of the rules of what we're going to be doing in this lightning talks. Lightning talks are essentially three minutes crisp like power packed talks where people share some ideas these are very raw ideas in some sense so it's a power packed three minute kind of an idea presentation and we are hoping that this will spark some some ideas in your head and something interesting will come out of it you know this is also a great opportunity for people who are first time speakers or who have not presented before to get on the stage and do something so it's a way of basically also creating new speakers for us and like I was saying you know a lot of times we've seen that lightning talks lead to interesting ideas and from there interesting projects come out so just as a case in time you guys know Dan who is the co-creator of the Appium project in this during the Selenium conference 2022 in London you know Dan was presenting about what he had done the automation he had done around iOS using similar syntax like Selenium using again page object pattern and stuff like that and you know some of the people who saw that they suggested why don't why don't why don't Dan give a lightning talk which Aron Jason Huggins who is the co-creator of Selenium was hosting and you know Dan of course had some technical difficulties but then was able to present his lightning talk and he was asking if anybody's interested in contributing you know three minutes or five minutes later everything was over and you know Dan thought that's the end of it right nobody's reached out but of course Jason reached out to him they kind of then work together and that's what led to the Appium project right and I'm sure like this there are many other stories that if you look at the list that Manoj and Diego shared yesterday many other projects actually got inspired and came out of such things so that is why lightning talks are very special for this open source testing community and we try to make it a point to have like a dedicated keynote type session for folks so today we have like I said earlier we have eight people that have been shortlisted and we will give each of them three minutes to present their lightning talks what I'm going to do next is I'm going to go through and invite each person you know who's been shortlisted they have already been communicated so the order again that I'm going through is a bit random it's basically based on when it's like a first come first thing so whoever submitted the first and got selected I'm just going to read out their name so can I please have Argo from Indonesia who wants to talk about HR utility the HR utility in Selenium 4 so you're going to do the inauguration Argo I hope I pronounce your name correctly and I'm going to set the timer for three minutes I hope you're ready you can share your screen and we can go from there so I'm starting your time of three minutes Argo I'll give you a time check at two minutes 30 seconds the last 30 seconds and then we go from there all right okay thank you so hi everyone I'm Argo from Libre.com today I will share about the HR utility in the Selenium 4 so the motivation when we are creating this one is when we are doing some like automation something this like blank spec yeah happen yeah but we don't know where is this coming from usually if you are running it manually you will use the inspect element in your browser and then go to the tab network and then you can set it the files and then you can analyze in the future the files that you have set from this windows is called the whole hard files so if you are opening the hard files it's like a JSON file yeah so we see the possibility for writing a utils to recreate the hard files and FOILA this is introducing the hard file so what is actually the hard files as we know we have Selenium 4 that feature connected to the CDP so we create some converting between the Selenium CDP request and respond and then write it to this so the concept itself is from the Selenium 4 we intercept the network traffic and then we'll be on the hard utils we will mapping the request and respond to the hard format and then after that we're writing to this and then you will get some file that hard and then you can use it for the puder analysis in your browser or in your hard viewer tools yeah actually our tools is already online so you can try it by put the dependency and also for the repo story at your network listener for your driver and also where is your specify your hard file and then you can run your automations as usual and after that if you want to write hard to this you can call the method for the creating the hard and after that you will see the hard file in your project folder yeah so what is the listen run that we get during these research first thing is not all data inside the hard is exist in the current Selenium API so we need some like work around for getting the data that we want and then in the previous Selenium version we found that but that not complete yet for the HTTP method for example pause get and pass et cetera but in the current Selenium it is already fixed yeah so if you want to try the how you do you can scan our QR code or you go to the github pics and then you can contact me via LinkedIn or email and I'm Argo Druto from blibli.com back to you Nares wow awesome that was perfectly timed Argo and I think you finished well before your time actually again if people are interested in getting more details about this maybe you know yeah I think someone's asking please share the link for the hard utility hard utils so if you can just put it on the chat that'll be great thanks Argo wonderful talk and I'm going to move to the next speaker now so the next speaker we have here is Vaibhav, Vaibhav Sukhla so Vaibhav is going to be talking about testing coverage with regards to application code so hello everyone my name is Vaibhav I am working as a automation engineer in to the new private limited node idea so today we will talk about testing coverage with respect to application code as you know in general scenario when we are doing the testing we don't know how much testing we are doing in respect of application code how much we are covering the application code so there is no use to do the manual testing or automation testing in respect to of if you don't know what is the exit oriented criteria so this is the new tool which is developed by the EPAM so we can use this tool and we can come to know how much code we are covering because in general when we are doing the automation we don't don't do the monkey testing or adopt testing so today we will cover the introduction solution tagging tags and how it does work and deploy how drillforge is the tool name and the demo so let's start without wasting the time as you know application code is important parameter to know the testing coverage we might be having tons of test cases but we don't know we are covering the hundred percent of application or don't so when we are doing the unit testing using the sonar cube or jgo code it provide good coverage but there is a dependency that developer has to write the unit test so when we are come to testing point of view so there is a drillforge tool which we can use without a dependency on the unit test so drillforge is a tool for real-time application profiling it does not mapping test case and does not hand dependency on the unit test and it does not affect the application code also we don't have any dependency on the application code so tech stack if you talk about it has the type of script Kotlin if you talk about back end admin stat watcher and if you talk about frontend it's using the UI and some APIs so we are showing the without wasting the time I can so the demo how it goes so there is a manual testing browser extension of drill4j so which we can set up on our local as you can see on my browser extension there's a drill4j browser extension so I need to add you need to add this in your extension and once you start adding this and there is a deployment this is the my drill4j which we can deploy with the help of docker image so this is the docker image from this we can deploy drill4j admin portal on your server or on your local so currently it's running on my server so you can see this is that drill4j admin and here we have here we have the multiple projects so I am going to give our demo I'm using the demo application for this so this is my application so I will start doing the manual testing and we can see how much code coverage is going so you can see these are the tests when we're coming to build methods these are the classes or the methods which is developed by the developer so these are the application code and we don't have the access just we can see what are the classes and what are the packages so you can see these are the classes and packages now I will start my manual testing and we can show how much coverage is going what are the different classes and methods we are covering in this manual testing so let's let's start have a quick time check you're done with your three minutes I'm giving you 30 second grace yeah so I'm giving the demo I'm giving my manual test case name I am starting the test so I'm giving the username any username we can give one two three this is a demo application so you can see our test case it started and we can see on this here also it's running so we can submit we are performing the some action on our UI on application can be run with the backend also and front end also so you can see 7.3 percent is covered so I'm stopping my manual testing here and I'm stopping the finish scope over here also I'm stopping the manual testing and now you can see I run a demo selenium test just now and it covers 20 percent of my application code and it covers 21 methods also over here so these are the type how we can cover and how we can find what are the different classes and methods are covered so you can see this is the controller class which is 15.4 percentage cover and this is the DTO 8.8 percentage covered so this is a just a overview how we can use drill4j with the applications code so these are the agent or the how we can deploy our drill4j and dashboard so it has a dashboard also which I saw so that's much from my side and it was in school. Perfect all right thanks Vibhav this was a good demo I think there is one question from the audience so Mudhat is asking if drill4j needs to be deployed on the same server on which the application is deployed? No it can be deployed on any server it depend no dependency with the application it can be deployed in centralized and we can use multiple applications with that. Perfect I'll take one last question from automation how do we achieve code coverage using docker? So we need to set up some configuration in our docker file and we can do the automation code coverage also cmb isoad manual testing so just we need to have some dependency in our .xml file. All right awesome so I think Vibhav you could maybe share the links and other details in the chat thanks again for your wonderful lightning talks thank you the next person I have is Kanchan who's going to be talking about testing lessons from a nine month old. Hi everyone am I audible? Yeah yes hi Kanchan yes your audible and your video is visible so I'm going to set again a timer for three minutes I know you'd ask for a little bit more grace so we'll see how that goes but I'm setting the timer for three minutes over to you Kanchan. Okay thank you so much Nareesh so hi everyone good morning I'm Kanchan Katare I'm QV Leader at Red Hat and the topic of our presentation is testing lesson from my nine month old so congratulations you're going to be parents it's been 18 months since we heard this and our life has been changed ever since a good change a great change this 18 months has been roller coaster so right so far and we're loving every part of it so like from nine months old I learned this lessons I just want to quick share with you so first lesson I learned is testing is crucial I had to go through this several layer out in a phases and this nine month of span this checks where to check the mother the baby development and the mother health as well similarly every projects need to be checked at regular interval at modular stages to ensure building perfectly as expected testing at the right time and the right times will ensure healthy chubby smiling project or a project owner I can see second lesson I have learned is give everything its time all that beautiful loveable task take its own time to build and develop just like baby take 40 weeks so often we see project on our developer team pushing for releases and expecting nothing less than perfect what I learned here is give everything its time Rome was not building a day I mean even if it was I'm sure testing took more days but on a serious note you could cannot expect testing to be done in one go it requires round of testing and patient hurrying on to things will only let the bugs fall through the cracks lesson three make your demands heard by the right people when she is hungry she knows whom to look out for when she is sleepy she knows whom to reach out to two important learnings I learned here is to find something if you find something have suggestion need something reach out to the communicated properly this may include documenting it or filing a JIRA so you are heard by the community and second ensure you are communicating your bugs to the right set of people to who who can help to resolve to solve your queries like UI related bugs have no place in the functional JIRA board fourth lesson is up skill from the first day till now she is learning new skill every day like smiling to Google who is now able to say mama papa likewise ensure you are adding new domain skill to your profile upgrade your older learning look out for the new updates like selenium 4 is there selenium 5 will be coming in market no point in crawling you need to walk and then eventually run keep the learning curve going if you haven't had at least one line updated you in a profile and last three months you are doing something wrong lesson five build your network when she was born she would only cling on me eventually she started knowing her papa now other family members and the neighbors also for a professional this is probably the most crucial learning always build your network no matter what domain you work for it will always benefit you networking will help you to know the new technology testing method or a job reference let's be honest the more friends you have the more toys to play with lesson six automate redundant task so lala wise earlier we used to sing to her trust me it was tiring and time consuming eventually we created a playlist on Alexa it's now simply putting her in her cradle and asking Alexa to play similarly use automation to for regular tasks focus more on automation it will not only save the time but keep your energy and of course reduces the manual error last lesson plan the next one at the right time she is only nine months old and we are already been pressurized to have another one what I learned here to make sure there is sufficient time between the two releases this will ensure you to get the time required to plan and process your project bite only what you can chew so this is what I learned from my nine months old and I will learn to know your thoughts on these things so please reach out to me if you have any thoughts on this you can reach out to me at kkatare.com thank you so much awesome that was very wonderfully put thank you for that we do have one question so I'll quickly read out the question actually it's not a question says good one content nice correlation with baby with the testing practices so thank you so much it's more of a all right if there are no more questions then I'm going to move to the next person thanks again Kanchan for bringing that correlation and some of the lessons learned from parenting so the next person we have is Sudindra so good morning also today like I am just going to give you a quick demo of like how we automated both the network mobilization flow in a single test and how we also achieved parallel testing for the same using beauty framework okay so before we start right so I want to give you a lower view so that you can relate the same and more development application in your testing okay so we are actually a website like maybe actually have tax consultants who submit the taxes on behalf of their clients send a link to the taxpayer who then signs it back so here right so one of the problems that we had is that the link the we introduced this new website and then the link that was at the taxpayer right so the taxpayer had an option to open the link on a mobile or a laptop or a tablet okay so when they did this right so there's a lot of bugs coming out because like each one we're using different configuration pro at the screen size was different okay and then we were all looking for a solution because one part of our pro is happening in browser then but the client who is using our documents is using a mobile device or a laptop right so we don't right so I'll just give you a framework overview right so what we use to implement this is like we have I'm going to show a demo where like yeah I have used spectro spectro is nothing but same for combo for total framework and we have used dotted code and then seven a.m. running on chrome with chrome depth so let's go to the demo so so this is a really test which we have written this is just a showcase like how you can achieve the same if you face a similar issue right so what I have done here is that like I'm just going I have just launched a Google here okay so this is my web page right so now right so my test is already running just to just for the sake of time right so now what I'm going to do right so I'm going to now you can see the screen here right so the screen is now going to change the size to an emulator right so the main issue that we had with the customers is that like few of the buttons are not visible and they're not able to process for them right so with implementing this selenium for chrome depth tools right so on the same browser right so we were able to do this enter process under enter flow and still achieve our test coverage okay so here like I'm just written a small test where we are checking the title of the web page and also to make sure that if it has a text called gmail okay so this is this this is how we implemented it and here one big advantage of using VDD is that like you can just pass the device name and in the back end you will be able to pass the sizes of your devices right so so that like you can run all the tests parallely and we don't need to bother about time taken for our execution okay so I'll just do the last slide so what are the benefits out of that right so we were able to test on wide range of screens and devices and then we started looking for a solution we were actually looking for mobile emulators and it was very complex to do that and we and if we had gone for the mobile emulators we would have got into a new creating a new framework and then implement the same but here we didn't do any change which was a small change in my existing framework and everything started working right and we are doing parallel execution as well so this is something that is going to save a lot of time and have good our way or on your automation so yeah so that's all from my side thank you everyone and thanks for sending me for such a great tool perfect all right thanks that was fantastic I will and I think you can share some of the links here in the chat so even in case it's okay I can see Bhargav has joined hello guys are you able to see us let me share my screen yes we see two in a box yeah thank you everyone first of all thanks for giving us opportunity good morning everyone Myself from Yusuf from consberg digital Myself and Bhargav went to present this and three minutes for sure the topic is how to connect non-dot-net frameworks to azure devops test plan basically there are a lot of requests and the open source community selenium and even non-selenium javascript java java python but this request has not been addressed out of the box it's not even today available out of the box so we tried our part and tried to just share this solution to the community so this is just a quick worry of the solution where you have the full stack automation is available in the form of test cases in azure devops api ui mobile whatever cloud related so the thing is we run let's say selenium java and then we generate the allure reports we have created on intermediate dot-net project because that's what natively supported in azure devops now we are reading this allure reports metadata required data for integration with azure devops test plan using this dot-net intermediate project then we are linking the test cases with the test written in dot-net intermediate project to the azure devops test case okay then we run the test and get the results updated in real time there in the azure devops test plan that's it on the solution part now varga will take it let me show you a quick thing how it works so i have a selenium example selenium java project which has the allure reports after the execution so i get the suits.json so if i clearly explore the suits.json which will have the high level of my test case names and then it's a highlighted status and a uid for every test case now i take the uid and go back to the test cases folder in the allure reports and explore what exactly happened with my test cases like if something has failed i see the status phrase and everything has been captured automatically by the allure reports now here where our idea came into picture so we take that allure reports and build this intermediate project in the dot-net solution which reads from your test reports after the execution and we just have these abstract methods at every test case and then we just do the assert dot assert equal for every test case name and then when there is a failure it will also read and upload the exact stack press over there so now after that there is a process of connecting your abstract methods from the visual studio to your azure test plan it's in the microsoft documentation we'll leave the links and once you connect like that so it's like a dot-net based project and you just like run from your test plan by using the automated test suits so we already have the pipelines that are built for the people to give you as an example and you just select your pipeline and run it so what this does in the back end is it thinks like we are running the dot-net based solution and it will give us the results back so when something fails you will also exactly see the error stack press that is being generated in the aluted reports so we are just mimicking the dot-net based project as like to integrate with the non-dot-net based solutions like selenium with java protractor web drive rival playwright or rest assured whatever it is if you are using aluted reports then the middle project that we have built in the dot-net is for you actually so for more details you can either contact us via linkrin or we will share you the sample project link as well in the q and s that's also more to your marriage perfect very interesting i think personally i have you know used you know azure devops and i do know that there's a lot of challenge so this could be quite handy for people so please do share the link in the chat once you're done so that people can get access i think there are a couple of questions for you there is one question from sudindra who's asking does this support only lower projects yeah for now our solution is like in the aluted reports we see it's very straightforward to read from the aluted reports and update in the solution but if people are interested and if we can get some contributors we will make it available for every kind of reports actual for extent reports or any other reports so we'll just make it as a full-blown solution and we're also looking for some contributors so right now we started with alute but we can utilize it to use just fine jason wherein the we can not the alute report the details record details will be made available in jason and integrate using that perfect perfect all right thanks i'll quickly take one last question which is from vishnu he's asking can we attach screenshots in the test results uh we are having that in our pipeline actually so we will be developing that functionalities as well in a month actually that we can hope we will build that as well so we read the screenshots from aluted reports and attach it so so far we're only attaching this status but not the screenshots but we have the plans to develop this for the for the next actually awesome all right thanks barker when you surf i was a great presentation uh and please do share the link thank you i'm going to move to the next person so i think the next person on my list was boon i think i will come back to boon hi guys thanks for this opportunity quick introduction i am boone kapoor working as a lead qa engineer at go to financial i will walk you through the low maintenance contract contract testing approach it is more of a quality delivery related process rather than a demo so coming to integration test versus contract test during integration test we end up testing the integrity of the system from a functional perspective whereas in contract test it is usually the interaction between the services that is under the test we have to make sure that it adheres to all the basic set of expectations that you have set for these contracts what you need to make sure in this approach is that the services are loosely coupled and these are independently deployable as well when it comes to the advantages the advantages that we have over the usual integration tests it is language agnostic where abstraction can be written at in any language it is also environment agnostic it is easier to maintain with multiple api documentation integration that you have available in the market it is faster testing method for independent services when it comes to low hanging approach where you might just have optimizations on top of certain set of releases how do we go about it so development can follow a contract first approach although it is not mandatory it's just that the contracts are available easily you can also follow a service-oriented design as well once you have contracts available in jason or viamen what you can do is you can use a generator or you can independently create a documentation which might help you out in testing we basically perform a jason schema level validation along with basic assertions on top of the contracts so there are multiple tools which are available in the market around api specifications documentations as well as the contract validation in multiple languages in multiple libraries so this is how it goes about at the abstraction length you create producer or the consumer contracts you create an abstraction layer for the sending logic bit for the apis and once you send the request to the service try to store the response that you get back and the code for the basic assertion set then you validate the schema and your expected set of validation and once you have collated the result what you can do is you can move towards the cd side and depending on the result you can either push and deploy it or you can send an error message as a web to your services around the service testing flow over here what you have is we have a single producer service which has multiple consumer service these consumers can be anything it can be multiple set of microservices or it can be a consumer client as well it can be a front end it can also be dependent on another consumer service in this case the producer would become a consumer but it's for simplicity imagine if there are two consumers which are consuming from and you had a minor set of optimizations where you would not want to test the entire regression flow or the sanity flow what you can do is you can run the contracts for the same once these have passed you can initiate the delivery process or if something would have failed you can just send the error message back let's say if there are two services which are being changed around the minor optimization bit of it then you can run the contract for both this this producer service as well as this consumer service which is dependent on this producer and then once all the tests would have passed and the contracts have validated you can just initiate the delivery process so this is the approach that we are currently trying to embrace in the commerce enablement vertical for the go-to for low hanging releases as of this point of time so I do have other set of documentations prepared but had to keep it restricted for three minutes so I'm reachable at these places thank you for your time over to you and Arish. Okay great thanks Bhuvan that was a good quick overview of the contract testing tool that you have is this thing that you've built open source is it available online somewhere? No it isn't open source at this point of time we are working towards organizing and open sourcing this entire thing. Cool cool okay awesome In fact anyone who's interested there's also today a workshop a 90-minute workshop on contract testing you know kind of you know if anyone's interested in this topic just thought I'll highlight that. Is there any questions? I don't see any questions as of now Cool I think we have a little short of time so we will move ahead thanks again Bhuvan this is a great demo and kind of explaining the concept of the difference between contract testing and integration testing so thanks again. Next up is Preeti all the way from Singapore thank you. Okay thanks Naresh so hello all very good morning I am Preeti working as a lead QA at Property Guru Singapore. Property Guru is located in different parts of the world including Indian Joe so just feel free to scan the QR code for any interesting and wonderful opportunities if you guys are interested. Let me just move on my talk today is about reducing execution time of mobile UI functional tasks there are many ways to achieve that and I have chosen one of them which is using deep links so let me begin with the situation now so I'm sure whoever works in the test automation of mobile applications this situation might sound similar to them one of the hapless realities of mobile test automation is the speed limit tap takes time keystroke takes time and waiting for animation and if there are any data to be loaded from the network again further increases the time so making the mobile UI functional tasks faster and as closer to real life as possible is a real challenge so let me put up the problem here so I have taken a mobile application where there is a home screen on tapping the search it gives the search results screen and tapping any of the listing here it takes to the detail screen so tasks in this detail screen relies on the same starting point then it becomes a big problem because it has to go through the home screen followed by the search and then the detail screen where the actual test begins okay so let me come up with the solution which I have chosen today which is deep linking so you all know that as most of you know that deep links or the special URLs that can be associated with specific applications the developer of the app registers a unique URL scheme with the OS and from then an app will come alive and will be able to do whatever it wants based on the content of the URL so to reduce the test execution time this is a sample implementation given by my developer so he has added a switch case and for each of the screen which the test automation requires and requests for he has added a case here so let me move on to the automation side so I just added a comparison of how a feature file or a spec file would look like without the deep link and with the deep link so without the deep link there are three steps required and with the deep link it's just a single step and thanks to the app I am with just a single line of code we can just open the URL which is the deep link customized URL and I have used web driver I work framework here so for which I have given the command browser dot url but if you're using a direct apm integration it would be driver dot get so moving on I've just added a simple demo of how the task would look like with deep link here so it just goes straight to the detail screen but without deep link it's going to through the home screen search and then the detail screen so as you can see here a rough calculation of like if it takes 10 to 15 seconds then if you're adding around 50 test suites in the regression flow then like I have already saved like approximately 13 minutes of execution time here so I'll just conclude my presentation here like apart from the test execution time saving there are some quick wins as well like avoid the flakiness like if you repeatedly go through the home screen and the salt screen for example so there are like you are exposing potential flakiness which could eventually make the test fail and also if there are any onboarding prompt or alert messages you can directly skip it because you're already bypassing the screen so that's it with my presentation thanks for the wonderful opportunity selenium confidence so feel free to ask any questions if you have and thanks again great thanks pretty I think this is quite useful we do have one question so Nick is asking I guess this is only possible for hybrid apps such as corvada based apps instead native iOS apps please confirm okay so for others native as well basically I mean it applies to all the apps because even the demo which I have put in is a complete native application so it applies to the native application supporting both iOS as well as android and we do have react native application which also use deep link cool just take one more question here not sure if this was discussed but can we bypass a login scenario I mean yeah I mean you can bypass the login scenario if the application supports in fact we have a b2b application which which includes authentication in every request so we have worked with the developer to come up with a customized url adding the auth token as well but just to remind like deep links you have to use it with caution because you can't apply the same you know bypass in the production app as well so make sure you're adding it in the debug configuration or the automation configuration perfect I think Ishaan has one last question which I think you answered he's asking is it possible for iOS apps as well yeah absolutely because the demo I have put in also applies to iOS app as well and we are using it perfect I think yeah again Preeti if you have any links to share you can put it on the chat folks will reach out to you so I'm going to just take this opportunity to quickly kind of I think we have 10 minutes left so we're gonna quickly go through and some of the important points from yesterday so I do see a lot of people are rating the session so first of all thank you for doing that religiously it's greatly helpful and we appreciate that so you know please continue to do that today as well to rate the session so it allows us to get the feedback as you might know the videos a lot of people were asking again about the videos video recording because we're not able to attend parallel sessions so a lot of the video recordings in fact if I'm not wrong I think 14 videos are already live from yesterday and more will be coming in the in the days to come let me also share my screen just so that we can see that so this is about the videos that I was talking about so you know you can go to YouTube convention you will see the videos in fact a lot of videos from yesterday are already uploaded so hopefully that should be there I talked about reading the session so thank you for doing that I do want to thank again all the wonderful speakers that are at the conference we see a lot of people are watching the tables but not really joining the tables you know it'd be good if you can join the table and have conversations with the speakers it's a great opportunity to network with the speakers and other attendees so do leverage this you know I want to quickly jump ahead I do see people using mingle but I think there's quite a few people who are saying I'm not getting any response back so you know please do check your mingle to see if someone's pinging you and do respond how many people use the law of two feet can I can I have a quick show of hands how many people use the law of two feet okay okay I see quite a few people so that's that's good hopefully this is a good use of your time in terms of making sure you find the right section for yourself and leverage that I know a lot of you have visited the booths and stuff like that but I just wanted to again give a quick reminder that today you know end of the day we will be announcing these winners who will be winning these goodies from the sponsors so please do visit their booths and claim these goodies a lot of them I'm just rushing through some of these things but yeah I'm sure you've had a look at some of these and if you've not visited so far then take the opportunity to meet them again I want to thank the program community for doing a wonderful job in putting this program together and the volunteers who are working to make sure that this conference is running smooth and seamlessly and the convention team that has actually built the platform and helped put this together so with that I think I will quickly stop I just wanted to highlight some of these things are there any open questions that you have that have not been addressed so far you know if you can just please ask them I'll try and address them we have another five minutes hopefully you guys all enjoyed the lightning talks I thought there were good comments in the chat at least positive comments so I hope you guys liked the lightning talk format is like short crisp three to four minute talks we were able to cover seven of them today and I thought there were some of them were very interesting from different different perspectives so hopefully you guys felt the same okay if there are no more questions that's a good news which means everything is clear and everyone knows what to expect so thanks again we will see you in the evening again when we meet all the not all but subset of all the committers we will have a panel for the committers and we will see all of you again in the evening with the committers so thanks again and everyone have a good day and see you shortly bye