Software test planning book? Encourage clarity in bug reporting. “Reporting bugs and requesting more information can create unnecessary overhead. A good bug report can save time by avoiding miscommunication or the need for additional communication. Similarly, a bad bug report can lead to a quick dismissal by a developer. Both of these can create problems. “Anyone reporting bugs should always strive to create informative bug reports, but it’s just as important that developers go out of their way to communicate effectively as well. For instance, if a developer needs more information, it’s best if they take the time to write a detailed request. Teach people to write good reports, but hold your developers to high standards as well. If everyone is going above and beyond to communicate effectively, everyone’s productivity benefits.
There are a lot of great staff out there and typically with testers I find attitude is everything! Sure, you can learn great technical skills but if your team members don’t have the right attitude or intuition for testing you will probably be out of luck. If you are lucky enough to have great Test Leads or Testers you will probably find they have the right attitude and social skills to deal diplomatically with people of all levels in all sorts of roles. JDI is always a good approach! Speaking of tester’s intuition, check out one of the earlier blogs in the series on using your intuition, Testing and Bad Smells: When to Investigate Potential Bugs. Thanks Penny for a great post!
Taking you deep into this ever changing industry is software test management consultancy Cania Consulting, comprised of industry leaders who specialize in software testing audit, strategy, and management. They use the techniques and insights provided in this book on a daily basis with their clients and are sharing their insider tips as a key resource for readers in the test management industry. After passing the ISTQB Foundation Certification, this eBook was great source to better understand what to expect from the Test Managers working on my Software Projects. Read a few more info on Test Analysis.
The ‘what if’ should become the leading question of the software research. On the other hand, if you had a bug in the accounting software that caused all of the data to become corrupted every 1,000th time the data was saved, that would have a huge impact but at a very low frequency. The reason I define software testing in this way is that — as any tester will tell you — you can never find all the bugs or defects in a piece of software and you can never test every possible input into the software (for any non-trivial application). Think outside of the box. More and more often we have to deal with assuring quality of various IoT developments. They require testers to become real users for some time and try the most unthinkable scenarios. What we recommend is to start thinking out of the box.
Isolation software testing tip of the day : With people working remotely, the overall environment will be less efficient, and/or collaborative. So it necessarily means that certain tasks may be less efficient and other task may be more efficient. When working from home, developers will have more time to code without being interrupted in meetings, but will have less time to clarify requirements, ask questions or hear what other team members are doing on the code that might help them (see tip 8 about requirements clarity). So now is a good time to shift to tasks that previously you didn’t have time for. Instead of doing some complex scenario tests that require you to talk to three other people, maybe it’s time to get some robust non-flaky regression tests in place. Use automation tools to improve both your automated testing and/or tasks in your DevOps pipeline. That tricky deployment process that has 5 manual steps that you have had on your personal to-do list for months? Maybe now is the time to write the code to automate it. Explore even more details on https://cania-consulting.com/.