Tips

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

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

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

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

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

  • 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 secrets to getting started in your software testing

    The way to advance in your career includes learning, experience and networking. Software test expert Kevin Beaver gives advice on best ways to further your career. By doing what you love and stayin...

  • Building solid security requirements

    Security expert Kevin Beaver describes the steps required to build solid security requirements. Beaver walks through key questions that must be asked to ensure both business and technical needs are...

  • Change management: Change in requirements

    When requirements change late in software development project things have a tendency to go wrong. Learn methods one expert uses to avoid complication when adapting a project t to meet revised requi...

  • Success factors for distributed teams

    Distributed agile expert Lisa Crispin describes the structure, management-style and level of acceptance required in order for distributed agile teams to find success.

  • Strategies for minimizing regression defects

    Regression defects, those unexpected defects that result from a fix of another defect, are often the most challenging to find and fix. Expert John Overbaugh describes why these defects are so chal...

  • Choosing a defect tracking system for your organization

    Does your software organization need a purpose-built defect tracking system but you don't know where to turn? Expert John Overbaugh explains what criteria should determine the proper defect trackin...

  • Seven quick tips for better performance requirements

    An expert tester explains seven useful tips for determining appropriate performance requirements that can be tested throughout the development cycle. Knowing the right conversations to have with st...