Ashley Hunsberger, Greg Sypolt and Chris Riley conduce to this post.

Software testing tools are a vital imagination for every successful QA team. But with so many puppet and examine frameworks out thither - from Selenium and Protractor to Espresso and Xcode - how do you choose which are good? How should your toolset vary depending on whether you do desktop testing, mobile testing, or both? And how do you make the most of software testing tools?

Below are answers to these questions from the panelist of a recent Sauce Labs webinar focus on software testing and QA. The webinar was hosted by Chris Riley, with Ashley Hunsberger and Greg Sypolt serving as panellist. You can also find their recommendations on package testing creature below.

Which tools has Greg used for exam mechanization at Gannett?

Greg: Here ’ s an inventory of prove frameworks and tooling used across Gannett products (technology alignment):

• Ruby+Cucumber+Capybara

• NightwatchJS

• Behave Python

• Mocha

• Jasmine

• Protractor

• Polymer

• Junit

• Espresso for Android

• EarlGrey for iOS

• Minitest

• Ruby+Rspec+Capybara

• Selenium

  Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

• Appium

• Jenkins

• TeamCity

• Sauce Labs

• Drone

• Chef

• Datadog KPI Dashboards

What are some creature used for mechanisation across the industry? I & # x27; ve heard of Selenium, but is thither anything else?

Greg: Selenium WebDriver is the industry touchstone for browser testing. However, I like to align the testing framework technology mass with the coating mountain. For example, web applications developed in AngularJS would align with Protractor as the testing framework. Selenium Webdriver comes in many sapidity; Java, Python, Ruby, Javascript, etc.

Here are some test frameworks to know:

• Browsers: Capybara/Cucumber, Capybara/RSpec, NightwatchJS, Behave, and Protractor

• API: NodeJS, Jasmine, and Mocha

• Mobile: Android Espresso, iOS EarlGrey, Appium, KIF, and XCode 7

I often experience like the DevOps substructure problem have to be work before I can do test automation. Is that true?

Greg: Check out this post aboutinfrastructure planning. It discusses how QA and Dev should share responsibleness for infrastructure. The team also should share responsibilities for DevOps tasks. The mod QA position has become a technological role, the gatekeeper of caliber, and QA engineers may continue to conduct on more DevOps responsibilities and tasks.

Ashley: Every company is different (such as mine and Greg & # x27; s), but I do act tight with our DevOps squad more and more as we transition. We definitely notwithstanding have our kinks, but we are still doing test automation. We are still working to be in the CI pipeline, but it doesn & # x27; t forbid you from notwithstanding having meaningful tests.

How do you get developer to use GUI screen tools? It seem like most devs instinctively dislike GUI tests.

Ashley: Once you get the right technology alignment, demo how and why they are used. We want few GUI tests, but we have roughly 40 tests that we consider critical workflows that we forever want passing. We are able to quickly name when something breaks in the UI. Show that you have deterministic resolution. For instance, we be able to identify which commit broke our tests quickly and discuss with the developer. Without these trial, this bug would not have been caught for two more weeks. Since this was still during the development period, overhead was low and we got a fix in within a few hr.

Greg: I agree with Ashley. The best buy-in from developer for me has been technology conjunction. Now the developers can help write and review test codification. The key to automatise GUI examination is honest processes for developing machine-driven GUI examination. Work as a team to determine the right GUI tests needed, best drill for test code, and continue to focus on ways to eliminate eccentric exam and build self-confidence in the tryout results.

Which analytics tools do you use?

Greg: We use Jenkins, Datadog, and CloudWatch to mensurate the health of the Android project to determine if it is on the course to success and name where melioration demand to be made to meet our end and deadline. It ’ s on our roadmap to explore open root Capital One Hygieia and New Relic Synthetic Monitoring.

Conclusion

There ’ s no shortage of software testing puppet out there for both automatize and manual testing. Selenium WebDriver remains a staple, but depending on your particular needs, you may want to take reward of former testing instrument, too. A major goal should be to seek technology alignment. That helps to assure that your testing strategy is as efficient as possible, while likewise facilitating better communicating between QA and Development.

Chris Riley (@ HoardingInfo) is a engineer who has spent 12 years aid governance transition from traditional development practices to a mod set of culture, operation and tooling. In addition to be a research analyst, he is an O ’ Reilly author, regular speaker, and subject matter expert in the area of DevOps scheme and culture. Chris trust the biggest challenge faced in the tech market are not tools, but sooner citizenry and planning.

Ashley Hunsberger is a Quality Architect at Blackboard, Inc. and co-founder of Quality Element. She ’ s passionate about making an impact in education and loves coaching team member in production and client-focused character drill. Most recently, she has focused on tryout strategy implementation and grooming, development operation efficiencies, and preaching Test Driven Development to anyone that will listen. In her downtime, she love to move, read, quilt, hike, and spend time with her family.

Greg Sypolt (@ gregsypolt) is a senior engineer at Gannett and co-founder of Quality Element. The concluding 5 years center on creation and deployment of automated test strategies, model, puppet, and platforms.