Richard Estra

Richard Estra is a Senior Software Test/QA Engineer. He holds a Bachelor's degree in Computer Science and has been working in the software industry for the past 35 years. He has participated in the complete range of testing responsibilities including requirements analysis, test strategizing, test planning and documentation, testing execution, defect recording, root cause analysis, defect avoidance, metrics gathering/reporting and customer support. He has extensive knowledge of increasing the software quality and end user experience by utilizing software test process improvement and optimization techniques, and is looking for his next challenge in testing/QA. Email Richard at [email protected] or on LinkedIn at https://www.linkedin.com/in/richardestra/

Connect with Me

https://www.linkedin.com/in/richardestra/

All Stories by Richard Estra

Defect Reporting: The Next Steps

When a software defect is identified, best practices usually only pertain to the initial writing of the defect, not the tasks required to close it. Many factors can influence the tester's work. The solution is to add a “Next Steps” section that identifies the work remaining and the person responsible for completing it.

Stop Fanning the Flames of Constant Firefighting

Continually having to address unexpected problems interrupts your original sprint activities, causing stress on the team members and fanning the flames for future firefights. But with due diligence, you can lessen the need to constantly put out fires. Here are some steps that can break the cycle of work and rework.

Use Self-Evaluation to Stay on the Right Career Track

Employer evaluations measure your performance against expected objectives, evaluate you against other employees, and aim to keep you relevant in your company. But it’s also a good idea to perform a self-examination in relationship to your place of employment, to ensure you stay attractive to potential future employers.

Are Your Fundamentals Malfunctioning?

Every objective has certain elements that are fundamental to its success. These include the supporting tasks or systems that we take for granted but without which our “real” work could not get done. In order for any organization or team to meet its primary objectives, these fundamentals need to be functioning properly.

Stop Email Overload and Communicate Better

Many of us fire off correspondence to groups and distribution lists that include more recipients than necessary, and we overcommunicate without stopping to think about exactly what needs to be conveyed. Here are some ways organizations and teams can cope with the influx of information and communicate intentionally.

Don’t Become a Slave to Process

More mature organizations are usually very process-disciplined, especially when teams are distributed. However, it’s dangerous to become overly reliant on process. People can become too complacent, accepting a process just to avoid having to make decisions. Here are some ways to keep your processes fresh and valuable.

Don’t Let “Try It Now” Impede Your Test Initiative

Sometimes environmentally based issues arise that impede your ability to access or test the software. Rather than addressing the problem methodically, as with defects, testers often attempt to solve it on their own. Here's why entering the problem into the defect-tracking database is a more efficient way to solve it.