Azure Test Plans is an exploratory test toolkit available from Microsoft's Azure suite of services. It enables manual testing for users, so that they can plan, execute, and track scripted tests with actionable defects and end-to-end traceability. Assess quality throughout the development lifecycle by testing your desktop or web applications. It is available with Azure DevOps Services.
N/A
Selenium
Score 8.1 out of 10
N/A
Selenium is open source software for browser automation, primarily used for functional, load, or performance testing of applications.
N/A
Pricing
Azure Test Plans
Selenium
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Azure Test Plans
Selenium
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Azure Test Plans
Selenium
Features
Azure Test Plans
Selenium
Test Management
Comparison of Test Management features of Product A and Product B
It works well for express test case implementation with a short duration. You can define the tests for two weeks and run the activities documenting the software errors and fixes to control the effectiveness of DevOps. The graphic reports give the idea of the backlog phases advances and errors detected. It needs improvement if you have a large test project and need to design financial budgets and control over costs of the test plan.
When you have to test the UI and how it behaves when certain actions are performed, you need something that can automate the browsers. This is where Selenium comes to the rescue. If you have to test APIs and not the frontend (UI), I would recommend going with other libraries that support HTTP Requests. Selenium is good only when you have no choice but to run the steps on a browser.
Recognize Adobe Flash and MS Silver Light elements without additional help
Detect and locate Java applets ingredients
Having the "Wait-till-Displayed" or "Wait-till-Present" as a built in Web Driver function instead of requirement for writing loops and defining expliccit wait, visiblewait, invisiblewait, etc.
We love this product mainly because of its high customization abilities and the ease of use. Moreover, its free and can be learned easily through online communities and videos. The tests are more consistent and reliable as compared to Manual tests. It has enabled us to test a large number of features all in one go, which would have impossible through manual tests. The reports generated at the end of the tests are really helpful for the QA and the development teams to get a fair view of the application.
As I mentioned earlier, the reason I use Selenium is because there is a fairly widespread community of users, and user support services are at a good level. because the application is open source, it works on many platforms (Windows, Linux, IOS) without any problems. In addition, it gives us a lot of options for writing functional tests. For errors that we receive through the application, we can easily find the reasons for errors in the forums.
Selenium does not have technical support available easily. You have to go through forums to get the information you need. However, there are excellent forums out there that make it easy to troubleshoot. The open-source flexibility makes it difficult to have dedicated support.
We did everything we needed to use it. Now we can execute our tests on different operational systems and browsers running few tests simultaneously. We also implemented Appium framework to execute our tests on mobile devices, such as iPhones, iPads, Android phones and tablets. We use SauceLabs for our test execution and Jenkins for continuous integration.
Test rail feels quite dated compared to Azure Test plans and Devops as a whole. Functionality and ease of use is actually night and day.
The ability to create structured test plans with ease that can be traced and attached to Epics and stories with relevant tasks allows the system to feel superior in everyway compared to Test rail which had a slow web interface
At the time of adoption, there were not many other alternatives that were even close to being competitive when it comes to browser testing. As far as I know now to this day, there is still little competition to Selenium for what it does. Any other browser-based testing still utilises Selenium to interact with the browser.
Typically the sprints themselves and managing the tasks have essentially eliminated our need for reporting.
The most valuable features of Microsoft Azure DevOps are high-level protection. Protection is very important to the customers to prevent eavesdropping.
Generation of detailed finding reports helped in cost savings in regard to direct labor.
Quality Assurance technicians found value in repeating mundane duties that they perform daily. It saved mental energy due to the automation process.
The value was established in high volume usage in setting up meetings as well as new accounts with A/B testing. Also merely cleaning up old test documents by evaluating them and organization or deletion.
