The hottest Quality Engineering Substack posts right now

And their main takeaways
Category
Top Technology Topics

Quality Engineering Basics: Incident Reports

QUALITY BOSS • 39 implied HN points • 05 Apr 24
🕹 Technology Quality Engineering Process Improvement Software Development Engineering Management
  1. Incident reports help us learn from mistakes without blaming anyone. By understanding what went wrong, we can improve processes and avoid future issues.
  2. Writing incident reports takes time but leads to fewer problems later. They keep everyone informed and help prioritize important improvements.
  3. To make incident reports effective, clear criteria and responsibility are needed. It's important to track action items so that lessons learned actually lead to real changes.

Quality Engineering Basics: Bug Retrospectives

QUALITY BOSS • 39 implied HN points • 05 Feb 24
🕹 Technology Software Testing Quality Engineering Team Collaboration Process Improvement
  1. A Bug Retrospective is a team meeting to review and learn from bugs that occurred during a project. The focus is not on blaming anyone but on understanding why the bugs happened and how to prevent them in the future.
  2. These retrospectives help improve the quality of the product by fostering a culture where everyone takes responsibility for quality. Each bug can be seen as a lesson that can strengthen the team’s processes and test strategies.
  3. To start a Bug Retrospective, gather the team, discuss selected bugs, analyze their root causes, and create an action plan for prevention. Sharing insights and encouraging collaboration can lead to better practices and overall product quality.

Welcome to QUALITY BOSS ✨

QUALITY BOSS • 19 implied HN points • 15 Oct 23
🕹 Technology Quality Engineering Leadership Women in Tech Personal Development
  1. The blog focuses on quality engineering and leadership in the tech industry. It's a space to share professional experiences and insights.
  2. It highlights the unique challenges and successes that women face in technology. This perspective aims to encourage others in the field.
  3. The author started writing as a hobby and wanted a platform to express her professional thoughts and advice. It's meant to be a community for exploration and learning.

Quality Engineering Basics: Types of Testing

QUALITY BOSS • 0 implied HN points • 19 Feb 24
🕹 Technology Software Testing Quality Engineering Automation Development
  1. There are two main types of testing: functional and non-functional. Functional testing checks if the software meets its intended requirements, while non-functional testing looks at things like performance and security.
  2. Testing can also be categorized by the level, such as unit, integration, system, and acceptance testing. Each level focuses on different parts of the software and helps ensure everything works together smoothly.
  3. Finally, there are different ways to test, including manual and automated testing. Manual testing involves humans checking software directly, while automated testing uses tools to run tests automatically. Both are important for delivering a quality product.

Quality Assistance, Not Assurance

QUALITY BOSS • 0 implied HN points • 18 Oct 23
🕹 Technology Software Development Quality Engineering Team Collaboration Process Improvement
  1. Quality Assistance means Quality Engineers work closely with developers. They help ensure high-quality software by sharing best practices and tools, rather than just checking for mistakes later.
  2. This approach moves away from the old method where a separate QA team is responsible for quality. Instead, everyone in the organization shares the responsibility for maintaining quality throughout the entire development process.
  3. Finding and fixing bugs early saves time and money. Waiting until the end of a project to test can cost a lot more if errors are found later.
Get a weekly roundup of the best Substack posts, by hacker news affinity: