4 ms·

I agree. What about a situation wherein you have a QA team that stands entirely apart from the devs and they are the holders of the specification?

bluGill 4y ago
Automate the tests. Sure the QA group holds the final say, but if you have a test that breaks you don't have to ask them. Or at least you have something to base a.conversation on. Note that requirements change, and bad tests will break on no requirements. Telling the difference is an exercise for the reader.
- bentobean 4y ago
  The tests are automated… by the QA team. Using a web-based tool for which none of the devs have access.
  - ghotli 4y ago
    I see two ways forward, both probably not great advice. 1. Ask for forgiveness and do whatever you think is prudent regardless of org structure. 2. Find a better org structure elsewhere :)
    - bentobean 4y ago
      I tend to agree. When I am capable of summoning the energy to care at this point, I make a run at #1. I have recently decided to actively pursue #2, as well.
  - bluGill 4y ago
    Write your own automated tests that you control.
- dathinab 4y ago
  One of the most common tasks for QA teams is to write automated "outer layer" integration tests.
  - jimmaswell 4y ago
    You guys have QA teams that know how to code?
    - BlueTemplar 4y ago
      I've seen a recent multi-months training course for testers. Half of it is manual testing (culminating in a website-related project), the other half automated testing which includes learning some Python.
    - bluGill 4y ago
      I have multiple QA teams. Some are straight up regular users who cannot write hello world in any language. Others are programmers who got hired to write and maintain our QA end to end suite. A good end to end QA suite for a large project is complex enough that it needs everything any large software project needs: architects, tech leads, and all the other technical staff.
deleted 4y ago
[deleted]
lmm 4y ago
Don't do that?
nullsense 4y ago
Really don't wish to go back to this. We don't have QA teams or QAs where I work anymore. We can get changes to prod much faster and our test suites are growing to be pretty high quality for the stuff our team owns.

bluGill 4y ago

Automate the tests. Sure the QA group holds the final say, but if you have a test that breaks you don't have to ask them. Or at least you have something to base a.conversation on. Note that requirements change, and bad tests will break on no requirements. Telling the difference is an exercise for the reader.

bentobean 4y ago
The tests are automated… by the QA team. Using a web-based tool for which none of the devs have access.
- ghotli 4y ago
  I see two ways forward, both probably not great advice. 1. Ask for forgiveness and do whatever you think is prudent regardless of org structure. 2. Find a better org structure elsewhere :)
  - bentobean 4y ago
    I tend to agree. When I am capable of summoning the energy to care at this point, I make a run at #1. I have recently decided to actively pursue #2, as well.
- bluGill 4y ago
  Write your own automated tests that you control.
dathinab 4y ago
One of the most common tasks for QA teams is to write automated "outer layer" integration tests.
- jimmaswell 4y ago
  You guys have QA teams that know how to code?
  - BlueTemplar 4y ago
    I've seen a recent multi-months training course for testers. Half of it is manual testing (culminating in a website-related project), the other half automated testing which includes learning some Python.
  - bluGill 4y ago
    I have multiple QA teams. Some are straight up regular users who cannot write hello world in any language. Others are programmers who got hired to write and maintain our QA end to end suite. A good end to end QA suite for a large project is complex enough that it needs everything any large software project needs: architects, tech leads, and all the other technical staff.

deleted 4y ago

[deleted]

lmm 4y ago

Don't do that?

nullsense 4y ago

Really don't wish to go back to this. We don't have QA teams or QAs where I work anymore. We can get changes to prod much faster and our test suites are growing to be pretty high quality for the stuff our team owns.