How can SDETs improve test script reading & understanding for complicated code bases?



  • Recently I decided to explore some open source projects. I think it's a good way to learn more that how experienced SDET/Test Architect approach in their design. I found myself a little overwhelmed by the projects I looked at it. With my level of experience, it was hard to understand the body of code I faced.

    This has been a great experience to know the approach the task of understanding a new medium to large scale project. Now I found myself struggling to understand someone test script. At sometime I feel that I could understand a small portion of the system but not see how its all fit together. Do others get this same feeling? If so what approaches do you take to understanding the project? Do you have any other advice about how to learn design best practices?



  • "A journey of a thousand miles begins with a single step"- Lao Tzu

    Go Small .I would start with a known open source project- most likely an automation library which I am already using .

    I would make a list of interesting API methods which I am using on daily basis and curious about how they work under the hood.

    In this way I will take small baby steps to understand those methods specifically and may be try to write documentation for them.

    This way somewhere down the line, I would feel more comfortable with the library as whole and will start to see the bigger picture. As I will be more comfortable , I would try to fix small open issues in the codebase. And on and on...



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2