Member-only story
An SDET is a developer and not a tester
More and more companies require that both the application code and the test automation code (for UI, API, etc) are written in the same language. This can be Java, C#, JavaScript, Python or Ruby.
The reason is simple.
They want the developers to contribute to the test automation code, read it and maintain it (if needed).
Sometimes, these requirements remain unfulfilled (as application developers do not have time for other things than the application they build) but in many cases they happen.
Moreover, not only the programming language should be the same but the repository as well. The test automation code should live in the same repository as the application code. This may be very useful as the automation project may need and use many classes that the application project has for product or general purpose functionality.
So, you have in the same repository two types of code:
- the application code
- the test automation code
The code is written in the same language, for different purposes and , at least initially, by different teams.
Should the code follow the same rules?
Should the test automation code be at the same standard as the application code?
