Jyothirmayee Pattem

Hi, my name is Jyoti. I'm currently working part-time at Pro Technologies. I have four years of experience in automated testing, along with manual testing in some cases. So we can consider it as having four years of experience in manual testing as well, in Appium and API testing as well. I worked on a BDD framework and also POM framework. We worked on data-driven testing and a framework. We used your CICD pipeline, Jenkins, as the CICD pipeline. We used Git as a version control tool, and currently, we're working in an agile model. My daily activities are, firstly, I need to log in, and then I need to attend daily scrum calls. In that scrum call, I need to explain what are the targets, what tasks I've done yesterday, and what tasks we have to do today. This is how I spend my day, and this is my brief introduction about myself.

What are some best practices when writing Erkin test scenarios to ensure clarity and efficiency in test automation? Some best practices when writing Erkin test scenarios are for first, we need to understand the test cases we need to write and for which conditions we need to write the test cases. And, we need to understand in which programming language we need to write and what are the conditions we need to take later on. The main aspects are clear and concise language in which we need to understand in which programming language we need to write the code and we need to write in a very simple terms because BD is a framework which is designed to be understood for both non-IT and IT candidates. In this BD framework, we'll use very common English words like given, when, then, so that non-IT people can also understand very easily. Firstly, to write test scenarios, we need to understand about clear and concise language, and we need to check for prioritization. I mean, which test scenarios we need to write first and what are the first priority? And we need to write prioritization. We have to manage the test data, perform negative testing, perform usability testing, perform retesting, and perform regression testing. These are the best practices. And first, we need to check for test coverage. I mean, we need to check all the conditions for all the scenarios we have covered the test case or not. And we need to check the automation framework and continuous integration and continuous deployment tools. Like, it is running the test cases automatically or not. These are the best practices we have to take while writing check-in test scenarios to ensure clarity and efficiency in test automation.

How do you effectively set up and use a local mobile device testing grid for parallel test execution? To effectively set up and use a local mobile device for parallel test execution, first, we have to choose a mobile automation testing framework, such as Appium or Selenium Grid, which we need to use. Most of the time, we use the setting just because it is open source and doesn't cost anything for installation. It also supports multiple languages, like Java, Python, and C++. So, most of the time, we will use only Appium as the tool for testing. To effectively set up, first, we need to choose which framework we need to use, and later install the required tools, such as Selenium Grid, on our local machine. After that, we need to connect our physical local mobile device and our emulated device to the nodes. If you are performing testing on a local mobile device, we need to connect the device to the nodes. If you are performing testing on emulated devices, we need to connect the devices to the nodes. After all that, we need to configure some test scripts, regarding our project. We can perform parallel execution in Appium, which means we can perform the same test case on multiple devices. For example, we have two devices with different versions. We can perform the same test case on the two devices. After that, we need to check if the test execution was correctly executed and check the reports generated using the test engine framework. And this is how we can effectively set up and use a local mobile device testing grid for parallel test execution.

In what scenario would you prioritize the use of explicit over implicit weights within your Selenium tests and why? What should you plot? Actually, in test cases, we will use both explicit and implicit weights. Implicit weight will be used defaultly for every testing. We will use explicit testing in some cases, like if you have any hyperlinks. For example, if you create a web page that contains some hyperlinks, we need to wait until the hyperlink is open to check whether the hyperlink is working or not. If you didn't use any explicit wait for that condition, you'll get an error like the hyperlink was not opening or a page load timeout exception. To get out of these situations, we will use explicit wait. And implicit wait, we will use this default for Selenium tests.

How do you handle dynamic page concept or interactions in Appium while writing test scripts for mobile automation? To handle dynamic page content or interactions in Appium while adding test cases, we first need to identify when the dynamic elements are present. Like, we need to identify attributes such as a class name or its path or ID name by using the Appium inspector or UI Automator. We need to identify the dynamic elements. In Appium, we can identify those elements using the Appium inspector or UI Automator. In the Appium inspector, we'll get all its path and its CSS. However, in the UI inspector, we won't get that information. So, most of the time, we will use the Appium inspector only. To test dynamic page content, we can handle it by using the contains method in its path and CSS. This is because dynamic page content means it will change. For example, if you refresh a page, the elements' identification will be changed. The path for the page will change. So, to get rid of that issue, we will use the contains method, which is part of CSS selectors to locate elements based on partially matching content. For example, contains class names or attributes. By using this method, we can handle dynamic page contents or interactions in Appium while writing test scripts for mobile automation.

When would you choose to use a data-driven approach? We would choose to use a data-driven approach in what key cases. Okay. Most of the cases, we will go for a data-driven approach instead of a keyword-driven approach in mobile testing automation. We will go for a data-driven approach in cases where we need to test some data. We have the data in our external file. In those situations, we will go for a data-driven approach in which we need to get some data from external files, like an XML file or a spreadsheet. From those files, we need to get the data into our framework, and from there, we need to use the data. This is called a data-driven approach.

In the context of data automation, Appium is often used for mobile testing. Okay. There is a snippet where Appium interacts with the Android application. Can you spot the mistake and explain what issue it might cause? Okay. Here, you're finding the it's part by using find element. And in the third line, we create we wrote like element dot click. Here, we need to assign this element or click to a variable so that it will work. Otherwise, we are not able to go to that element and we can't perform this clickable options.

I'd like to point out that the issue here is the way the username and password are being handled in the login method implementation. They are currently being passed as strings, but the speaker is suggesting that they should be treated as identifiers, not strings. I think the issue is that the username and password should be passed as variables, such as `username` and `password`, rather than being hardcoded as strings. This is because they are being used to identify a user, and should be treated as unique identifiers, not just strings of text.

Complex CSCD pipeline. It involves several steps including data collection, data cleaning, data transformation, and data visualization. Yeah.

Okay, how do you use Maven or Ant to manage build automation scripts? Basically, we use dependencies. By using dependencies, we don't need to install any specific dependencies. For example, if you add any, we don't need to add any JARs separately to the project. If you make changes in dependencies, for example, if you want to add a Selenium dependency, by adding the dependency, we will get it and make it available in our project. So, this is how we can use Maven to manage dependencies or build automation scripts.