BrowserStack is a test platform built for developers and QAs to expand test coverage, scale and optimize testing with cross-browser, real device cloud, accessibility, visual testing, test management, and test observability. BrowserStack states it currently powers over a billion tests a year for customers who include Amazon, Paypal, Well Fargo Bank, Nvidia, MongoDB, Pfizer, GE, Discovery, React JS, Apache, JQuery and several others rely on BrowserStack to test their web and mobile apps.
$0
per month Unlimited users and 5000 free screenshots
React (React.js)
Score 8.8 out of 10
N/A
React or React.js is a JavaScript library for building user interfaces. React enables users to create interactive UIs.
$0
Selenium
Score 8.3 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
BrowserStack
React (React.js)
Selenium
Editions & Modules
Percy - Free
$0
per month Unlimited users and 5000 free screenshots
App Percy - Free
$0
per month 5000 free screenshots and 100 minutes of infrastructure
When we are comparing BrowserStack have faster session start times compared to Sauce Labs. And also simpler, user friendly setup and UI. This help to our team members to navigate and use. Browser stacks have reliable parallel execution with stable performance. We can get better …
We chose BrowserStack as our solution as it provides a comprehensive, all-in-one package. This integrated approach ensures that all your needs are met in one place, eliminating the need for multiple tools or services. It streamlines processes, improves efficiency, and …
It is one of the product which each software organisation should include in their end to end product development journey. I have explored other products in this category and I can proudly say that BrowserStack is a clear winner in terms of its Features, Performance and Product …
Price looks little high for browserstack , they need to introduce more flexible plans to stack their customers, support team must be more quick, sometimes they take more than 2-3 days to resolve the issue. other tools are available in less cost with same features. so later on …
I have used Saucelabs with Jenkins and would say both of them are really comprehensive. Yet I suggested BrowserStack to our customers and team since I have used it recently and felt it easy to use and implement Tests on it. BrowserStack support team is another reason behind why …
I'm using the app automate feature for Automation of mobile application. So, we are add Jenkins for CI process to use on BrowserStack. For mobile application testing, We are using Appium with java client in our framework and also integrate with BrowserStack capabilities.
Easy to start using the first tier plan and from there you could easily upgrade based on your team's need and if you need to extend to other users. A good and wide selection of server locations helps us oversee how an actual user experience might be. His credentials in terms …
Before using BrowserStack, we had limited access to virtual machines for testing. Booting up each of these devices was time consuming and difficult to manage when multiple users needed to test. BrowserStack opened up our testing to more devices, being accessible by anyone who …
Open sourced and free: Multiple language support: The community: Wide plugin support: Easy installation and intuitive usage: Cross-browser support: Remote testing: Multiple testing and parallel testing execution:
I have the most experience with selenium. I have used form filler, which is a Google add-on that allows you to create a form quickly. This is a little easier to use and has less setup time than selenium IDE, however, it is less powerful. I picked selenium because it is an …
If you need immediate testing (for example, from Azure pipelines agents), use BrowserStack instead of LambdaTest (which makes you wait in a "pool" until the device/platform combo you are querying is accessible). If you don't need your tests to be immediate and prefer a wider range of devices, then use Lambdatest.
React is a JavaScript user interface construction library that works well for:
Developing web apps with dynamic and complicated user interfaces.
creating reusable UI elements that may be used in other applications.
creating single-page applications with dynamic content updates that don't require a page reload.
The Virtual DOM's effective updating mechanism allows it to handle large volumes of data updates.
React, on the other hand, might be less suitable for:
Websites that are simple, stagnant, and have no interaction. Other libraries or simple HTML, CSS, and JavaScript may be a better fit in such circumstances.
Web sockets may be a better choice for applications that need real-time updates, such as chat or gaming apps.
When creating mobile apps, React Native is a better option.
Server side rendering only, as React is designed to run on the client side.
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.
React is fantastic for building performant user interfaces. Our web app is snappy and great for our customers.
React has the philosophy of doing one thing and doing it well which is the view layer of the application. This makes it incredibly intuitive and flexible for developers to use.
React has lead the way in being able to write modular and structured code. It is a drastic improvement since the days of spaghetti jQuery code.
React has an unmatched community. The amount of tools and libraries available is fantastic, and there plenty of solutions available online for common problems.
Debugging React is challenging. Bugs in react code generate stack traces internal to React and it is often totally unclear how it relates to the code you actually wrote.
Relating your React elements to corresponding DOM elements is difficult. The intentional separation of virtual and actual DOM also makes it difficult to map the elements to the structures in the DOM. This is partially ameliorated by the use of the React dev tool, which provides a DOM-like view of the React elements, but the tool still does not provide a direct correspondence with the DOM that is often necessary to figure out why something isn't right.
Because JSX is React-specific and not a language feature, a special compilation process is necessary to convert JSX code to normal JS. Coming from a C++ background, compiling things doesn't bother me, but many JS developers are used to a less structured development.
Selenium is pretty user-friendly but sometimes tests tend to flake out. I'd say roughly one out of twenty tests yields a false positive.
Selenium software cannot read images. This is a minor negative because a free plug-in is available from alternate sources.
Slowness may be a minor factor with Selenium, though this is an issue with basically any testing software since waiting on a site to execute JavaScript requires the browser to wait for a particular action.
It's almost the 3rd year for us and it's renewal time for us. So yes, we are already discussing how many licenses we need to increase as users are increasing internally. So it's 100% sure that we are already planning renewal this year as well BrowserStack with live and app automate.
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.
So many options that it can be a little overwhelming, but the core functions are easy to find and use and it's usually not too hard to figure things out for the more complex tasks. Very easy to boot up a device and a specific browser from the dashboard to begin a manual website test.
React is just a bit of a different animal. I was avoiding it for the longest time. I thought for sure I would land on Vue or something else with a more approachable and familiar appearance. But after taking an online course in React, I started realize what people were raving about (and complaining about) and decided to implement it at our office for one of our products.
For those who are unfamiliar with coding, there is a bit of a learning curve. There is plenty of helpful documentation and resources but it can take a little time to get the software up and running. Once you get the hang of how Selenium works, and what it can do, you realize how many things you can use it for, and how many processes you can automate.
I rated BrowserStack's availability a 10 because it is consistently reliable, with minimal to no downtime or unplanned outages. The platform is accessible whenever needed, ensuring uninterrupted testing. Its robust infrastructure and proactive monitoring ensure a seamless experience, allowing us to meet deadlines without delays caused by availability issues and all
The tests are fast considering the fact that they're Appium tests. I've seen tests reliably pass or fail when they're supposed to, with next to zero issues on the BrowserStack side of things. Tests launch only seconds after I kick off them off from my CLI.
I've not had much direct interaction with the BrowserStack support team. The help and community are great and we've not run into any issue that has really required us to reach out. I guess having a stable and easy to use system means you may never need to contact support.
Since it's open-source and very popular, the community support for React and related tools and libraries is excellent. There are a lot of people using the same tools, and so issues tend to get fixed quickly and "recipes" are easy to come by. And since it's backed by Facebook, they have a dedicated engineering team working on the progression of React.
The Selenium app has a pretty fat community of users. For the problems we are experiencing, we are primarily receiving support from these communities. In addition, there is widespread service support. Instant support is given to the problems we experience when we need Online support. We and our team are happy to provide this support, especially before important deployment processes
Yes, it was online training on meet, and trainer looks like skilled and technical strong, he has covered end to end all the features and he has answers all the queries. because of this trainings we are able to implement it by our own in the organization, thank you for support and training.
It was a quick training from the support of browserstack, it was nice and easy to understand, thanks again for the support given by the team. and regularly I used to receive mails for training from support for any new feature they launch, I was able to spread same training to all my team and dev.
I rated the implementation satisfaction an 8 because while it went smoothly overall, there were some challenges during the initial learning phase and integration with existing tools. Key insights include the importance of providing sufficient training upfront and ensuring seamless integration with other systems to minimize disruptions and improve adoption speed.
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.
BrowserStack products has been found better for low code automations and visual regression techniques. We have been struggling to maintain the API endpoint sanity tests and writing a lot of code for them while releasing the builds, while we chose BrowserStack accessibility solutions, we found it a way easier than we thought and worked it up.
While this is a widely contested debate with various blog posts and benchmarks all over the place, its really a personal choice to determine what works for the team. Coming from a Angular 1.x background, I decided to try a new framework when Angular 2.x was announced and at that time React is gaining popularity and Vue hasn't taken off yet. Compared to Angular 1.x and Vue (hybrid of React and Angular) that split the logic from the html templates, I loved the way React breaks code into components using the jsx syntax. In my mind, this allows for cleaner components and easier maintenance
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.
I may not be the best person to answer this as I am only using it for 1 department and at 1 site but will still try my best As far as Scalability for Devices for Mobile Automation is concerned, it gets a Solid 10, as the users can run cases on upto 10 device parallel and also have the best choices of devices to choose
