• @rockSlayer
    link
    69 months ago

    That’s what QA engineering is for. They are integrated into the dev team and they pull double duty with QA and code review.

    • @[email protected]
      link
      fedilink
      119 months ago

      In my company QA is dedicated to manual and automated tests. I haven’t met many QA engineers who could effectively review any of my code.

      • @rockSlayer
        link
        39 months ago

        I’m thinking of it not as a title, but a role. Often times the 2 are not related

          • @rockSlayer
            link
            19 months ago

            A title is just something a company calls a particular job. A role is what that job actually is. So a lot of jobs might be called “QA engineer”, but not fitting the intended role

            • @[email protected]
              link
              fedilink
              29 months ago

              Gotcha. I mean, all software engineers should do some QA engineering, but we have QA engineers who are the experts and “QA coaches”.

      • @[email protected]
        link
        fedilink
        29 months ago

        As a qa engineer this makes me feel better about myself. Because I’m included on reviews but never know what I’m looking at.

        • @[email protected]
          link
          fedilink
          29 months ago

          I’ve worked in places where QA we people with no coding knowledge who just clicked around looking for bugs, as well as places where QA never did that, only automated tests. And then there are places that believe hiring QA is useless, because “everyone should do QA”.

          • @[email protected]
            link
            fedilink
            19 months ago

            This is my first big career job and in my limited experience I think I support the idea of a second pair of eyes, with a hybrid on automated testing. It seems more comprehensive and thorough than having a single person work on a task (minus code reviews).