Will we ever really be at 100 % automation? I hope not. Of course automation is critical in implementing Continuous Integration and Delivery, but there are simply some things that you can & # x27; t leave to a machine. Human evaluation is important. In a world where we are appear to release faster and quicker, why would we want manual try? Let & # x27; s conduct a expression at some of the things you may want to do that mechanization can & # x27; t, and how manual evaluation helps us present the correct product.

The human aspect

Several years ago, our UX team kept asking, & quot; Is it delightful? & quot; I ’ ve act on many features that I truly felt would make for a best experience in education. There are various that, frankly, I just couldn ’ t stand. We just weren & # x27; t building therightproduct sometimes; even if all tests legislate, and there were no bugs — if I didn & # x27; t like using it, I establish myself asking, & quot; How would users feel? & quot; I hold to say, I & # x27; m capture by the human factor and evoking feeling (for better or worse) when essay package. As a consumer of package, sometimes I bump myself thinking,Wow, did ANYONE look at this?(For example, I & # x27; m on the Board of Directors for my Home Owner & # x27; s Association, and the package we use to track document, get assessment, and so forth just get me want to cry). I & # x27; ll be honest - sometimes it is difficult to see how functional something is until there is something to use it for. Hopefully, though, we can spot this former as we define acceptance criteria and are evaluating the workflows, spectacles, wireframes, or prototypes.

Be like Lewis and Clark

The obvious manual examination action that should be at the top of everyone & # x27; s list is explorative testing. In an ideal world, the characteristic themselves are completely automate, and development is done when all tests pass. This is fantastic, but what if that were it? Lewis and Clark had specific goals, and reported what they ground along the way. Exploratory testing is similar to me: I start with a charter (or a destination) from a user view, and report what I find along the way. Perhaps it is a feature that works fine in unit and integration trial, but once I commence appear at it myself in an end to end workflow, I think of early scenarios that peradventure we didn & # x27; t think of when writing script.

One of the biggest success I & # x27; ve seen late is with a bug bash. This activity is open to people still outside of our dev team. As characteristic complete development and pass initial cycle of testing, we open them up to a bug belt. People from QA, Engineering, UX, Product Management, Support, and beyond have been involved, go a wide range of perspectives and scenario that perhaps were not think of before. Use exploratory testing to your advantage — there is no one way to do it. Do what work best for you! Get different perspectives, think like the user, and see how the product get you feel.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Testing for everyone

Another area of testing that I & # x27; m real passionate about is Accessibility. Not everyone uses the Web in the same way. (To see some of the many ways in which someone may be hinder, read more in this bewitching situation:https: //the-pastry-box-project.net/anne-gibson/2014-july-31). Yes, there are tools and scans that can be utilize to check for standards. But if I don & # x27; t check for handiness manually, how can I live whether keyboard navigation occurs in a ordered order when tabbing through, or know (by seeing it in person) that what the screen reader calls out makes sense? To celebrate Global Accessibility Awareness Day, we recently held a bug bash where we asked users not to use a mouse. While most features held up easily to the challenge, it gave us more perspective on trying to construct the right product, and building one that is delicious to use. (To memorize more, read:http: //blog.blackboard.com/mouse-free-an-accessibility-challenge/).

Mobile everywhere

Consider that we live in a world where most people are accessing your software on their nomadic devices. Now consider what you look for in an app. Personally, there have been moments where I & # x27; ve tried out five or six running apps — but to quickly delete most of them after about ONE MINUTE if they aren & # x27; t user friendly or don & # x27; t see my needs. ONE MINUTE. If you don & # x27; t direct time to run through your app and explore how it is to use, why would your clients? If I can & # x27; t figure out how to do something cursorily, I & # x27; m pretty much do with that app. DELETE. (Don & # x27; t let that be you.)

Putting it all together for continuous delivery

I hope it & # x27; s pretty open that manual testing can emphatically help you deliver the correct ware to users, and a fun one at that. Of course you don & # x27; t want to save manual testing for too late (the cost keep rising the ulterior issues are account), so try and find a happy proportionality from your feature/dev branches to the examination environment, and you will start seeing the usability lots earlier. Although Continuous Delivery provides for a constant feedback cycle and chance to memorize and fix issues speedily ground on that feedback, use manual examination to your advantage and make clients happy from that first (or thousandth) freeing!

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 enjoy coaching team members in product and client-focused quality practices. Most lately, she has focused on test strategy execution and training, development procedure efficiency, and advocate Test Driven Development to anyone that will listen. In her downtime, she loves to travel, read, quilt, hike, and spend clip with her family.

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