Release Notes: how to test technical accuracy

Grasshopper, what do you after you’ve written your release notes? Test it. Here are four ways to check if the bugs, issues and enhancements are written correctly: 1. Can you reproduce the issue? Have you reproduced the issue on a local machine? Note that you’ll need the same version of the application that the bug […]

Software Testing: how to keep Agile projects on track

Is Agile software development good for a tester’s mental health? Depends, doesn’t it? So, how can we keep software testing projects on track when the Developers are using Agile to create sprints? What do we need to ask our developers? Ask Dev to confirm THEIR understanding of UAT It’s not enough to ask, ‘do you […]

Release Notes: 7 Steps to Better Enhancements

Want to improve the quality of the enhancements in your Release Notes? Here are seven ways. Enhancement Identifier Provide the reference number for the enhancement, such as Salesforce 12345. Business value Describe the benefit to the user if they use this enhancement. Usually, there is a specific business driver or customer request behind each enhancement’s […]

Release Notes: Sample Text for Writing Enhancements

An enhancement is a new feature, or an improvement to a current feature, included in the current release. To help the reader understand the enhancement, describe: Where the enhancement is located in the user interface. What parameters need to be configured. What is the default setting. Why you should use this enhancement, for example, a […]

Release Notes – How to Write ‘Known Issues’

This week we look at how to document known issues in release notes. The Release Notes web page on the NuGet site offers good examples of how to document known issues in release notes. We’re going to look at three common issues: Installation issues Known issues Workarounds Let’s see what we can learn from it. […]