Don't bore or bamboozle your stakeholders with lengthy test plan documents. Use these leaner, simpler, more easily digestible options instead. When writing a test plan, keep the 5 W’s front of mind: What, When, Who, Where, hoW.
In my experiences of planning for testing in various environments, and across several teams and organizations, the value of that planning was never the document itself; rather, it was the thoughts and consideration of the activities, resources and potential risks and issues yet to be discovered. Thinking deeply about all of those things and writing them down, in whatever form the final document took, was the real value of the exercise.
Having those thoughts documented can of course be useful when you need to communicate the testing activities across a team of subordinates. It’s not quite so useful for communicating your intentions as they relate to testing activities to your stakeholders. It’s far better to have those people in the room with you while you’re formulating your plan so that they can provide you with the information you need to do that planning; and so that they have a say in the what, when, who, where, how of your test plan.
Dialexa's very own Stephen Kilbourn teaches us about how better understanding unit testing can be utilized to create collaborative testing plans. Dallas QA A...
The shift towards microservices and modular applications makes testing more important and more challenging at the same time. Learn more here.
API endpoint when you send the get request to that URL it returns the JSON response. In this article, I am going to use postman assertions for all the examples since it is the most popular tool. But this article is not intended only for the postman tool.
The demand for delivering quality software faster — or “Quality at Speed” — requires organizations to search for solutions in Agile, continuous integration (CI), and DevOps methodologies. Test automation is an essential part of these aspects.
What do you do when you have lots of free time on your hands? Why not learn test programming strategies and approaches?