ACCELQ

Selenium is a powerful tool to automate user interactions on a browser. A robust Selenium framework with the right design can increase test coverage and save time. This is why many organizations use Selenium for automating their application testing, including Salesforce application. You may also want to automate your Salesforce application testing with Selenium. Especially when manual testing alone can’t cover your testing requirements for regression testing. But applications built on Salesforce are pretty complex and can be challenging to test with Selenium. Here are the top three testing challenges with Selenium scripting, particular to Salesforce test automation. Navigating through frames Salesforce is a complex application with the front-end built with dynamic frames, that are able to load content independently in the current HTML document. Handling frames is difficult with Selenium as it cannot access the content directly.  Normally you would require to switch the Sele

You probably won’t find any issues navigating through your e-commerce website, given that the new release was vetted sufficiently by your QA and certified for the release. But it doesn’t mean your visitors will have the same experience. This is because visitors can access a website with various bandwidths, devices, browsers, and geographical locations. And all these external factors influence a website’s performance at the user’s end; so much so that any minor change can impact the shopping experience. For instance, you add a third-party marketing plugin (or app) on your webstore to increase sales or to track user behavior. The addition of this plugin may look benign in your internal testing and usually does not get a high level of attention from your QA teams. Such third-party plugins are common on e-commerce platforms like Magento, Shopify, and WordPress. While these e-commerce platforms guarantee industry-best performance in the shopping experience, they usually have no contro

Ever since Quality Assurance was recognized as a formal practice in Software Development Lifecycle, manual testers have held high the responsibility of ensuring a bug-free software delivery. Over the years, manual testing community has adapted several tools and processes to continually enhance the outcome and predictability of application quality. Software expands with every new release, update, and modification. Testers have a crucial role and a daunting task to keep up with the regression testing, ensure quality of new features, test integration with other systems, keep a track of defects, and maintain a log for new ones. Test Automation has proved to be disruptive, and many software testers have jumped on this automation bandwagon so to speak. But with so many predictions, opinions, and innovation around test automation, will the manual tester’s role remain the same or will it change with time? Here’s our take on the topic: Test Automation: Was the Purpose Defeated? With t