During nearly every project I hold worked on, the interrogationCan I test everything?always come up. The answer is (usually) a resoundingNO. Sometimes it & # x27; s because of time, sometimes it & # x27; s lack of people. How can we even ensure a quality product, even if we can & # x27; t cover it all? Sometimes, we have to test smarter.

The common suspect

The typical scramble to finish examination and get something released is usually (in my experience) a result of one of the next (or a combination thereof):User stories that are WAY too big. When user stories are too large, it create it difficult to break out task and identify all the espousal standard. They also become more unmanageable to plan for unanticipated scenarios, and can often blow estimates out of the H2O.Complex Workflows.Depending on your characteristic, the workflow could be very complicated, and it can be difficult to expect how a exploiter is actually proceed to use the product. This makes it more challenging to find every possible scenario for end-to-end tests. Even if your user narrative are modest, the overall workflow contain all user stories can nonetheless result in missed tests if it is too complex.Not using Test Driven Development. If you are still go in a world where Development works on their own and throws it over the proverbial fence to QA, you are opening up doors for late surprises to enter, and blocking bugs that hinder your screen procession.Date-driven releases * *.Have you ever worked on a labor that individual has already told stakeholders will be delivered by a sure engagement? A sure belligerent date? I feature. These projects are no fun. If Development is behind docket, but you still feature to release on a certain date, how does that impact testing?Supporting too much * *. Thinking about everything in a project that might receive to be supported makes my head twist. Considering the number of versions of a product, browsers (and browser versions), mobile device, operate systems (and so on) can give anyone a cephalalgia. Is it really viable to get 100 % test coverage across everything you say you indorse?

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

Then what?

The list seems stacked against QA to furnish adequate coverage. But, in reality, do weneedto cover everything? Not if you are testing smartness.First and foremost, make those user story small!If they are small enough, it is far easy to identify acceptance criteria and guarantee reporting (at least for that isolated feature). You should still aim for the try triangle (mostly unit, some integrating, very few UI).Understand your paladin workflows!Everyone is different. There is no way to predict (in total) how your users will interact with the scheme. But you CAN know what most users will do. Have you talked to your designer or UX lately? You should. Understanding these workflow can help identify what you really need to cover (and hopefully automate), and leave any askew scenarios for exploratory examination.The Pareto Principle.Test smart. What are your areas of biggest risk? Ask yourself —How can I do as little essay as potential to uncover the most glitch?20 % of your tests should find 80 % of your bugs. If you have an area that has had few bug in the past, do you want to put too many resources into it? Or would you rather focus your resources on an area that is consistently a trouble?Big Data.I have to admit, I used to cringe when I see this buzzword, until it helped me. Finding out what clients were do, what browsers they were using (speck: not IE), and what they were clicking helped regulate my exam strategies. I so knew where to focus my testing and my team to make the most of what time we had.

It ’ s a Team Thing

No, we & # x27; ll never be able to test it all. But we can plan, and test, by testing smarter — though remember that it is the team ’ s responsibility to find the correct coverage! This is not just on you, the tester. We can drive conversations and make recommendations, but the team should adjudicate when we can ’ t test it all, and what we should test.

Ashley Hunsberger is a Quality Architect at Blackboard, Inc. and co-founder of Quality Element. She ’ s passionate about make an impact in pedagogy and loves coaching squad members in product and client-focused quality practices. Most recently, she has focused on test strategy implementation and training, development summons efficiencies, and advocate Test Driven Development to anyone that will listen. In her downtime, she loves to travel, read, quilt, hike, and spend time with her house.

T: @ aahunsberger L:https: //www.linkedin.com/in/ashleyhunsberger