Wednesday November 14, 2018
Around 90% of the test automation community doesn’t know test coding, rather just a small percentage of the people know their tool, program and they understand coding as well.
Most of them go for the easy way!
Most hacks occur because individuals can’t afford real options, lack access to appropriate products which exist in a market that just doesn’t recognize their requirements. This similar strategy which is infused in our nature is applied by the test automation engineers.
There are primarily 4 types of automation tester who adapt to simple hacks for performing automation testing:
1. The Now Syndrome Tester: Whose aim is to fix the code now and rest will be tackled later on and that never again arises.
2. The Lazy Tester: These sorts testers have no time to write the codes or to learn new from the projects.
3. The Never-Failing Tester: Whatever arises these testers will make the test pass.
4. The Cod Puzzler: The testers who don’t know what they are writing in the codes.
So, what is the wrong way of coding? When you have utter disregard for anything you do that work monotonously.
You try to find the easiest solution to deliver the result as soon as possible, no matter how you are doing it.
Such kind of attitude is clumsily adopted by someone who is not proficient in the field. This is what people are doing in test automation projects, who know nothing about coding or don’t even want to the learn proper way.
There is a good chance that a failed automated tester will be having the following symptoms:
Rather than modeling tests every time, writing four lines of code and using test assertion from the test engine, and trying to catch bugs every time, testers believe to do 10 lines of coding.
They give weight to quantity instead of quality. And the good news is many of these code snippets technique is used all around the world, not just in India.
But it’s not something to take pride in because it basically is not the accurate method of testing.
Let’s have a look different types of coding shortcuts/hacks strategies applied by automation testers which categorize them as failed testers.
1. For Loop Method
Almost 38000of lines go through thought work, test runners don’t use test engine, especially in C#.
They start with the for loop for first 10 tests, then read the copied codes from excel and make this a regular procedure that sums up to 25000 tests.
This is the method of for loop with hardcore process calls. And these are really easy to accomplish automation test hacks which might seem unbelievable.
However, it’s a bitter reality of how unlearned testers are performing automation testing these days.
2. Duplicating of Tests
Another instance of such improper automation testing approach is taking one copy of tests as the point the variable changes in another scenario, even operating system changes but copied the content of code is taken in all the environments.
It’s never revealed by testers that the copy of the same test from a previous one is performed instead they tell that is was the same kind of test.
And this is done continuously on different scenarios. Moreover, after a certain time, the test code does not remain the same but it becomes similar since difference always occurs in automation testing–it’s impossible to refactor the code.
Since right testing is an outcome of hard work, not the hack of using “control + C” and “control + V” technique from the excel sheet –this is an extremely bad habit in coding and testing.
Spreadsheet IDE for Keyword-Driven Testing
There are many cases of test automation engineers who have complete codes saved in their excel sheets which they use in their keyword drove testing process.
Hence, in this way keyword driven testing has outlasted its purpose. Why? There are tests that need coding than some other tests require well representation by employing the keyword driven strategy.
But this addiction to copying code from spreadsheet practice has eventually ruined the whole process.
The automation testers are simply reading and copying from their spreadsheets, do string formatting, generate the C# file, organize it at the runtime and run the code!
Such failed testers don’t know how to model, even don’t want to study C# or.Net reflections just take the easy road to test, i.e. copying the codes. And this pathetic hack is run in almost all the keyword driven testing.
4. Researching Approach
Individuals nowadays state they are researching to learn better coding skills, but here too such testers use Google search engine to find the shortcut solutions.
The testers open the links from the first few results of the Google page than they directly apply the same strategy –copying&pasting the codes from these links.
They do not model it; even they don’t notice that these codes already exist in their previous spreadsheets, because such automation testers are not trying to understand the real and accurate intent of testing. Surprisingly, they proudly declare that they write so many codes in a day.
5. Delete Assertion Rule
Further, these types of unprofessional automated testers work on the goal of deleting the assertion.
It’s our duty that in case that the automation testing begins to fail, we need to work on them rather than thinking that company will consider us a bad tester if we show them the failed testing results.
So, to save them from a shame the automated tester deletes the assertion which is a total misunderstanding of performing the test automation properly.
There is nothing wrong if a test fails basically, the goal is not passing the test. But the rule in an unskilled tester’s diary is – comment – run the code – create the report – uncomment it, eventually to pass the test anyhow.
6. Repeat Testing Technique
Then there’s a repeater automation tester. What is this type of tester’s goal?
The person doesn’t want to learn multi-threading so he/she instead of solving any issue will read it only once per test considering there are merely 10 or 12 tests that need to be run, so it’s fine using such technique! Most of the testers are working on this strategy.
So, the same file is read hundreds or thousands of times rather than learning something new.
Consequences of using Coding Hacks in Test Automation.
To be honest, never can an automation testing be performed and achieved in this way. Hence, the test automation is not at all meant for the failed developers, knowing nothing about testing and coding.
Testing is not for everyone, not just for anybody who doesn’t know to code appropriately. In fact; automation testing is also not for the one who knows a few codes.
This great process needs right aptitudes, understanding of coding languages and eagerness to further learn something to sharpen the testing skills.