In many cases, I have had to team up with new solutions and play around with code on my own, which has been a great learning experience for me. And what I've learned is that not everything is that easy to automate. Once I get an application, any application whether it be a WAVE app or mobile app, I very much enjoy getting stuck into the automation part of testing. My biggest lessons while using Selenium have had to do with automation and how it really works, which is something I've always been interested in. There's a lot of support for different programming languages with Selenium. As for myself, I'm using Java, but you can use C#, Python, Ruby, PHP, etc. You can use any programming language you prefer. Develop from any framework, use it as best as possible, get some experience with it, and try to become an expert from there. Then, take a piece of code and ensure that it works as a standalone script, then finally jump into the framework. For instance, before jumping into it from the deep end, try get a handle on a few small steps first, and as you go along you will learn the basic coding, the basic architecture, how Selenium works, how the automation process works, and so on. And in that case, my advice would be to first understand the logic of the process. If you only have manual experience, like a lot of new testers, then you likely don't have much experience in coding either. My advice to others is that, first of all, you have to understand the process of automation from a general point of view, and how people get on with the coding and all that. So, ultimately, more support for non-technical people would make for a great improvement in Selenium. With SoapUI Pro, if you want to fetch some data, you don't need to write any code or anything, and for someone with no coding experience, this makes it much easier to be able to use effectively. If I can compare Selenium with another solution such as SoapUI Pro, there's a big difference when it comes to coding your own solutions. It also makes you rely on your problem-solving skills to a large degree, because some problems are not that easy to solve by yourself. In this case, you have to rely solely on your own coding experience and exposure to the tool, and you often have to search through many pages of code when you want to change something in your implementation. With Selenium, we're using freeware software, and because of this there is no support or anything from the vendor. You could then simply grant access to only those people who need it.Īnother improvement I can think of is in the area of documentation and support. For example, once you have the app credentials and all the other security data and you don't want to show them to other people who are not authorized, a repository for this kind of data would be very useful. In future, if they can provide an object repository or some kind of repository for data, then that I would greatly appreciate it. One drawback to Selenium is that there is nothing like an object repository, such as that found in QTP, especially considering continuous integration practices that have become common nowadays.
0 kommentar(er)
