June 2019 Summaries

Regression testing is crucial for organizations that aim to deliver high-quality code quickly. However, creating a comprehensive yet fast regression test suite can be challenging. This article provides techniques to create quick and comprehensive regression test suites, including optimizing elements of a test script, breaking down test scenarios into faster, independent tests, and examining the test suites' execution. By implementing these strategies, organizations can improve their testing process, leading to more productive and happier QA teams.

On May 16th, BrowserStack hosted its first ever meetup in San Francisco with over 50 automation engineers and developers attending. The event featured speakers from various companies such as Twitter, Lyft, Square, and more. Ritesh Arora, co-founder and CEO of BrowserStack, shared the company's journey and mission to empower teams to ship quality releases with confidence. Other speakers included Lanette Creamer from The Omni Group who discussed how QAs can ship faster while juggling multiple projects, Priyanka Halder from GoodRX who talked about setting up a successful QA function, and Brian Lucas from Optimizely who shared insights on eliminating the back-and-forth between dev and test teams.

Functional testing on the cloud can be optimized by making changes in setup, test suites, and solutions provider. Key steps include targeting an acceptable test execution time, running tests on every pull request, configuring CI for efficiency, keeping tests short, embracing parallelization, mixing-and-matching browsers to prevent queuing, using built-in debugging options, testing on the right browsers and versions, testing on different screen sizes, testing on the right mobile devices, running tests in real user conditions, setting up alerting, monitoring, and bug tracking. These optimizations can help teams get better builds in less time and make the most of functional testing on the cloud.