Why are we “Software Developer” in Test? (Part 1)
Hi folks!
In this article, I’ll be sharing my personal perspectives and insights.
Are we “Software Developer” in Test because we create automated tests?
Not!
We are testing applications developed with different technologies.
We can write Java, javascript, HTML, etc. This means we can understand how applications are working and coded technically. Also, this means we should not test business logic only. We should know what happens in the application code base. Why? Let me explain with an example.
I encountered a situation when I tested a feature. We had a new feature for our React Native application. Expected business logic and UI are defined before the feature is developed.
I found a bug after the feature was developed. A text was supposed to be bold, but it wasn’t on Android. It would be a waste of time to forward this bug to the developer and wait for it to be resolved just to bold a text. How it would waste time?
1- Tester creates bug
2- The developer sees the bug issue cart on Jira bord and examines the bug. (Btw, when will the developer see this bug? Will the developer have free time?)
3- The developer creates a new branch
4- The developer debugs the code to find the reason for the bug
5- The developer fixes the bug and commits
6- The developer creates a merge request
7- The merge request is reviewed and approved, and then it is merged.
These are basic steps for a bug. Think about it! These steps will be applied only to make the text bold. Is it needed? Should it be? Why waste time?
I have the code base of the application. I searched the text on the application and found it. The code with bug is below
I only changed the following statement
I created the merge request and redirected the merge request to a developer to review and approve the merge request. And we are happy! We found the bug and FIXED! the bug. I think we did this job as a “Software Developer in Test” should do.
Should we only do these for small bugs? Never!
Because if we know the code of the app we can;
1- understand, if a feature is applicable.
2- inform and remind the teammates about the features as technically.
3- test better
4- WE CAN DEVELOP A FEATURE! AS A SOFTWARE DEVELOPER IN TEST! WHY NOT?
Join Us
We’re building a team of the brightest minds in our industry. Interested in joining us? Visit the pages below to learn more about our open positions.
