Home > front end >  How do Devs share relevant testing information with Devs-in-Test and QAs?
How do Devs share relevant testing information with Devs-in-Test and QAs?

Time:07-06

One of the problems our group is having is in regards to sharing relevant information between the Devs, Devs in Test and QAs.

How is this typically done in the industry?

For instance, our devs typically follow TDD with CI/CD pipelines offering the capability to illustrate code coverage. Do devs in test and QAs typically review coverage numbers prior to construction of integration and manual test plans?

How are devs typically communicating edge cases and relevant test procedures to the testers these days?

Finally are there any great resources (docs, podcasts etc) that discuss these types of things?

CodePudding user response:

In my experience, there isn't a whole lot of such information shared between DEV and QA, apart from the requirements, things like API documentation and maybe usage examples. The reason is simple: Developer tests (unit, integration) are usually whilebox tests, while tests performed by QA are usually blackbox tests (i.e. oblivious of the code being tested). What use is a coverage report for blackbox tests?

  • Related