How are your projects set up working with an outsourced testing company?

While developing the Software Testing Essentials Certificate, we’re developing several diagrams to describe where testing fits in.

One diagram describes outsourced testing, or if you like, Testing-as-a-Service (TaaS) or a Testing Centre of Excellent (TCoE) setup.

I’d love to know:

  • If you’re a tester/QA person working for a Testing-as-a-Service company, what sort of testing approaches do you take? How are things set up where you work? How do you get involved in projects with your clients?
  • If you’re a tester/QA working with a Testing-as-a-Service company, how are things set up? What sort of testing do they do for you? How do you communicate with each other?

Have seen and been in both situations.

Testers were working with the team in the sprint.

Their accesses and stuff had to go through a more rigorous route / process at times.

However, once the tester is in the team, they are usually part of the game including all scrum meetings. They are usually out of the organization meetings, quality programs, etc.

Communication & Basic tooling happen like we do it with the team (Jira, MS Teams, Emails, Gitlab, etc.)

In case they are not integrated in the team for a while, then they are interfaced with a developer or tester from the hiring company and they host a weekly or bi-weekly meeting to catchup on the updates and doubt solving.

1 Like