Posted on

Free – Automation Tutorials – BrowserStack Summer of Learning

 BrowserStack Summer of Learning, a free 5-part webinar series designed to help QA and engineering teams of all sizes learn and scale test automation. Whether you are a beginner QA analyst dabbling with exploratory testing or a 50 releases-a-day veteran, Summer of Learning is a go-to for everybody.

The series begins with an introduction, first to Selenium and then to BrowserStack, and gradually takes you through the process of moving from manual to automated testing. It covers industry trends in testing and features testing stalwarts such as The Weather Channel, who release to millions of users each day.

BrowserStack Summer of Learning has the following episodes:

Episode 1 — The Basics: Getting started with Selenium: An introduction to Selenium, how to set up/write your first test scripts, and how to pick the right framework. This is a great introductory session for those looking to learn test automation in 60 minutes.

Episode 2 — Introduction to BrowserStack Automate: In this episode, you’ll learn how to set up and run your first test with Automate, how to test on various real devices and browsers on the BrowserStack Real Device cloud, how to test your local instance on the cloud, and how to collaborate and debug better.

Episode 3 — Continuous testing at scale: You’ll learn how to build an efficient, well-integrated CI pipeline that helps release quality software at speed. You’ll also learn how to use BrowserStack to deploy faster and listen to stories from great companies like The Weather Channel, who release to millions of users every day.

Episode 4 — Selenium + BrowserStack at scale: In Episode 4, David Burns, core contributor to Selenium will explain how to plan parallelization more effectively to achieve faster build times, the best ways to maintain test hygiene while scaling your team or automation suite, and how to monitor test feedback effectively.

Episode 5 — Testing for a mobile-first market: There are 9,000 distinct mobile devices in the market—and you most definitely can’t test on them all. But with this episode, you’ll learn the best strategy to pick the right devices for testing your website or mobile app.

Posted on

The 9 Best Tips to boost your Retail Mobile App Testing

In this post:

1. Test your User Experience application performance

2. Improve QA Environment availability

3. Test data complexity –

The key to solving this, based on our experience with large retail customers, is in applying these two methods:

– Implementation of service virtualization can help to address test data challenges.
– Use Rest API interfaces to configure and collect the current relevant test data.

These two solutions will help assure that test data is always valid, and minimize the time invested in investigating testing issues.

4. Combine API in your UI functionality tests – highly recommended that you combine an API with functional UI testing. Implementing this will eliminate setup overhead, and allow for your functional tests to stay short, atomic, and focused.

5. Test for Retail mobile app specific scenarios

6. Build a fast feedback pipeline – Building a fast feedback pipeline is important for every industry but it is especially important in a retail mobile app testing environment.

7. Handle device fragmentation

8. Test for accessibility

9. Test in the cloud

Read the complete article: https://experitest.com/mobile/the-9-best-tips-to-boost-your-retail-mobile-app-testing/

Posted on

Can TDD Apply To Performance Testing?

Neotys explained in a simple way how we can do Performance Testing early in the cycle and how can we minimize the risk and costs.

Test-Driven Development is a great tool for functional testing, but can you apply the same technique to performance testing?

Why not?

The purpose of TDD is to build out small unit tests, or scenarios, under which you control your initial coding. Your tests will fail the first time you run them because you haven’t actually developed any code. But once you do start coding, you’ll end up with just enough code to pass the test.

Some Tricks for Performance TDD:

1. Create small-batch load tests that can stress small components. As you start planning your module, think about how that module would be stressed. What algorithms are most likely to limit scalability? Is there an opportunity for resource contention? Do you have queries that could impact performance if they get too large or complicated? Then create your test scenarios specifically to stress the component in these ways. As you and your team work through more and more of the product, you’ll end up building an amazing library of load test scenarios that you can leverage in lots of interesting ways moving forward.

2. Don’t apply TDD to optimizations, instead just use it for base-level performance. The job of a performance engineer is often focused on optimizing code that’s already been written by someone. TDD isn’t really going to be much help here. Remember, TDD is best leveraged at the beginning of the code-writing process. So that’s where you should start. As your product matures, it’s completely appropriate to make your load tests incrementally more demanding (a certain function must return in 2 seconds instead of 4 seconds), but that may not always be the ideal place to focus because scaling problems are often driven by more complex interactions that are best suited for different kinds of test methodologies.

3. Automate. TDD and automation go hand-in-hand, and you should approach it that way from the beginning. Think about how to automate your TDD from the moment you start doing it, like any modern development method. By doing this, you’ll be able to easily plug your performance testing into other automated processes like continuous integration, but you’ll also end up with a number of micro-load test scenarios that can be strung together into a larger automated test scenario. This gives you a ton of leverage.

Article Source

Posted on

Best Practices- Speed up your releases with parallelization in Selenium using BrowserStack

Every Dev and QA team wants to release software at speed. Parallel testing helps teams run a massive number of tests in minutes, reducing build times and enabling faster releases. However, in order to prepare for parallelization, you need a well structured test suite and a stable, scalable test infrastructure. In this webinar, David Burns will demonstrate how to optimize your test suites to make the most of parallel test execution.

From the webinar you’ll learn how to:

  • Effectively plan parallelization
  • Maintain test hygiene while scaling your parallels
  • Achieve faster build times by running tests in parallel
  • Best practices of monitoring test feedback

Click Here to Register to the Webinar
Webinar Date: April 22, 2020; Time: 9 AM PT/4 PM GMT

Posted on

Benefits of real device testing on AWS Device Farm (with Demo)

AWS Device Farm - Mobile Testing

Benefits of AWS Device Farm

Use the same devices your customers use:
 Run tests and interact with a large selection of physical devices. Unlike emulators, physical devices give you a more accurate understanding of the way users interact with your app by taking into account factors like memory, CPU usage, location, and modifications made by manufactures and carriers to the firmware and software. We are always adding devices to the fleet.

Reproduce and fix issues faster:
 Manually reproduce issues and run automated tests in parallel. Device Farm collect videos, logs, and performance data so you can dive deep and solve problems quickly. For automated tests, it will identify and group issues so you can focus on the most important problems first.

Simulate real-world environments:
 Fine-tune your test environment by configuring location, language, network connection, application data, and installing prerequisite apps to simulate real-world customer conditions.

Choose the tests that work for you
 Run our built-in test suite (no scripting required) or customize your tests by selecting from open-source test frameworks like Appium, Calabash, and Espresso (see supported frameworks). You can also perform manual tests with Remote Access.

Integrate with your development workflow:
 Integration with CI/CD pipeline: You can use AWS CodePipeline to incorporate mobile app tests configured in Device Farm into an AWS-managed automated release pipeline. Jenkins plugin for AWS Device farm: https://github.com/awslabs/aws-device-farm-jenkins-plugin

Setup your own private device lab in the cloud
 Device Farm’s private device lab offering lets you choose iOS and Android devices for your exclusive use. Device Farm provisions these devices with the exact configurations you need, and lets you persist settings between sessions. Since these devices are exclusively for your use, you don’t have to wait for other users to finish using them.

Posted on

Simplifying Mobile app testing with AWS Device Farm.

AWS Device Farm - Mobile Testing

With AWS Device Farm, you can interact with real Android and iOS devices from your browser or run automated tests written in popular frameworks like Appium, Espresso, and XCTest.

Device Farm was launched by Amazon in July 2015 and it has been improved a ot over the years. It helps mobile developers test their apps against a large (and growing) collection of real phones and tablets to improve the quality of their apps.

Developers can upload their apps and run tests simultaneously on all of the most commonly used mobile devices across a continually expanding fleet that includes the latest device/OS combinations. As tests complete, developers receive timely reports that identify problems, helping them bring their apps to market faster and with better quality. There is no setup cost to get started with AWS Device Farm, and developers pay as they go.

You can run automated tests as well as connect to the real devices remotely and test manually.

AWS Device Manager - Mobile Testing

Device farm has a large pool of devices. Here is the complete list of supported devices: http://awsdevicefarm.info/
You can schedule your tests and also do the integration with CI/CD pipeline. Jenkins plugin for AWS Device farm:  https://github.com/awslabs/aws-device-farm-jenkins-plugin.

Watch the Introduction Video:

PS: You can also test your web desktop apps on various rowsers using Device Manager and run your Selenium tests in parallel on multiple versions of Chrome, Internet Explorer, and Firefox, that are hosted in the AWS Cloud.

Posted on

Karate Capabilities – UI Test Automation Made Simple

Karate script

Below are the capabilities of Karate UI. Gives many reasons why one should go for Karate over Selenium.

Reference: https://github.com/intuit/karate/tree/master/karate-core

Posted on

The State of Test Automation in 2020 (via Perfecto.io)

Test automation is critical to the DevOps pipeline. But its rate of adoption varies. And many teams still struggle to achieve successful test automation.

Download this report by Perfecto.io to learn:

  • How many test cases teams are actually automating.
  • Who exactly is responsible for testing.
  • The biggest challenges teams face in automation.
  • The length of a typical release cycle.
  • Which tools teams rely on for testing.
  • The top priorities for testing in 2020.
  • And much more!