InfoQ Homepage Quality Content on InfoQ
-
Building Quality in for Blockchain Systems
Blockchain technology can be used to build solutions that can naturally deliver better software quality. Using blockchain we can shift to smaller systems that store everything in a contract. We have to understand our data needs and decide what is stored in the chain and what off-chain, and think about how requirements, defects and testing history can be built into the contract models.
-
Adapting a Zero Bug Policy to Solve Bugs
Applying a zero bug policy made it easier to prioritize bugs and increased team visibility and responsiveness towards bugs. As it’s a radical change, you will need to adapt it to your context regarding decision-making and time to fix a bug.
-
How Mob Programming Collective Habits Can be the Soil for Growing Technical Quality
Mob programming can support teams in changing old habits into new effective habits for creating products in an agile way. Collectively-developed habits are hard to forget when you have other people around. Mob programming forces individuals to put new habits into practice regularly, making them easier to adopt. Teams are intolerant of repetition, looking for better ways of doing their work.
-
Experiences from Having Developers Write E2E Tests
Developers writing e2e tests can make code testable, provide fast feedback, and prevent bugs. Wix worked with their product managers, developers, and QA engineers to transition from QA-only testing, to having developers write e2e tests to shift QA left and deliver faster.
-
Adding Security to Testing to Enable Continuous Security Testing
Teams can be trained by security experts to become able to identify areas to add security testing in the test process and add security checks as part of functional test automation. This can lead to continuous security testing where security defects can be spotted at an early stage with higher security testing coverage in every release.
-
Shifting Quality Left with the Test Pyramid
Shifting quality left means building in quality much earlier in the software development cycle, rather than testing for quality after completion of development. Using the test pyramid model, a project was able to move testing towards earlier stages, thereby finding defects that caused integration issues earlier in development.
-
Agile Approaches for Building in Quality
Built-in quality is a core pillar in agile. However, if we want to build in quality at scale, we need to look at the whole development life cycle. Quality awareness needs to be increased at multiple layers of the organization; agile coaches can help by boosting quality thinking by embracing an agile way of working.
-
Applying a Zero-Bug Policy at Redgate
A zero-bug policy is a simple yet effective bug management system that can help you avoid being buried deep in months or sometimes even years-old bugs. Any bugs you agree are serious enough for you to fix, you fix right away, and any other bug will not be fixed and closed. Tom Walsh spoke about how Redgate Software applied the zero-bug policy at Lean Agile Exchange 2020.
-
Experiences from Using a Disciplined Approach to Change
When a company embraces the agile path, the first question is: “Where do I want to go?” and not “What is the right framework to do agile?” A disciplined approach to change can help you to choose from possible practices such as a “design pattern book” for agile transformation, and to identify when a practice is promising and when the current context is not the most favorable for it.
-
Ensuring Software Quality at eBay Denmark
Quality is not only about not releasing bugs to production, it is much more than that. Quality is a product that is user-friendly, easy to access and use, has high performance/short load time, and is about code that is stable and easy to maintain. Jette Pedersen gave a talk about how to ensure good quality products at Swiss Testing Day 2020.
-
Organizational Topologies and Their Impact on Quality
August Lilleaas recently wrote about the correlation between organization complexity and software quality citing a paper by Microsoft. Rapid Software Testing Methodology creator James Bach has also recently written about how we should interpret quality metrics. The authors of Team Topologies shared insights into how adapting organizational structure can improve the health of software.
-
AdoptOpenJDK Introduces Quality Assurance Program
AdoptOpenJDK has created a comprehensive set of over 30,000 tests designed to ensure compatibility, performance, and reliability of their JRE distributions. The test suites are small enough to be run regularly by those working on the project, and also benefit those who simply use the project.
-
Quality and Culture: Learnings from Other Disciplines and Industries
We can gain by learning about other industries such as aviation and healthcare, and studying other disciplines, argued Conor Fitzgerald, software tester at Poppulo, at RebelCon.io 2019. Aviation has a history of continually learning from its mistakes, whereas in healthcare, culture and bias seem to challenge learning and continuous improvement.
-
Experience Building a QA Team in a Growing Organization
Shifting the test team to the left brought the whole team closer together, enabled faster learning, and improved collaboration, claimed Neven Matas, QA team lead at Infinum. He spoke at TestCon Moscow 2019 where he shared the lessons learned from building a QA team in a growing organization.
-
Optimize Automated Testing Using Defect Data
By integrating the test framework and the bug tracking system, it becomes possible to deactivate test cases for known bugs and reactivate them when the bug is solved. Aneta Petkova, QA chapter lead at SumUp, presented The Framework That Knows Its Bugs at TestCon Moscow 2019.