Developers in my team rarely create documents to support testers such as release note, or specification. I often go and ask for more information.
Why do they hate create documents while testers really need them for testing?
Developers in my team rarely create documents to support testers such as release note, or specification. I often go and ask for more information.
Why do they hate create documents while testers really need them for testing?
© 2024 AskTester
Theme by Anders Noren — Up ↑
Like it or not, writing specification is a boring tasks to me and it’s no surprise that your developers do not write much documentation for your testing.
We can force developers to write those but that’s not a long term solution. My suggestion is to call a meeting and discuss why we need documents. If all agree that documentation is necessary, let’s do that. If not, just adapt that and change the way you do the testing. What you should do is to discuss more with team to have the information you need.
Hope it helps