How a tester can become a great developer?
Today we were having some good discussions in the office with a colleague. It all started when a newly joined colleague asked about testing and wanted to know how testing jobs could be a good stepping stone to becoming a developer. I thought that some testers start their initial career as a tester and gradually become good developers.
In order to become a good developer, there are some skills that are required. Some of the skills have to be unique and some skills have to come through experience. The skills someone acquires from testing are very important and that definitely helps to become a developer. It is a general belief that testers are always tough people who expect more perfection in everything. Usually, it is understood that way but it is not the case. They are the people who follow the protocol and reach the result.
Good developers are always good testers
In order to be a good developer, it is also important that they have to be good testers too. People have to learn more about testing and the application they develop should also be developed with many client test cases in mind. The developers who test their own code multiple times usually become very good developers. While doing multiple rounds of testing, the end product becomes high quality and with significantly fewer bugs.
When a developer understands the importance of quality, they tend to deliver a good and valuable product. They are able to get used to the quality and they try to maintain the same quality. One thing that testers usually lack is the idea to fix issues. They are usually good at finding defects but they don't care how the issue is fixed. But developers who have experience with their new learning can also make some good suggestions as to how the issue can be fixed.
Testing from a client perspective
Testers usually have a great understanding of the system. Whenever a tester is onboarded to a product, the first thing they have to do is understand the product. Only then they will be able to validate the product and raise defects if it is not up to the mark. Testers who are developers usually get an additional perspective where they are able to think from the client's perspective and they are able to come up with solutions that are client-friendly.
Testers usually know the expectations of the clients and from their experience, they are able to understand what can be made better. This is what happens if they are given the opportunity to think from the client's perspective. When this happens the outcome of the testing becomes very good.
Reduces burden on a testing team
I can even say that if a tester becomes a developer, they give tough times to the testing team. Usually, the testing team, might run with targets on how many test cases were executed and how many defects were identified. If a tester is going to be a developer, the product may not have any major issues when it comes to the testing phase and it might reduce the burden on the testing team thus making it hard for them to raise defects.
If you like what I'm doing on Hive, you can vote me as a witness with the links below.
|
|
|
|
|
|
Posted with STEMGeeks
This post has been manually curated by @bhattg from Indiaunited community. Join us on our Discord Server.
Do you know that you can earn a passive income by delegating to @indiaunited. We share more than 100 % of the curation rewards with the delegators in the form of IUC tokens. HP delegators and IUC token holders also get upto 20% additional vote weight.
Here are some handy links for delegations: 100HP, 250HP, 500HP, 1000HP.
100% of the rewards from this comment goes to the curator for their manual curation efforts. Please encourage the curator @bhattg by upvoting this comment and support the community by voting the posts made by @indiaunited..
This post received an extra 20.00% vote for delegating HP / holding IUC tokens.
@bala41288, @pixresteemer(10/10) sent LUV. | connect | community | HiveWiki | NFT | <>< daily
! help
(no space) to get help on Hive. InfoGeez dude, how are you posting daily but can't be bothered to respond or curate the few genuine comments you receive?
Yes agreed. I used to do it regularly. It was part of my routine. Recently I had some lifestyle changes that affected my engagement.
I will make sure I allocate some time to engage more. Thanks for mentioning it.
Usually testers are used to put an application to the test; it's not certain, though, that they are prepared at the code level.
When this happens, you have the best, because the tester knows where the problem is and already gives the developer a solution.
Over time, the tester also becomes familiar with the code and may even become a very good developer
Yeah maybe a tester may not have knowledge on the code initially. But logic wise they would be very strong and they can easily pick up all dev concepts.
I agree, testing is a really good stepping stone to becoming a good developer. I have seen some testers doing automated testing and having a better understanding of their product code than some senior developers. I think though, if you are a tester, you need to be open to new things and simply manually testing a product is not going to help you become a good developer. !LUV
@bala41288, @strava2hive(1/1) sent LUV. | connect | community | HiveWiki | NFT | <>< daily
! help
(no space) to get help on Hive. InfoThe testing industry has improved a lot in the last few years and the scope for manual testers is slowly reducing. Testers will also have to be innovative and find new solutions.
Good software testers must develop and run automated tests. Testers often create python scripts.
Some developers will dislike what I am about to say, but I think it is good for software testers to run tests that go step by step through a program. This is especially true on open source products. Testers who have access to the code will become intimately acquainted with the code.
!WINE
Yeah by thinking as a tester they get better than a developer.
Most of the developers we have today also started as testers so it is nothing new for a tester to become a developer, with the combination of the two, be ready for a quality brand
Yeah the combination of two is definitely a good one.
For the agile development method the developers used to do their own tests to speedup the process. Specially for a white-box testing the development team itself tests, finds and fixes the issue before it goes ahead. And during black box testing, testers don't bother (neither they need to actually) about the code as they suppose to find corner cases.
But yes white box testing indeed makes the person more aware and efficient.
Writing exhaustive test cases is actually critical to any project development and robustness of the final product. I believe its an art as important as to write code.
Yes I agree with your points on writing exhaustive test cases. Some development teams are also moving towards a model where they don't have any developers in the team one persons dev work is tested or automated by another developer.