 So, I am going to attempt some magic here today. I'm going to go through 42 slides in 3 minutes and I'm 10 seconds down. Soap opera testing is a dramatized effort. It's a business engagement activity. It's condensed in time. You can engage your business, the history of the term. Chen Khanna originally coined the term scenario testing back in 2004. He's a serious looking tester dude. We have Hans Verwalder, also another serious looking testing dude who coined the term soap opera testing in 2006. So what is it, the process? You might go through, you might start with a brainstorming activity with your business, your sales, you might ask them, what are the stories our users have done? What are some of the most amazing things that our users have really tried to do? Where is the drama in our product? You execute the exercise and then analyze the results. You might want to redo it again. For example, we're going to use the Simpsons with a mortgage loan application. So as a home assistant comes into a bit of money, he wins the lottery and he's going to apply for a second loan as an investment property. Unfortunately, his father, Abe Simpson, lives in an apartment and it birds down. So he's a bit down on his luck. Homer goes in and he signs, but he's not all that literate. So he signs it incorrectly. He's signing up for an investment property. His application is declined because he doesn't have a good credit rating. Flanders next though, Oh Deadly Dough, the neighbor, comes in and says, I'll help you out with your application. I only put down a 10% deposit, but most of my house is mostly paid off. They'll just help you with your credit rating. Flanders has 90% of his house paid off. He's putting down a 10% deposit. The Simpsons have their house is 50% paid off and they're putting down a 90% deposit. So they go into the bank, they arrange all the paperwork, but then Homer's brother comes along and he's like, I've got an investment property. I've got an investment option here. Nuclear powered cars, they're going to be the next thing. They're going to be all the rage. Just give me a bit of an investment and we'll see it grow. So Homer has to go in and readjust his down payment. What did we just test? We tested rejections. Homer was originally rejected with his first application. He had to re-edit his documents because he mis-signed his name. We had multiple applications for the same person. We had to adjust his deposit after the application had gone through. Multiple assets with different mortgage amounts and different percentage ownership. We also had the two owners of the property, not located in the same address either. They also had different credit ratings that fed into the different algorithm that would have gone into their application process. The co-owners weren't related and we're signing up for investment property. Here's just a big list of all the possible things we could have tested in that scenario. Amanda, I imagine how many bugs we would have found going through that process versus creating just the standard case case walkthrough. So have fun with testing and tell me about some of the dramas. You've seen in some of your testing before. Thank you. Sorry folks, I just decided to talk here. I don't have any slides to showcase you. So can I start now? Yeah, so my name is Rakesh Kumar. So today I'm here to discuss small about things about accessibility. So we have been testing the application functionally a lot. We are caring about if a user having valid credentials, he's able to enter into the homepage and doing NFM number of activities. We are only concerned about those kind of activities. And sometimes we are more concerned about some of the activities like non-functional activities like security because billions of dollars we are exchanging it, right? So we are concerned about our security. And sometimes since during the sales, so many people are accessing your application. So you are very concerned about the performance testing. So we are just caring about where money is inside and all, right? So there are other things also we need to care about. So from a minority point of view, we need to make sure that every web application is accessible by everyone, right? So that's why we need to do accessibility testing. So you do accessibility on the test, accessibility testing on product and make sure this is accessible by everyone, even though the people are having special needs or are differently able. So I'm here, I'm doing accessibility testing in my arc. So I implement manual ways of doing accessibility and some ways of automating the same flows integrating with Selenium. So from developer point of view, so being here, we are here not to find the defects. So if I, any person asks you, being here, you are here to find the defects. I say, no, I'm here to prevent the defects from initial phases. So how to prevent the defects? You talk to your UX developers. You talk to the normal developers who design front-end backend. So what I would like to say is for the UX developers, design something which makes the UX developers follow WCAG standards. There is web content accessibility standards. You follow those things and there are some levels like AA, AA and AAA. You follow those kinds of standards and successful criteria. So now here comes the picture. How UX can help you? So UX, they're developing all the things, right? Make sure you have color contrast things like foreground colors, background colors. And when they design the wireframes itself, make sure there is a label whether there is any title associated or not. So you make the UX resources aware of all these things. Then comes the picture of developers. You go to them and say, hey developers, while writing your code itself, you make sure there is an alternate text which is available. So if some persons are using screen readers, make sure they can read it. And if you are displaying some video out of it or if you are displaying some slides so that you can maintain all the captions around it. So what I would like to say is make sure that web is equal to everyone and accessible to everyone. So start doing accessibility testing and enhance teams. So there are so many plugins available like color contrast analyzers, A checkers, HTML code sniffer and acts. Try them and make sure your applications is accessible to everyone and makes the whole life easier. Thank you. So I start. Yesterday I did a presentation on PR, how to do VR testing in order to prepare for this presentation. I actually created the room that I was going to present in VR. I've never been here before. I only asked for a few pictures of this room. This is the goal, the end goal. So in order to do this, the first thing I did is that I took pieces of the room that I wanted to use as texture. For example, the floor. I created some PNG image files for these textures. Then I went to, there is more, but I went to Unity, I created a new project. I created a new 3D object plane. Just right-clicking literally. I created also a new material. Same right-clicking but down instead of the left. I added in the Albedo property, I added all these PNGs for all the materials that I wanted to have. I added the material to that plane that I created before. Boom, I have the floor. I did the same exactly for the walls. I also created some cube instead of planes to create the effect of 3D. And that's how my first wall look. I add some lighting as well. I repeat the same for the other walls. I add the doors. Then I don't add some objects from the internet. They're free for downloading. If you look for 3DS objects, I don't add the chair. I get some people sitting down. Main issue, these old people are really white, so I have to change a little bit their skin to match with the audience that I'm going to have and make them look kind of a little bit more Indian. In this case, I don't know if I did a good job, but I tried my best, sorry. And then again, I add the projector. I add my slides to the projectors and I add a little bit of code to be able to change the slides. In this case, I add a new component on the right. There's an option that you can see down there that is add a new component. Even trigger, point the click and when I have the click, then I added a little bit of code that looks like this and it just changed one slide until the other and when you reach the end, it goes back to the beginning, very, very easy. Then at the beginning of the script, you can see all these public properties, all these public properties, then after look like this thing on the right. So you'll see the list of the different slides and I add one by one, this is drag and drop literally, you get the slides there. So then I have this as a final product. You don't see 3DS because it's impossible for me to show it unless you want to use the device, but basically you have a 3D version of the room that you're gonna be presenting on with people sitting down and with your slides that you're able to change. I wanted to just quickly show you a thing that you can do to practice public speaking and to have fun at your office, get your people together. It's called presentation karaoke. So somebody, actually I'm gonna look at Nomi, give me a topic title. I will do a talk on that topic. Guts, guts, guts, okay. I will talk to you on guts today. Let me if we start this with the, shouldn't do this before I get to this, so. Hello, I'm gonna be talking about guts and I'm gonna add guts in testing because we're in testing conference. So you know, when you're thinking of guts and having guts, there's something, complicated scenarios like the ones that Samantha was just talking about, you know, the soap operas, maybe that, takes some guts to bring into India testing. But that's not the only thing that takes guts. So let's see what comes next. You can put guts together with just about anything, guts in scenario testing, guts in selenium, guts and whatever. Use your guts, use whatever you have, be brave about doing whatever you're doing. And you know, you might want to use some, maybe external motivation as well and you know, external motivation like money, might make sense. In addition to money, you might look into things like, your blood would kind of surprise me, but you know, it takes guts to bring your whole self to whatever testing you're doing. So as a final note, I wanted to mention that in thinking of guts in your testing, you might want to compare it to something very complicated, something a little simpler and you know, it takes guts to take a look at either one of them and approach them from a testing perspective. So the idea with what we just did is, I do not know what is the next slide. That's called presentation karaoke. Get a topic that you have and do a talk on that. There's no other way than failing in some way, but usually you fail in an interesting and funny way like I really didn't expect to see 80% block here. So thank you. Hi everyone, good afternoon. Am I audible? Yeah. So I hope everybody must be aware of Bitcoin these days. Bitcoin, blockchain, decentralized technologies. So before going to my topic, which is about implementation of blockchain in the industry, which a company named Great has implemented that. I just want to add two lines for the blockchain. It is something like on which we don't, a single entity or a group of people don't have control over it. A community controls it and it's public. So no one can go and change it. Everyone can say it. It's anonymous. You cannot see what changes have been done by someone else. Yet it is public, but everyone can say this. Changes are done, but who has done it? We don't know. It is DDoS free, DDoS resistant. You cannot attack it. You cannot hack it. These are the advantages of black blockchain or decentralized technology. Blockchain is one of the decentralized technologies. So there is a company called Great in the United States. It's a sneaker company, Shoes. And the problem statement was the parallel gray market was running and for the counterfeit products, they were making shoes and they were like putting a lot of money in the R&D. But once the product was launched, after a few days or a few weeks, the counterfeit product was in the market and they were facing a lot of losses due to that. These are the few statistics. 600 billion worth of counterfeit product in the fashion industry itself. And out of that, 40% of the counterfeit products are in the sneaker industry, only in the shoes industry. And 100 million worth of sneaker shoes are getting seized by U.S. customs every year, which is a very, very less amount if you compare it with the $240 billion. So what is the counterfeit problem? People are doing like putting so much money in the R&D but they're not getting value out of it. So due to this, the price of the product becomes very, very higher and it becomes difficult for us to buy this. What was the solution? The traditional solution a company will make where something like it will make the manufacturing process very difficult so that it is very difficult to counterfeit. They tried that instead of counterfeit product getting into the market in seven days, 10 days, the counterfeit product was getting into the market in 15 days or 20 days. But yes, the counterfeit product was getting into the market. Material science, they tried to change the product, the material of the product. But again, it is very difficult for a normal person to check if this is the same material, if this is the original material, everyone cannot know about it. Everyone don't have the knowledge about the material. After that, they came up with the authentication certificate or some kind of barcode but these can also be replicated. So then they came up with a solution of blockchain in which they just had, I hope everyone is aware, we can only have 21 million bitcoins. We cannot generate more than that. If you lose any of the bitcoins, you cannot regenerate it. So they used the same concept. They said for our new product, we will be having only one million shoes available. These are the maximum number of shoes they will be having and they attached an address to each and every of the shoes. They tied up with the two companies, Chronicles and some other company, I don't remember the name. And after that, they created an NFC chip. They baked their chip into the shoes and they created an app. Now, if you scan the shoes, they will just tell you these are the shoes which is in our one million pair of the shoes. If this shoe is not available in our one million pair of the shoes, then it will reject that shoes. Like this is a counterfeit product. So by this and if you try to replicate that NFC code into the shoes itself, then just 30 seconds. If you try to replicate that NFC code in some other shoes, then if you try to scan that specific shoes, then it will show you a message. Like this shoes was available in US, the United States, but how can this reach to India before, sorry, before, like without intimating us. So it stores all the information related to that specific address, which is the shoes actually. So that is how they stopped counterfeit of their new product. Hi, I'm Sridhar. So today I'll be speaking on a tool to mock the responses. So like we all work in micro environments, microservices, distributed teams. Like we are dependent on the output of some different team. So we can't afford to wait till the development of that team is complete. So we need to mock the responses. And also as a QA we need this. So I work in a travel domain where like if you have to test some of the UI or some of the error codes when there are some trained disruptions or some cancellations, then we can't afford to test it in production. So we have to mock the responses. So I'll quickly show you a tool. So we're using which we can mock in one minute. Okay, so this tool is called wire mock. So it's just a jar file. You need to just run it as a Java FNJAR and wire mock. So that's how you have to run. And if you run it, there are two folders. So this is the directory structure, folder structure of this. So there is a mapping file and the files. So mapping just shows like what is the, like this is a condition for me, like what condition I should do the mock. So in here I'm saying if my URL is v1 slash mock, then just return whatever is the content of mock.json file, right? And also the status code you can also add what the server headers you want to send. If you have to set the cookies from the server, then you can add that. And if you have to allow only a few origins, then you can add it. Like there are multiple options to it. And also this is the request. So I'm just checking the URL and method is get. So if there is a get method with URL v1 slash mock, then return me the content of mock.json. So this is what I'm doing here. So if you see the mock.json, so the mock files are there in the files folder. So if I just open this, this says username valid json file. Okay, so I will just run this. So I'm just running the wire mock server here. And by default it's started in 8080. And when I hit v1 slash mock, this gives me the username and password which I have stored in the mock file. So there are multiple options for it. And this is a standalone file, just java-jar. And you can just run the jar. You can put it in your EBCS and add a build step in your pipeline to start the mock server. So as simple as that. So there are multiple ways to do the request matching here. So just a second. So you can do it using Java or also the json which I have showed here. So you can also add say the some conditions, some star operators or some regular expressions just to match the request and responses, to match the request so that you get a proper response. Okay, so I think this is a very handy tool. It will be useful for on our day-to-day purposes. Yeah, thank you. Hey guys, I'm Tomak, I'm from Poland. And I'm totally not prepared. It wasn't planned. But I want to tell you about two things that we are using in our Selenium framework that makes our life really easier. First thing is email testing. We are using in-bucket. If you are familiar with any temporary email service, in-bucket we can set up locally and use any email at webpage, as plain HTML. So we can implement it as page object pattern and just run Selenium tests around it. If you want details, I'm happy to share after presentation. Second thing is the way to monitor performance in easiest, fastest and cheapest possible way. Every modern browser has something like navigation timing API. It's building, you don't need set up anything and you can save data from this, like DOM ready, like when external sources for web page are downloaded. And we can push this data, for example, to Elasticsearch and later to Grafana to have beautiful view how performance of our site is going. Set up is literally like five lines of the code. So you can, without any additional framework, without any additional tools, set up performance monitoring in your company. Like I said, I'm happy to share details after. Originally, it was a topic for two hours workshop. So yeah, I have something to tell about this. Thank you. Thank you very much time. But how many people are facing challenges with data generation in test automation in your companies? Nobody? Yeah, people might be facing, yeah. I understand that. Because I was also facing the same kind of issue. So we come up with a way of generating application specific data, random data, so that we don't need to go to any library available in the online to just play around with it. You can generate your own data in your own way. So for example, I can, I want to show you a piece of work which we have done. So you can see a data folder here and the text files over here. So these text files are contains the random data and you can create any text file with the data which is specific to your application. For example, in my application, I had a field which required questions, some kind of fact or questions. So I had added a file with questions inside this folder and by simply defining function called getQuestion, I will be able to read a random question out of all the questions which is in the file by using this function. Similarly, you can define anything. For example, if you want to get in any medicine name, you can create a new file here with the name medicines.txt and define a function there. It will pick up a random medicine name from this file and put it into your test cases. Now another challenge which generally people face is outdated data. So for example, if you have a URL and in the next release your testing URL has changed. How do you manage it? The best way is the common way is just go to your test code and change it from there. But we have to find a new way which is by defining it into the Excel sheets in such a way that by centralizing your data, so that whenever you need a change into your data, you just get into the Excel and change it from there. Now another problem decides is that if you are using Excel, then you would have to commit Excel into your code base also. But to solve this problem, we have also come up with a library called Read Excel Anywhere. This library actually allows you to read the Google sheets or SharePoint Excel sheets or your local sheets or other like open text kind of Excel sheets. Any Excel sheet which is there in the market, this library allows you to read it by very simple configurations. For example, if you want to read Google sheets, you just need to have the Google sheets resource ID and your key and that's it. By these two parameters, you would be able to read your Google sheets and it will return you the sheet data in a very simple format like a map or a list which you can further use it into your framework for getting the data out of those sheets. There was a requirement that most of my team members are manual testers and SMEs. So we wanted to have a framework which enables you to do creation of easier automation test suite and a test suite which can be collaborative. We wanted faster test executions and easier maintenance and the major hurdle which we had was our team was geographically separated. So I was working from Mumbai and my team from Ukraine and other team members were in the US. So to meet those requirements, to fulfill those requirements, we created this framework. Now what exactly we have built? So you must have heard about a term called BPT, it's called business process testing. Anybody who would have used UFT or QTP in their past, they must be aware of BPT. So this framework is a combination of BPT, that concept, some concepts taken from cucumber and some concepts taken from keyword-driven framework. Now putting all this together, I have created a framework which is code-less by using simple Google Sheets because Google Sheets is well-known for collaboration. And you can test your code, you can test your test cases also, you can execute your test cases without checking your code to get our SVN. Now, how does it work? I'll talk about it. As you can see, can you see it clearly? I hope so. Okay, I'll try to make it bigger. All right, this consists of only three sheets. First is test case sheet. You can see that a single test case, if you see over here, it looks like a scenario, a cucumber scenario. It simply says related user, customer, user can login successfully. And on the right-hand side in the business process column, you can actually see business processes. Business processes are nothing but reusable components which you think can be reused across multiple test cases. You create business processes thinking about that. You can see there are simple business processes like user navigator login page, enter credentials, and user is on the homepage. So with these three business processes, I can actually validate and test this particular test case. And the best part of this framework is that you can write your test case in any language. You see, I have written it the same taste in Spanish language, in Hindi also, and in any other language with Google Sheets supports. And talking about the business processes, this is another sheet where you actually map your business processes with the sequence of actions which is responsible to perform that action. Like, as it says, user navigates to the login pages. So you can decide upon the actions which creates that business module with the right set of parameters. And the last sheet is the locators sheet. So at last, I just want to say that this framework allows you to collaborate without installing anything. You just need to have the access to those Google Sheets and you don't need to have to access to your Jenkins or Bamboo, wherever your framework is installed. And by just hitting build button, you will, that framework is going to read all these Excel sheets on Google Sheets and it will give you the reports of if it looks something like this. So I have extended the extended report in a way so that it can support my framework. So if you can see here, its report is very clear. It has all the dashboard stuff. And by simply looking at the reports, anybody can understand what this test case is doing. So it makes it more apparent, more helpful in understanding your business. And it helps the developers and testers and SMEs to collaborate together because we are not talking about functionalities more rather than just writing the code, right? And I just want to show you the demo. So this is what I wanted to showcase to you guys. This is called, I named it as Automatica and you can use Google Sheets just to write your test cases and manage it from anywhere. Thank you.