Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The Top 8 Things We Learned From the QA Team at America's Test Kitchen

DZone's Guide to

The Top 8 Things We Learned From the QA Team at America's Test Kitchen

These webinar takeaways talk about how the America's Test Kitchen team created a top testing strategy for their three websites.

· DevOps Zone ·
Free Resource

Read why times series is the fastest growing database category.

With three core websites, America's Test Kitchen has a lot of content to cover. Yet when Megan Collins came on as QA manager, she was the only tester. Since then, America's Test Kitchen has exponentially scaled their testing, adopted an automation strategy, and expand the QA team to three members, including Automation Engineer Michael Ng.

We recently had Megan and Michael join us for a webinar to talk a little bit about the web testing strategy behind America's Test Kitchen and how they handled their shift to automation with the help of CrossBrowserTesting.

Here are the top 8 things we learned in the webinar:

  1. Fast deployment schedule demand testing: Most organizations dream of achieving the agility that America's Test Kitchen has reached, deploying code to production every two days. But when you're integrating as often as they are, you can't just rely on developers to test each others code or you'll never achieve consistent test coverage. By bringing in Megan Collins as QA Manager, she was able to spend her time on something that had been severely lacking - testing. This way, proper exploratory tests could be performed when there are any changes to code, and the development team can continue working doing their jobs instead of worrying about the intricacies of whether a new feature works or not.
  2. Real devices matter: When discussing emulators, simulators, and real devices, there's a time and place for each one. In fact, Megan mentions that the developers on her team use emulators. However, the only way to see exactly what your users are seeing is to use real devices, which is why they are so important to the QA team. In fact, they even ran into a bug where membership details weren't displaying for a user that wasn't found on the emulator they were using - they noticed it once they performed the test on a real tablet device. While emulators are highly accurate, they do not replace real devices, and this is a large reason why they need a tool like CrossBrowserTesting that includes all three in order to prioritize both speed and accuracy during mobile testing.
  3. It's important to understand different user journeys: The success of the America's Test Kitchen QA team has a lot to do with their ability to identify the different users they have and how it affects their testing. Because a lot of the web content they have is for members only, there are paywalls that occur when someone accesses from a non-paid account, for example. By separating user states into two focused areas for their automated tests, static and dynamic, Michael is able to create more precise tests for different parts of the website. Understanding that they need to test different based on whether users are new, registered, on unsubscribed helps them build out different test cases and scenarios.
  4. Capture tools can help prove a point: Sometimes seeing is believing, and it can be hard to convince other team members of a bug they haven't seen for themselves. Tools like CrossBrowerTesting's screenshots and video capture help the America's Test Kitchen QA team build out their test reports to include visual evidence of different occurrences during tests. This way, Megan doesn't have to repeat the test case or find it on the right browser when she shows it to development, she can just show the screenshot or video instead so bugs get fixed faster. Additionally, by using the screenshot comparison engine, Michael has been able to create an archive of each homepage over time so it's easy to show what changes in each regression.
  5. Use automation to make your life easier: America's Test Kitchen isn't automating every single test on their website. In fact, manual testing is still a large part of their strategy. Automation comes in mostly with repetitive tasks that take up a lot of time. For example, they use automation to sign in as a member in order to see whether content can be viewed instead of going through the actions of logging in in every time. This saves Michael valuable time in performing different test cases under different user scenarios - instead of replicating the same actions every time, he can focus on how each test differs.
  6. Collaboration is key: We say it over and over again, but communication with your team is important to productive testing. By leveraging tools for organizing your tests, taking notes, and tagging, it's easier to remember which bugs you've encountered before and which are new. Additionally, keeping open communication with the development and design teams has been essential to America's Test Kitchen for understanding priorities, risks, and hot spots for more insightful testing. Megan and Michael have found collaboration with the development team to be especially crucial in the shift to automation - learning new skills, choosing what to automate, and being notified when new code is added.
  7. Test while you sleep: Many of the automated tests that the America's Test Kitchen QA crew create run at night, meaning that you literally can test in your sleep. Overnight testing is at the crux of their Selenium strategy, meaning they can check tests in the morning to see if they pass or fail. Because they have so many tests that run for an extensive amount of time, they rotate their browsers each night to get coverage of all the different configuration their users are on to see which tests are failing on which browsers. By running these regression tests, they're able to test a subset of test cases across different pieces of functionality that they need to make sure are working day-to-day.
  8. Tests are only as good as how much time you put into them: Michael runs a lot of automated tests, but he also spends a lot of time maintaining them. The America's Test Kitchen QA team emphasizes that maintenance is crucial to the success of the project. This is one of the main reasons they have a dedicated QA automation engineer. In order to ensure that Selenium tests aren't just been created left and right, Michael spends a lot of time on each one to make sure it is accomplishing his goals (and may even be a few steps ahead of Elon Musk in this way).

Megan and Michael gave us a great look at how they use automated and manual testing to further the goals of America's Test Kitchen. By taking the time to learn from other successful QA teams such as this one, you can apply some of their practices to your own testing strategy.

If you want to view the full webinar, you can watch below.


This article was originally published on CrossBrowserTesting.com.

Learn how to get 20x more performance than Elastic by moving to a Time Series database.

Topics:
devops ,qa ,mobile testing ,agile ,automation ,software testing

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}