User Interface (UI) Testing. The idea is simple — automatise some UI tryout to check your covering is still behaving as wait. Usually your first set of examination — running green, no doubt — do you all cheer and pat yourselves on the dorsum. Then you open up the framework to more people. Despite the follow-up (so many reviews), the failures start to come, and they don ’ t stop. Or they run green and then betray and so run green again. And then fail again. So why are they so precarious? Is it bad handwriting? Environment issues? Sometimes you simply don ’ t know, and you think you are going to lose your mind. Let ’ s take a look at some common and possible issues you may be facing.

Architecture, Environments and Settings

Is your infrastructure designed for constancy? Are you using on-premise or cloud instances? What may have saved you a dollar upfront could be you many more down the road - so your testing environment is important. Understand if your tests require particular system settings. Tests betray because of undesirable server variable is a wastefulness of everyone & # x27; s clip. We launch that out the hard way a long clip ago. You may need to get some isolated exam that can not be run on the like waiter so the majority of your other tests can legislate. (Or perchance adjudicate how crucial the exam really is.) Or let ’ s say your examination frameworks are stable, but what about the creature or libraries you are importing? Are you pinning your stack to a version of these tools or libraries? A new variation can completely break everything.

Many times, teams are exhort to have tests run as tight as possible. The way to accomplish this is parallelization (say more on that hither). That said, if your automation architecture design was not project out to support it, you may discover difficulties.

Back-end Stability

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

How confident are you in your back-end acceptance tryout? Without a stable base, it is hard to be confident in the UI built on top of it. When you publish end-to-end (E2E) workflow exam, you are hit your back-end. If they aren ’ t loss, you can ’ t be sure if your UI E2E tests are providing value, or if they are being impacted by deeper matter. Consider using mock API testing as part of your UI testing strategy. This reduces some of the impact of back-end issues, and give more flexibility to the QA team.

Timing Issues

Consider how complex your scheme under exam is. How long does it take to progress? Does your back-end get out of sync with the UI and perhaps have changes that may not be in the UI yet (or vice versa)? In fast-paced modern ontogeny these types of issues can come up more and more. Also consider how you are setting up data. For model, let ’ s say you need to create a user, a student, an assignment, and a submission for that assignment. If your test is to grade that submission, but your setup hasn ’ t completed for some reason, your test will fail because it can ’ t find the submission. Think about how the team can help. Can your developers and automation champion design and deploy answer for mock testing? Can DevOps help deploy those solutions with configuration management mechanization? Collaborating with the broad team for both timing and backend topic will help everyone.

Knowing What to Test: Just Because You Can, Doesn ’ t Mean You Should

Seriously think about what you are testing through the UI, and why. The more exam you hold, the more of a pain your test suite will be to proceed running green, and maintain. You should make higher-level conclusion about the goals of your end-to-end tests. It is improbable that the goal is to test every possible scenario. (Testing critical workflow is much more potential.) No matter what, there ’ s a constant struggle of balance that you need to view. Try to focus your tests on UI components and business logic. For example, I just had a conversation with a developer — and, while I ’ m thrilled this person was thinking about testing — this someone wanted to screen how to cancel an item delete in two different ways. Rather than prove every combination, I recommended simplification, because i knew it would not have a critical workflow impact. In this case, I asked the developer, “ Why not just concenter on UI component/unit tests instead? ” Automation provides a ton of benefits. But in order to make sure those benefits are realized over a long period of time, some planning is require. Consider your business goals and prepare for the things that can commonly go improper.

Ashley Hunsberger is a Quality Architect at Blackboard, Inc. and co-founder of Quality Element. She ’ s passionate about making an wallop in education and loves coaching team member in ware and client-focused quality pattern. Most recently, she has center on test strategy implementation and training, development process efficiency, and preaching Test Driven Development to anyone that will heed. In her downtime, she loves to travel, read, quilt, tramp, and spend time with her family.