Feature maps support exploration and learning. They create opportunities to identify risks and dependencies. And they can complement other resources.
Today's post is about all that and more. (2/2)
https://t.co/QG0ebMBSyi
Over the past few years feature maps have become one of my favourite tools in my testing toolkit. They add value throughout the whole development process. (1/2)
Today's post is about four questions that can help you write better bug reports, and some thoughts about what steps you can do next.
https://t.co/NdT4c0pzyi
(2/2)
Exploring, experimenting and learning about the software under test leads to findings and these findings should be documented in some way: bug reports.
(1/2)
This technique helps me to structure my thoughts and to talk about possible improvements.
If this sounds useful to you, read her article, which contains an example and her experience of using it: https://t.co/Nl0CWtU17M
I discovered SPIN many years ago through an article written by @katrinaclokie and I find myself using it again and again.
Situation: What I see.
Problem: Why I care.
Implication: Why you should care.
Need: What I think we should do.
(1/2)
I believe that non-software tools are a crucial part of what makes a professional software tester. They allow software testers to kick-start their thinking, reproduce their success, reason for what they do and to teach their profession. (1/2)
You can learn about a feature through exploration and experimentation. By observing the feature in action within the software under test. But there is also information outside the software that cannot be discovered in this way. (1/2)
In today's post, I will show you how to document QA-related actions taken within your organisation or project and the benefits of doing so.
https://t.co/qiZQnNLyUm
(2/2)
Understanding all the quality assurance measures brings the following benefits for testers:
• Focus on uncovered risks
• Prioritise their work
• Have a better understanding of the business
• Question features
• Prepare earlier
(1/2)
Here are seven questions testers can ask to identify dependencies worth resolving:
• What tasks do I do that depend on other people?
• Are these dependencies blocking my progress?
• Are these blocking dependencies recurring?
(1/3)
• Have I asked these people to teach me how to do it by myself?
• Do you want to learn it?
• How much time and effort will it take, and is it worth it?
• Can anyone else benefit?
(2/3)
I have been a software tester for over 13 years. In today's post I write about three aspects that fuel my passion and keep me doing what I like.
https://t.co/MDfaEAPx1F
If someone has removed a feature from a release, check that it has actually been removed.
Also check that the removal has not broken any functionality in the area where it was implemented.
Something may have gone wrong.
This week I listened to Randy Pausch's famous talk, Last Lecture: Really Achieving Your Childhood Dreams.
I can't remember ever thinking after a talk: I want to hear it again. Not now. But maybe in a few weeks or months.
Such a wonderful talk.
https://t.co/Uk2H7Lq0p5