BrowserStack vs. PractiTest

As per my experience, BrowserStack is more suited for those organizations that have a remote work culture and also for those who need multiple device testing. Also, it is beneficial for those organizations that do not want to spend more on physical devices, as the devices update frequently in the market. It is not appropriate for those organizations which have lesser need of multi- device testing as the subscription model may not be feasible for them. Also a small organization with less number of employees would not opt for BrowserStack as it would be costlier for them.

Incentivized

For most of the test case scenarios, PractiTest works fine. If we talk about one specific feature then it would be the automation side. I like this feature a lot just because it made all testing so easy and effortless but on the other hand automation in this platform comes with so many limitations and that's where I am not fully satisfied.

Incentivized

• Test client website on 5x more platform.
• Provide a real device with features like media injection and Physical SIM testing for manual testing of a specific feature.
• Automate regression suite to execute parallel on multiple device.
• Provide an accessibility report for the website through automated scanning of the site using site.xml.

Incentivized

• Effective Test case template.
• Can integrate with different Atlassian products.
• Report generation.

Incentivized

• I wish it didn't time out so quickly. I often move back and forth between my native Mac OS system and browsers to BrowserStack for Windows browsers and it often times out so I have to start over.
• I am not sure why, but when I've been testing in BrowserStack for a long period of time - maybe over a couple of hours, it sometimes gets buggy and unresponsive or slow to respond. It makes it hard to tell if I'm experiencing an issue with the site I'm testing or if it's an issue with BrowserStack.
• If I'm wishing for the moon and stars, I'd ask for the ability to use BrowserStack to also test with JAWS screen reader. But I'm happy having NVDA.

• Better dashboard display capability (drag and drop to rearrange gadgets)
• Creation of global user groups (as opposed to just project groups)

Incentivized

It's simply a must-have tool. As a designer, I have to ensure my work is at least functional in older browsers. I also have to ensure that, when I design for mobile devices, any differences between platforms aren't problematic. BrowserStack allows me to test my work in a fraction of the time, with a whole lot more accuracy.

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.

Incentivized

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.

Incentivized

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.

Incentivized

The chat button is available to anyone who logs into PractiTest. In my experience, the support has always been very quick, very friendly, and very thorough. They make sure that your question is answered in a way that you understand it. They also provide documentation of best practices so you are never left hanging on what to do next.

Incentivized

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.

Incentivized

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.

Incentivized

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 used LambdaTest, but ultimately it didn't work for us because it put us in a queue when we kicked off a testing job instead of starting immediately. Our continuous integration process is managed by Microsoft Azure DevOps, and the pipeline agents it provides have a 60-minute timeout. We need immediate tests instead of flipping a coin, which could cause a false positive failure due to timeouts.

I've used many different Test Case Repository tools, and while each of them has its perks, I like the capabilities of PractiTest best. When creating a test in qTest for example, you can only input information into the fields provided, and you have everything set up in a folder tree structure. With PractiTest, we are able to create custom fields and filter our tests based on those fields to provide more accurate information in a readily available format while quickly searching for the filter instead of through a folder tree. TestRail did not appear to meet our needs as a company. It just didn't have the potential that we found with PractiTest. Zephyr for example worked seamlessly with Jira, which is really nice since that is what we use for the most part. However since we cater to many different clients, we needed an external Test Case repository so we could use something that wasn't tied to 1 Jira instance.

Incentivized

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

Incentivized

• Browserstack improved our internal confidence level when it came to signing off on testing
• Browserstack improved the confidence level of our clients by decreasing the number of bugs found during PVT and providing an entry level opportunity for our clients to perform UAT using the same tools.

Incentivized

• Test Reporting
• Defect Management

Incentivized