Test documentation describes the artifacts created before, during, and after testing for the purpose of communicating with stakeholders to solicit feedback, to capture your intended approach to provide guidance for your team, to provide actionable information for business decision makers, and to ...
"Is this going to be a stand-up fight sir, or a bug hunt?" - Hudson I've always wondered what the secrets were to writing a great bug report. Over time I've narrowed down the activity to three ...
I've been in many difference sized companies and in many different environments where we've used terms interchangably, Testing Terms, Development Terms and Process types have been overloaded in one ...
In Agile we favor immediate communication over documentation. Yes in QA we still have a need and desire to document the process to provide structure and guidance. What high level structure in our ...
I need to write and execute some test scripts and provide evidence on a short time-frame. The basic scenario revolves around creating work requests in one system, and approving or rejecting them in ...