In the yesteryear, in order to be a workable contributor in the world of Quality Assurance, all you had to know was decent about computers to run an coating and how to gather test results. Today, as test mechanization becomes a more critical prospect of the QA landscape, testing practitioners need to know how to program. That 's the simple, cold truth. Manual testing is fall by the wayside.

Moving to automated testing

Most companies still doing manual test realise the need to move to automation. But, moving a QA Department from manual to machine-controlled testing isnot as easy as just send the manual examiner out for re-education. In fact, many company that send their manual tester out for “ training ” fail. Why? Mostly for two intellect. First, some employees simply have neither the interest or aptitude to learn the programming skills necessary to do machine-controlled screen. Second, many companies whole lowball the depth of apprehension and work required for even the well-nigh able employees to acquire the knowledge and skills demand to contribute effectively in footing of test automation.

So, what ’ s to be done?

The reply is to change the posture and behavior by which employees and fellowship approach moving to prove automation. Companies that genuinely want to make it so that those moving from manual to automated testing are successful will do good to accept the following 4 affirmation:

1. Accept that even the easy stuff is hard
2. Accept that larn to do abstract thinking counts
3. Accept that you necessitate to be uncoerced to do whatever it occupy
4. Accept you need to programme every day

Allow me to elaborate.

Accept that even the easy stuff is difficult

As much as some of the conventional wisdom will say you otherwise, test automation programming is difficult and learning to do it is even harder. Yes, there are some people out there that have a knack for coding. But even these people will end up spending hours, if not days, trying to solve a ostensibly elementary problem to which the answer might be something as trivial as place a misplaced comma in a line of codification. There ’ s a lot of item that goes with the art and skill of coding.

Thus, any person or company transition from manual testing to automation needs to understand that when it comes to scheduling, even the easy stuff is hard. There is no pill to be swallow that will magically inject the considerable knowledge and cognitive skill required to do even the most basic programming required for test automation. Individuals and companies must be willing to invest the clip and do the work required to become competent, even at an elemental level. It ’ s more than a matter of a week or two of training. Getting a true understanding of the bedrock can be a process that can go on for months. Remember, we ’ re verbalize about changing how people think. This takes time. If the person or company is not uncoerced to make the commitment of time and effort only to learn the basics, failure is more likely than not.

Accept that learning to do purloin thinking counting

No affair what form a company ’ s test automation drill take, those wanting to act in automation testing need to not only learn the BASIC of programme but also perfect a highly developed understanding of abstraction.

Being capable to convert testing scenarios into code means developing the ability to define entities and conduct in a conceptual manner, a.k.a, the ability to nobble. Being able to name general patterns from a variety of test instances provides the base for scalable test mechanization. One test design, properly understood, can be applied to many quiz scenarios. Not only does abstraction cut the price of test automation by elevate reuse, the actual scheduling is a lot more fun. It ’ s the analogical conflict between writing a formula for making chocolate chip cookies and project a baking process that can create a number of different types of cookies.

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

Developing an acute sense of abstraction requires a special way of looking at the domain. And, it takes time. Yet there is welfare. When you can seem at your reality in an abstract manner, transforming test scenarios into code will become second nature.

Accept that you need to be willing to do whatever it lead

There are two things I ’ ve noticed about people that are very successful in take new skills. First, they will do whatever it takes to get good. Second, they tend to surround themselves with people that are already very good at what they do. It ’ s like playing tennis. You always want to play against citizenry who are best than you. You need to improve to keep up.

As competitive as the world of mod programming may be - and it can be very competitive - the professing has developed a benevolent attitude toward helping those who want to discover. Today any aspiring person can learn to cypher by spending an innumerous amount of clip watching videos on YouTube and studying codification on GitHub. It wasn ’ t always this easy. Before the Internet came along, when you wanted to larn to cypher and you couldn ’ t afford the time or money to do formal study (a.k.a, go to college), you had to say a lot of book and/or know someone who knew programming who was willing to help you learn. Today we ’ re yield it off, literally.

Doing whatever it takes to be feasible execute not discontinue once the initial teaching experience is over. Technology is changing too quickly. There is always more to learn. One technique that many companies use to acquire the skills of its technical staff, as well as improve codification character, is to absorb in pair programing. Pair programming is when two programmers work on the same body of code together on a individual computer. It ’ s as if two minds are coding as one.

Companies in the know realize the welfare of enforce some stage of pair programming, either formally or informally. In terms of professional development, I can attest to the fact that I ’ ve perpetually benefited from a pair programming session, regardless of whether it ’ s with someone junior, or older to me. I always walk forth smarter.

Pair programme offers significant welfare In price of examination automation. First, the tests will likely be better in that two minds often best than one. (Ten minds, not so much, see Fred Brooks ’ s book,The Mythical Man Month.) Second, both party will learn something new and improve. For the wishful test automation engineer, pair scheduling can be a highly efficient educational experience supply he or she is uncoerced to accept the cerebral vulnerability that come with the attempt. It can be anxiety provoking. Yet, disclose one ’ s weaknesses to another person is a little price to pay for the enormous benefit to be gained.

Accept that you need to program everyday

Programming is like playing the piano. You need to do it everyday to reinforce and establish upon what you ’ ve memorize previously. Make every learning session tally.

Those who experience taken the time to acquire the necessary knowledge and skills to become effective at test mechanization must be yield the opportunity to use what they get learned everyday. It makes no sense to invest time and money to assist an employee to get competent at programming only to have him or her go back to doing resultant manual testing while waiting for an opportunity to come along to work on an mechanization undertaking. Nor does it make sentience to have employees hire in automation action periodically.

If a fellowship require to have automation as the foundation of it testing activity, it must allow those creating the mechanization to rest active consistently and continually. Otherwise, as the saying goes, “ if you don ’ t use it, you lose it. ”

Putting it all together

Programming is fast becoming the lingua franca of mod QA. There will nevertheless be require for manual examination for complex test scenarios beyond those usual for typical occupation applications. But for the most component, manual testing will become the exclusion rather than the rule. To work in QA in the modern enterprise mean cognize how to cypher.

Learning the programme skills required to work effectively in tryout automation requires time and commitment, both from employee and the companies for which they work. Those that are successful will see the inherent trouble of the work. They understand that even the leisurely stuff is difficult. They will understand the importance of abstract thinking in modern trial automation. They will make a loyalty to make an environment in which learning is continuous and unchained. They make certain that acquired skills are not left to wither forth due to inaction. In short, both the employee and companionship will be unforced to do whatever it takes to apply automated testing in a manner that is effective for the long term. To do otherwise is to follow test automation at your own peril.