BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Defects Content on InfoQ

News

RSS Feed
  • How to Assess Software Quality

    The quality practices assessment model (QPAM) can be used to classify a team’s exhibited behavior into four dimensions: Beginning, Unifying, Practicing, and Innovating. It explores social and technical quality aspects like feedback loops, culture, code quality and technical debt, and deployment pipeline.

  • How We Can Use Data to Improve System Quality

    To understand how systems are being used, we can collect metrics and identify trends over time. The data and insights gained can be used to improve system quality by improving software design or testing patterns.

  • 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.

  • Investigating Near Misses to Prevent Disasters: QCon London Q&A

    Investigating near misses by gathering data from the field and exploring anything that looks wrong or is a bit odd can help to prevent disasters, said Ed Holland, software development manager at Metaswitch Networks. At QCon London 2019 he gave a talk about avoiding being in the news by investigating near misses.

  • Increase Learning with 10% Autonomy Time

    Giving teams autonomy to spend 10% of their time for learning reduces delivery time, increases quality, and increases motivation. The 10% rule gives teams full autonomy to work on things they consider important. It results in freeing up people's creativity and letting teams grow their potential.

  • How to Effectively Debug Software

    InfoQ interviewed Diomidis Spinellis, author of the books Code Reading and Code Quality, about finding and fixing errors in software, principles for debugging software and how to improve the effectiveness of debugging, how to write code that requires less debugging, and what managers can do to support error prevention and handling.

  • To the Moon: Parallels Between Space Missions and Developing Software

    Russ Olsen did the opening keynote titled "To the Moon" at the GOTO Berlin 2015 conference. InfoQ interviewed him about drawbacks of doing all the things at the same time to meet the deadline, learning from things that went wrong and from things that went right, how little things can kill you in software development, and how to focus and deal with details when doing complex work.

  • Coverity 2012: How to Get a Low Defect Density

    This article contains the testimonies of several project leaders detailing the process used to achieve a low Coverity Scan defect density.

  • Tasktop Sync Supports Application Lifecycle Management Synchronization

    The new release of Application Lifecycle Management (ALM) tool Tasktop supports an ALM synchronization solution that addresses the visibility and traceability needs of the software development teams. Tasktop team announced the release of Tasktop Sync 1.0 version last month. They also recently released Tasktop Dev 2.1 version which builds on Eclipse Indigo release of Mylyn 3.6.

  • Application Lifecycle Management in Team Foundation Server 11

    Team Foundation Server 11 has added many features in the area of Application Lifecycle Management. Some of the highlights include support for code reviews, iterations/sprints, resource allocation, third part testing frameworks, and a much more capable dependency graph.

  • The Holy Grail of Zero Defect Systems

    While, zero defects sounds very good to hear, is it really possible or is it an unachievable goal? Many organizations adopt a 'zero defects methodology'. Does it really mean anything?

  • Interview: Luke Francl Explains Why Testing Is Overrated

    In this interview filmed during RubyFringe 2008, Luke Francl explains his position towards testing. While supporting unit testing, he thinks testing is not going to reveal all application defects. Development teams should practice code reviews and usability tests which are likely to discover bugs not visible though other methods.

  • Presentation: Testing is Overrated

    In this talk from RubyFringe, Luke Francl asks: is developer-driven testing really the best way to find software defects? Or is the emphasis on testing and test coverage barking up the wrong tree?

BT