Is selenium a framework or tool or library. I have seen selenium being addressed as framework in many places if so where is inversion of control achieved in selenium.
Selenium is a web automation tool for testing. it's free. You can build an automation framework by selenium and OOP programming concepts.
For example, you can store data in the excel field inside the project folder
There are design patterns in selenium like Page Object Model and Page factory design.
I am currently working on TestNG framework in which Galen framework is embedded. The Galen Testcases deals the UI part of our website.
I have researched a lot and there is no other automation tools same or better than that of Galen Framework for UI testing specifically.
I am well aware that it can be done with coding Java or even writing testcases script manually in Java itself. But, is there any other advanced UI automation too available in market?
I want this because the report of Galen is such a big size that mailing this report or moving this report is not a good practice(Which makes my CI/CD pipeline slow).
I have an application built on flash and that runs only on Internet Explorer. Sample screen of the application looks as shared. Also, I have shared object details.
I want to know, Can I choose Python language + Any tool to automate. I have browsed for tools like Selenium, PyCharm, Sikuli etc. But not able to figure out the exact tools along with Python and other settings.
You can try Ranorex. We used it to automate Flex application with C# as auto script.
But it's not free software.
I have to do Automated testing of Application based on Flash builder, after searching on this topic i came to know that flash builder includes Testing API's, and these API's supports HP QTP so After Including Testing API's in my application and making test cases Scripts based on VB scripts I can do automated testing, how should i do automated testing of application based on Flash builder.
You should take a look at Flex Mojos, which is a Maven Plugin. You can use it for automated builds and tests as well.
I am looking at some options for using a web automated framework. I have so far looked at Selenium and Web Test (part of Visual Studio), Web Test does not test any client side code, so that kind of rules that one out. Selenium has most the features needed although I need to generate the .NET code for the tests, so that I can run the tests under TFS build server.
Is selenium the best automated testing web framework, or is there anything else worth looking at that could integrate with .NET and the TFS build. Ideally I want minimal code changes if any.
Appreciate your thoughts
Cheers
I've been constantly frustrated with Web Test in Visual Studio, though I'm not sure I understand what you mean when you say it can't test client side code.
For developer community support, ease of use, and cross platform access, I'd say Selenium is the hands down winner for programmatic browser automation. Selenium 2 works on every major OS/browser and even mobile.
I've tried WaitN and found some bugs in recent version of IE. There was a recent 2.0 release that has probably worked things out, but there are so many more people using Selenium it's worth relying on that community.
Selenium can generate C#. You can use the Selenium libraries in a C# class to create a web UI test library. Selenium is probably the most common tool.
Another option is WatiN, which is a descendant of Watir for .NET. It's another web UI automation library
This StackOverflow thread discusses using the two to test ASP .NET webforms, and might give you a good set of concepts to start from. My experience with the two is that they were both nice. I would go with Selenium if working with non-programming testers due to its great record-and-playback tools (for Firefox), and WatiN if working with SDETs / developers due to its richer libraries. When in doubt, Selenium is more common and more frequently used.
I've been using Selenium 2.0 (the C# bindings in particular) / NUnit / Hudson. Works well, and Selenium 2.0 is constantly improving and working out the remaining bugs