Skip to main content
The Workplace

Return to Answer

fix grammar
Source Link
JosephH
JosephH
  • 129
  • 4

My experience of small teams (I'm not sure how small we're talking here, but say 4-6 people) is that it's very unusual to have a dedicated QA person, and even more unusual to have a QA person that'sthat has the skills to build out automated UI testing (which I think is the ask here?). In that size of team maintaining the automated tests is a shared task everyone contributes a very small amount of their time to.

Creating the initial set of automated tests is almost impossible for a non-programmer to do, as you inevitably run into a bunch of bugs in the product that prevent the tests from working properly. The programmers are generally always reluctant to test their code themselves, at least at first, and their chances of finding a good programmer that wants to be "the QA guy" isare small.

So one option might be to pitch:

I'm very happy to help setup the automated tests, but I expect this will mean changing some things in the product so that the tests can work to best effect and reliably, and hence "iOS engineer" is the job title I'd be looking for - especially as once the tests are setup I'll have plenty of time free to work on improving the product.

The only thing to watch for is to make sure the existing engineers are willing to create automated tests (once the framework is there) for new features as they write them. If their engineers are completely inflexible on that point, this is usually a red flag.

My experience of small teams (I'm not sure how small we're talking here, but say 4-6 people) is that it's very unusual to have a dedicated QA person, and even more unusual to have a QA person that's has the skills to build out automated UI testing (which I think is the ask here?). In that size of team maintaining the automated tests is a shared task everyone contributes a very small amount of their time to.

Creating the initial set of automated tests is almost impossible for a non-programmer to do, as you inevitably run into a bunch of bugs in the product that prevent the tests from working properly. The programmers are generally always reluctant to test their code themselves, at least at first, and their chances of finding a good programmer that wants to be "the QA guy" is small.

So one option might be to pitch:

I'm very happy to help setup the automated tests, but I expect this will mean changing some things in the product so that the tests can work to best effect and reliably, and hence "iOS engineer" is the job title I'd be looking for - especially as once the tests are setup I'll have plenty of time free to work on improving the product.

The only thing to watch for is to make sure the existing engineers are willing to create automated tests (once the framework is there) for new features as they write them. If their engineers are completely inflexible on that point, this is usually a red flag.

My experience of small teams (I'm not sure how small we're talking here, but say 4-6 people) is that it's very unusual to have a dedicated QA person, and even more unusual to have a QA person that has the skills to build out automated UI testing (which I think is the ask here?). In that size of team maintaining the automated tests is a shared task everyone contributes a small amount of their time to.

Creating the initial set of automated tests is almost impossible for a non-programmer to do, as you inevitably run into a bunch of bugs in the product that prevent the tests from working properly. The programmers are generally always reluctant to test their code themselves, at least at first, and their chances of finding a good programmer that wants to be "the QA guy" are small.

So one option might be to pitch:

I'm very happy to help setup the automated tests, but I expect this will mean changing some things in the product so that the tests can work to best effect and reliably, and hence "iOS engineer" is the job title I'd be looking for - especially as once the tests are setup I'll have plenty of time free to work on improving the product.

The only thing to watch for is to make sure the existing engineers are willing to create automated tests (once the framework is there) for new features as they write them. If their engineers are completely inflexible on that point, this is usually a red flag.

Source Link
JosephH
JosephH
  • 129
  • 4

My experience of small teams (I'm not sure how small we're talking here, but say 4-6 people) is that it's very unusual to have a dedicated QA person, and even more unusual to have a QA person that's has the skills to build out automated UI testing (which I think is the ask here?). In that size of team maintaining the automated tests is a shared task everyone contributes a very small amount of their time to.

Creating the initial set of automated tests is almost impossible for a non-programmer to do, as you inevitably run into a bunch of bugs in the product that prevent the tests from working properly. The programmers are generally always reluctant to test their code themselves, at least at first, and their chances of finding a good programmer that wants to be "the QA guy" is small.

So one option might be to pitch:

I'm very happy to help setup the automated tests, but I expect this will mean changing some things in the product so that the tests can work to best effect and reliably, and hence "iOS engineer" is the job title I'd be looking for - especially as once the tests are setup I'll have plenty of time free to work on improving the product.

The only thing to watch for is to make sure the existing engineers are willing to create automated tests (once the framework is there) for new features as they write them. If their engineers are completely inflexible on that point, this is usually a red flag.