Tips

  • Pair programming: Two people, one computer

    Pair programming, the technique where two programmers use one computer to develop software code, is a practice which has been shown to improve software quality when done well. In this tip, SSQ site...

  • Waterfall or Agile? - Differences between predictive an

    Is your organization trying to decide whether to use a predictive methodology such as waterfall or an adaptive methodology such as scrum? Senior consultant David Johnson describes the history of so...

  • Applying lean concepts to software testing

    If we're going to use a factory analogy for software development, shouldn't we at least study the techniques modern factories use? In this tip, software quality expert Matt Heusser describes concep...

  • How to alleviate software test design bottlenecks in Ag

    Senior test architect David Johnson describes two different design challenges: testing the current release and regression testing in agile environments. Johnson discusses the use of exploratory tes...

  • Software developers and testers: Can't we all just get

    The relationship between developers and testers has often been strained, but it doesn't have to be. In this tip, site editor Yvette Francino talks about how this contention can develop and discusse...

  • Scaling Agile software development: Challenges and solu

    Software consultant Nari Kannan describes how agile practices and work can be scaled appropriately for success in large organizations. Using lean thinking, reduction of waste, and appropriately org...

  • The software experience report: Record what you learn

    Each software project provides an opportunity for learning. By documenting our experience in an experience report, we are able to reflect and share what we learned. In this tip from frequent SSQ co...

  • Breaking the bug reporting rules

    Software test expert Chris McMahon talks about three rules for bug reporting, but then explains that there are times when breaking these rules are necessary for even better bug reporting. Intermitt...

  • The perfect storm: Multiple mishaps lead to disaster

    A series of mistakes, due to a series of software errors and lapses in judgment, result in a situation that could mean the difference between life and death for customers. Find out lessons that tes...

  • Happy customers through high-performing service level a

    Software pro Kay Diller describes how to set up an effective system to ensure high-performing SLAs. By using automated monitoring systems, operating level agreements (OLAs) and staying informed as ...

  • Hacking For Dummies: Hacking Methodologies, Chapter 4

    Kevin Beaver teaches the steps for successful ethical hacking, gleaning information about your organization from the Internet, scanning your network and how to look for vulnerabilities. Tools and t...

  • What is a test case? What is a requirement?

    After exploring the definition of a test case by surveying test experts, authors and students, consultant Robin Goldsmith learns that interpretations remain ambiguous and varied. Similarly, the lev...

  • Automating software development: The Big Red Button

    Seasoned tester Chris McMahon talks about using automation in all phases and aspects of the software development cycle. Continuous integration, test environments, test data, regression testing, per...

  • Self-organizing teams exposed

    Software expert Chris McMahon describes how self-organizing teams can work well, even in a distributed environment, by tuning team roles and team workflow. Silos are being broken down so that the t...

  • The distinction between functional versus performance r

    Senior test architect David Johnson describes the distinction between functional and performance requirements and the benefits from keeping these two test efforts separate. Examining differences in...

  • Daily Scrum meetings: Must we really stand up?

    Often called the daily stand-up, must everyone at the Daily Scrum meeting literally stand? Which rules are inflexible? How are the rules enforced? Find out the objectives of the Daily Scrum and how...

  • Test design focused on expediting functional test autom

    Senior test architect David Johnson describes test design paradigms such as keyword-based test design, which can be leveraged for functional test automation. Johnson addresses both commercial and o...

  • Exploratory vs. planned testing: Which yields better re

    Software test expert Chris McMahon tests in an exploratory manner side-by-side a colleague who tests with a methodical, planned manner, comparing the rate of defects found over time. The results ma...

  • Inadequate requirements and what to do about them

    Software requirements are often subjective and poorly written resulting in inadequate requirements documentation. In this tip, QA Director John Scarpino describes some of the reasons behind poor re...

  • The link between automated UI tests and exploratory tes

    Smart agile teams typically mix automated UI tests with manual exploratory testing to achieve better coverage this is a good practice but still has potential problems. Learn how to provide an impro...