Deploy each feature branch to its own environment<\/strong><\/h3>\n\n\n\nProviding every feature branch with its own environment provides clarity around ownership of any issues and allows different teams to work independently without creating collisions that slow things down. <\/p>\n\n\n\n
Giving each feature branch an environment that developers can use for end-to-end testing also supports shift left<\/em> practices, which help the development team catch new issues before code becomes too complex to easily debug.<\/p>\n\n\n\nReset and deploy test data with your test environment<\/strong><\/h3>\n\n\n\nFor a measurable reduction in the complexity and maintenance costs of your tests, set up test data in your test environment that can shorten your tests.<\/p>\n\n\n\n
For example, if you want to confirm the \u201cpast orders\u201d page on an e-commerce site is working as intended: Instead of adding steps to the test to create backdated orders, automatically add sample orders to your test environment upon deployment.<\/p>\n\n\n\n
To avoid broken tests, reset the state of test data before each execution of your test suite.<\/p>\n\n\n\n
Avoid shared state<\/strong><\/h3>\n\n\n\nRunning tests concurrently shortens the time it takes to get results. But when tests share test accounts and states, running them concurrently can create conflicts and subsequent false-positive test failures and incorrect validation that waste the team\u2019s time and energy. (Few things are more disruptive to the software development lifecycle than engineers having to investigate false positives.)<\/p>\n\n\n\n
Wherever possible, seed unique test data and account profiles to each test so all of your tests can run concurrently without colliding.<\/p>\n\n\n\n
<\/span>5. Test like a human (even with automation)<\/strong><\/span><\/h2>\n\n\n\nTesting should represent the customer experience as much as possible. This means using the right kind of automation and recognizing when automation isn\u2019t a good fit.<\/p>\n\n\n\n
Use the right kind of automation<\/strong><\/h3>\n\n\n\nMany approaches to test automation evaluate what the computer sees in the DOM (behind-the-scenes browser code), not what your end users will see in the user interface (UI). To validate the actual user experience, use an automation approach that interacts with the UI.<\/p>\n\n\n\n
Know when to use test automation and when not to<\/strong><\/h3>\n\n\n\nAutomation isn\u2019t a fit for every use case and testing phase. It\u2019s a great fit for rote, repetitive tests that don\u2019t require subjective evaluation and for features not subject to significant change.<\/p>\n\n\n\n
Manual testing is a better fit for new features still in flux, particularly complex use cases, situations that benefit from human judgment, and high-risk releases where manual testing can augment automation.<\/p>\n","protected":false},"excerpt":{"rendered":"
After 10 years, we have a set of QA testing best practices that work for teams shipping fast and frequently.<\/p>\n","protected":false},"author":28,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2003","post","type-post","status-publish","format-standard","hentry","category-qa-strategy"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/posts\/2003","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/users\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/comments?post=2003"}],"version-history":[{"count":12,"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/posts\/2003\/revisions"}],"predecessor-version":[{"id":2342,"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/posts\/2003\/revisions\/2342"}],"wp:attachment":[{"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/media?parent=2003"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/categories?post=2003"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/tags?post=2003"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}