Friday, May 26, 2017

The Value of Coding as a SQA

This is a very controversy topic and it kind of goes hand in hand with manual testing vs automation testing (which I have written on before).

What is it like black box testing? Is it fun setting up your environment every time you to be a specific way to be able to test a specific feature a specific way?

The short answer is black box testing is a valuable way to test because it more mimics users. Manually doing this is sometimes the only way to test some features especially new features. There is however a way to set environments or automate certain sections of testing that could alleviate your headaches in remembering how to set up a certain environment. It is coding it out to have it automate setting up an environment in Selenium or Ruby or whatever other automation tool you can think of. The issue of course is that you need to know how to use these tools, which for a lot of tools requires coding.

I go back to the title of this post. Is it valuable for SQA to know coding? Absolutely, they can by doing this learn how to use scripts to set up environments they can learn how to completely automate tests, which in turn saves time and money.
Another great reason for SQA to learn to code is that they can Pair-Program. This is a great way of eliminating bugs as they are being coded.

For example, the other day I was pair programming and was able to bring up a use case that was not thought of because I was able to follow the code and the logic of what was being coded up.

In the end it is up to you to figure out whether you can learn to code and if you could set up any form on automation or pair programming, but I would recommend it. It is, in my opinion, well worth the time to learn because it saves both headaches and time