Open Source Portfolio Ideas for Testers

As a test engineer, building a portfolio that showcases your skills and expertise is crucial. However, it’s not just about the projects you’ve worked on or the credentials you’ve earned. Contributing to open-source tools is an excellent way to demonstrate your knowledge and passion for the field. The good part is that as of today (2023), only 1% of folks contribute to any form of an open-source project. This means that you can easily join the 1% club by working on any of the below ideas.

99% of Engineers want to use Open Source Tools. โœ…
99% of Engineers don’t contribute to Open Source Tools. โŒ
Contributing to it is damn easy. ๐Ÿงก

Rahul Parwal

These ideas are based on my experience of working with open-source projects and I would love to know more ideas from you in the comments section ๐Ÿงก Let’s share to make this list more exhaustive.

  1. Documentation Fix ๐Ÿ“

๐Ÿ”ธ Every documentation has some gaps.
๐Ÿ”ธ Find those; Fill those.
๐Ÿ”ธ Raise a Doc Bug | Suggest a Doc Enhancement

Get started ๐Ÿš€

  1. Report Bugs ๐Ÿ›

๐Ÿ”ธ Come on, You know you find issues. We all do!
๐Ÿ”ธ Instead of moving on, Report it!
๐Ÿ”ธ Add your suggestions.

Leave the world cleaner than you found it ๐Ÿš€

  1. Retest Bugs ๐Ÿ•ต๏ธโ€โ™€๏ธ

๐Ÿ”ธ In any active repos, there are bugs fixed and waiting to be retested.
๐Ÿ”ธ Add your comments to it

Help the community move ahead faster. Alone, they cannot ๐Ÿš€

  1. Advocate for Bugs ๐Ÿ—ฃ๏ธ

๐Ÿ”ธ In many repos, some bugs are long withstanding and pending.
๐Ÿ”ธ Evaluate those.
๐Ÿ”ธ Add your analysis, associated risk, and impact of the issue.

Help the decision-maker pick important bugs first ๐Ÿš€

  1. Create a Cheat Sheet, Mindmap, and Sketch of the Product ๐Ÿ“Š

๐Ÿ”ธ These are the kind of documentation add-ons that everyone likes to have.
๐Ÿ”ธ Identity, what can you explain in a simple way?
๐Ÿ”ธ Add it and send a PR.

How to send a PR? by Testsigma

  1. Respond to Queries | Issues ๐Ÿ’ฌ

๐Ÿ”ธ Got a query or issue in the forum?
๐Ÿ”ธ Evaluate it. Over 30% of issues are usually duplicates or previously asked.
๐Ÿ”ธ Respond to it if you already know the answers.

Help the community. This is pure bliss ๐Ÿงก

  1. Respond to Surveys | Feedback Form ๐Ÿ“‹

๐Ÿ”ธ Most products suck because we do not respond to them. It becomes a one-way street.
๐Ÿ”ธ Engage Actively.

Help them to help you ๐Ÿงก

  1. Blog your experience report. ๐Ÿ“

๐Ÿ”ธ This is exactly what I am doing right now.
๐Ÿ”ธ Unless you will talk about it; they will never know.

Please talk; express; share; give back ๐Ÿงก

  1. Want a new feature? Add a request. ๐Ÿ†•

๐Ÿ”ธ Start a discussion
๐Ÿ”ธ Maybe there is already a workaround and you don’t know about it yet.

Help them groom their product backlog ๐Ÿงก

  1. You like Coding! Okay, this is for you then: ๐Ÿ’ป

๐Ÿ”ธ Add Unit Tests (They are always short of it).
๐Ÿ”ธ Fix Bugs
๐Ÿ”ธ Implement a Feature or Change Request.

Just do it โœ”๏ธ

Now, after reading all the above points, if you are thinking of which open-source testing projects to start with; here are some good options for you:

  1. dacoaster/yattie: A tool to help testers test. (
  2. testsigmahq/testsigma: A powerful open-source test automation platform for Web Apps, Mobile Apps, and APIs. Build stable and reliable end-to-end tests @ DevOps speed. (
  3. cometa-rocks/cometa: Cometa.Rocks Source Code (

In conclusion, there are many ways for test engineers to contribute to open-source projects beyond just using open-source tools. By taking advantage of these opportunities to give back to the community, you can not only enhance your skills but also help improve the quality of open-source software for everyone. So, what are you waiting for?

Get started and make a difference!

If you liked this article, you can check out this popular post from my blog hits:

Leave a Comment

Your email address will not be published.