Richard Estra

Member for

7 years 10 months

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/

Job Function

Testing

Job Title

Software Tester/QA

Interests

Process Improvement

Quality Assurance

Releases

Requirements

Testing

Country

United States

Richard Estra

All Articles by Richard Estra

All Stories by Richard Estra

	Are You Testing The Quality Into Your Software? The test team shouldn’t have the onus to improve the software quality, rather the quality should already be built into the software. A few subtle indicators can reveal if the quality isn’t being built into the software.
	Test Teams Evaluation to Improve Effectiveness Evaluating a test team member’s abilities is crucial in recognizing deficiencies within the team, and it provides an opportunity to outline a strategy to remedy the weaknesses. Selecting the proper method for evaluating the test team’s abilities is vital.
	Immunizing Your Software against a Defect Pandemic When your released software is infected with problems, there is the possibility of a pandemic defect, when a wide geographic area and an exceptionally high proportion of the end-user population is affected. Just like with the coronavirus, following proper guidelines and taking mitigation steps can reduce the spread.
	Testing in the DarkRequirements only go so far in identifying areas to test. Sometimes testers are given no information at all, leaving it up to them to determine what to test. Don’t accept the need to indiscriminately test with no clear understanding. Your testing should be targeted, and these techniques will help focus your test effort.
	Build Better Teams by Finding Hidden TalentsWe’re not all created equal, and it’s counterproductive to act like that’s the case on a team. Every individual has their own unique set of strengths, and knowing what everyone’s strengths are contributes to the team’s success. When you're putting a team together, you first have to discover each person’s strong suits.
	8 Questions to Ask before Fixing a DefectSome defects require a fix, without a doubt. But not all defects are created equal, so careful thought should be applied before a defect is fixed. The goal isn’t to fix every reported defect; it’s to return value to the customer and profit to the company. These eight questions can help in the decision-making process.
	Stop Releasing Untested Defect Fixes into ProductionReleasing untested defect fixes into production is a real possibility. Being aware of how this can occur may help reduce the possibility of it happening. Let’s explore the common reasons defect fixes go untested—insufficient testing or resources, and undocumented fixes—as well as the steps we can take to prevent them.
	Defect Reporting: The Next StepsWhen 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 FirefightingContinually 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 TrackEmployer 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 BetterMany 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 ProcessMore 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 InitiativeSometimes 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.
	Get Your Defect-Tracking Database Back on TrackWhen defects are ignored or mismanaged, it can compromise the integrity of the defect-tracking database. When this happens, defects could go unfixed, or code fixes may not be verified by the production release. Before you can resolve a compromised defect-tracking database, you need to know how to recognize one.
	It’s 10 p.m. Do You Know Where Your Defect Fix Is?Have you ever had to ask whether your defect fix was deployed to a particular environment? You shouldn’t need to, because the answer should always be readily available. Having to request information on the status of your defect fix indicates inefficiencies and a lack of maturity within your organization’s process.
	Are You Unintentionally Unapproachable?Could you be giving off an air of unapproachability without meaning to? Is it possible that you exhibit some unwelcome behaviors that are so subtle you’re not even aware of them? Think about whether you have any of the following habits that could give your coworkers the impression that you are unapproachable.
	Achieve Success by Joining a Failing ProjectWe all want to be associated with success, so when there’s a failing project, most of us want nothing to do with it. However, if you’re looking for a way to give your career a boost, you may want to rethink that. If you’re not afraid of a challenge, here are some ways embracing a failing project can help your career.
	Beware the Bad Apple: 3 Types to Watch for on a TeamWe all know some obvious personality types that can be less than ideal to work with. However, there are other personality traits you may want to beware of as well. Although these characteristics may seem perfectly harmless on the surface, in excess they can be just as dangerous to a project as the more glaring types.
	The 6 P’s of Getting Started on a New ProjectIdeally, when an employee is transferred to an existing project, there would be at least one team member designated to train the new person. However, this isn’t always the case, and you may be left to fend for yourself. If you suddenly find yourself on a new project, take control and get started with the six P’s.
	Make the Most of Your Downtime with the 3 P’sDowntime doesn’t need to mean unproductive time. It doesn’t have to be spent passively waiting for your next assignment. Instead, you can take advantage of your downtime and use it productively. If you want to maximize your downtime but don’t know where to start, focus on the three P’s: product, process, and people.
	4 Ways to Increase Software Quality and Decrease Test TimeSoftware testers are continually under pressure to test faster without sacrificing quality. By taking the perspective that quality is the responsibility of the entire team, not just the testers, shorter test cycles with higher quality software are possible. Here are four ways the whole team can improve releases.