Problem solve
Get help with specific problems with your technologies, process and projects.
Problem solve
Get help with specific problems with your technologies, process and projects.
How to measure test progress: Every picture tells a story
Seeing the big picture when it comes managing the progress of your software tests may require putting together all the little picture pieces. Continue Reading
How does the role of project manager change in the cloud?
Agile and ALM expert Yvette Francino discusses how the role of project manager may change when applications are developed and tested in the cloud. Continue Reading
Agile project management using the Cynefin framework
Learn how the Cynefin framework facilitates problem solving, Agile project management and teamwork. Continue Reading
-
When to perform post-production testing
In some cases, testing post-production is needed, according to expert Pete Walen. He discusses the potential situations where post-production testing is helpful and what expectations we can have for performance testing. Continue Reading
Security testing for unvalidated redirects and forwards
Security expert John Overbaugh gives security testers the information they need in order to ensure the Web application code that they’re responsible for is protected. Continue Reading
Integration testing: What are the challenges?
Expert Pete Walen describes common problems with integration testing and offers insights into implementing it correctly, so that both internal and external users can benefit.Continue Reading
Exploring integration testing in the Agile development lifecycle
Agile expert Lisa Crispin explores the various meanings and offers tips to testers on how to work integration testing into the Agile development lifecycle.Continue Reading
Streamlining user acceptance testing (UAT) with Agile
Organizations that implement successful user acceptance testing can greatly reduce errors and business risks.Continue Reading
Agile testing quadrants: Guiding managers and teams in test strategies
Agile expert Lisa Crispin explains the four Agile testing quadrants and how they can guide managers and development teams in creating a test strategy.Continue Reading
Software development bugs: How to identify and prevent them
With strong Agile practices such as unit testing, code reviews and proper attention to requirements, bugs can be prevented or found early in the application lifecycle.Continue Reading
-
Defect tracking: Lean principles for getting the right data at the right time
In this tip, author Paul E. McMahon describes how Lean principles can be used to help determine when defect tracking is appropriate for your organization and what type of data is important to collect.Continue Reading
Exploratory testing and regression testing in continuous integration
Expert Lisa Crispin explains how and when to implement exploratory testing, automated regression testing and manual regression tests in an Agile development environment.Continue Reading
The whole-team approach to Agile development: Examples and benefits
Lisa Crispin continues in this second tip in the series by giving real-life examples and benefits gained from practicing the whole-team approach on Agile development teams.Continue Reading
Agile software development: Tips for writing testable user stories
Testing pressures are always high on Agile projects. In this article we explore some of the ways adding clarity to stories can help make testing easier for all parties involved.Continue Reading
Tools and techniques for tracking changes to software requirements
In this tip, requirements expert Sue Burk explains different techniques and tools that can be used to track changes to the requirement itself as well as changes to the attributes of the requirement.Continue Reading
Regression vs. risk-based testing: Managing complexity
In this tip, consultant Vasudeva Naidu describes in detail the steps necessary to implement risk-based testing in your organization to ensure your regression test strategy is solid and successful.Continue Reading
Managing change requests to your application
In this tip, we look at end user requests, and the process to prioritize the requests for IT, so they know where to focus their work efforts.Continue Reading
Application security: Protecting application availability, data confidentiality and integrity
Network security and application security are both important in keeping your applications safe from hackers. In this tip, security engineer John Overbaugh focuses on application security, which is needed to protect the confidentiality, availability ...Continue Reading
Understanding the dependencies between requirements in a Scrum environment
Prioritizing user stories for each iteration in a Scrum environment can be challenging if the project owner does not understand the dependencies between requirements. In this expert response, Lisa Crispin shares best practices for prioritizing user ...Continue Reading
How user stories help to define software requirements
User stories play an important role when defining requirements and they also contribute to living documentation during the software development process. In this expert response, Lisa Crispin offers key practices for ensuring that requirements align ...Continue Reading
Mapping software requirements to test cases
Even though you must have at least one test case per requirement, it's possible not to have a one-to-one mapping between each requirement and test case. In this response, expert Sue Burk explains how it is important to trace the relationship between...Continue Reading
Tracking changes to requirements in Agile development
All development teams need to track requirements changes, but depending on the software development lifecycle and overall ALM process, the best approach to change tracking may not be the same across the board. In this response, expert Mike Jones ...Continue Reading
Embedded software testing: Five messaging event styles
In testing embedded systems, timing can often cause trouble. In this tip, consultant Scott Allman describes the five different types of event styles that can occur when two events are executed. A good test plan will cover each of those event styles ...Continue Reading
How to gain acceptance of organizational change
Any organizational change can meet with internal resistance. In this response, SSQ Site Editor Yvette Francino offers advice on how to win buy-in from those affected through honest communication and continuous improvement.Continue Reading
Manual testing vs. automated testing: A decision point
Automation in a test environment can be expensive and doesn’t always yield a high return. In fact, a high percentage of automation efforts fail. In this tip, Vasudeva Naidu gives advice on key factors that will lead to success in your automation ...Continue Reading
Waterfall vs. Agile development: A case study
Two projects very similar in scope were executed by the same project team for the same users. The first project used a waterfall methodology and resulted in missed deadlines and failure to deliver user requirements. The second used an Agile ...Continue Reading
Agile ALM tools: How they differ from traditional lifecycle management tools
Software consultant Nari Kannan describes the differences between agile application lifecycle management (ALM) tools and traditional lifecycle management software. Agile ALM tools are more tightly integrated, easier to use, supportive to distributed...Continue Reading
Specialized testing for your enterprise application
In this tip, Judith Myerson describes examples of five types of testing for your enterprise applications: cloud testing, user acceptance testing, modular testing, agile testing and incremental testing. Myerson gives a brief overview of each type of ...Continue Reading
Application development for mobile phones: Testing across different devices
New mobile phone models enter the market all the time, and it seems daunting to perform application testing on the various devices available. Expert Karen Johnson carefully examines the factors developers must consider and offers strategies on how ...Continue Reading
Functional requirements and nonfunctional requirements in software engineering explained
Clearly defining both functional and nonfunctional requirements in software engineering projects is important from both a business perspective and a performance perspective. In this expert response, Sue Burk offers definitions and examples for both ...Continue Reading
Eight steps for a successful software release
Have you done everything to prepare for a successful software release? Software project manager Kay Diller describes eight things you can do to ensure your deployment will go smoothly. From creating your team to being prepared with a back-out plan, ...Continue Reading
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 concepts used first for lean manufacturing, which are now ...Continue Reading
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 level of detail thought to be needed to define ...Continue Reading
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 challenging and offers up techniques, such as automation...Continue Reading
Differences in Agile and traditional software project management
In this expert response, some of the differences between project management in traditional environments and agile environments are explained. One of the biggest differences is the flexibility of scope changes that is welcomed in agile environments.Continue Reading
The importance of critical thinking in software test
Even though there are numerous definitions for the term "software testing," there is common ground. Testers need to use critical thinking skills when diving into the testing of a software application. In this tip, expert Chris McMahon explains ways ...Continue Reading
What does "change management" mean in software development and QA?
Change management, sometimes called configuration management, has a few different meanings in the software development community, from team changes to code changes, explains expert Yvette Francino.Continue Reading
Six tours for exploratory testing the business district of your application
Exploratory testing is sometimes thought to be "directionless testing", but James Whitaker's new book suggests that exploratory testing, is more structured than it is credited for. Exploratory testing is filled with numerous tours or testing ...Continue Reading
A software expert's heuristic for regression testing
Often, regression testing is what stands between a product in a test lab versus a product in the hands of our users – so we don't want to take longer than we need – but we don't want to haphazardly release a product before its ready.Continue Reading
Scrum Master or Scrum project management, is there a difference?
A Scrum Master is commonly mistaken for a project manager who works in a Scrum environment. Learn what distinguishes a Scrum Master in this expert response.Continue Reading
Using Fist of Five, Planning Poker to reach Agile team consensus
In these tips, consensus-building tools such as Fist of Five and Planning Poker are introduced. Even when these tools are used, the team must decide how they are going to handle a stale-mate condition and move forward on decisions.Continue Reading
Why use POST vs. GET to keep applications secure
Although POST and GET HTTP requests essentially perform the same command on a Web server, a security expert says there are inherent dangers in using one over the other. Learn why one type of processing request provides more security for your Web ...Continue Reading
What are the pros and cons of centralizing a QA or software test team?
Is it better to centralize a test team or have testers paired organizationally with developers? There can be advantages to either approach. This expert response examines some considerations and an alternative that will allow your quality team to ...Continue Reading
Who determines the appropriate severity or priority for a defect?
There are often differences of opinion on the definition of severity or priority of a defect. The bottom line is determining when and if the defect will be fixed. Factors that need to be considered are customer urgency and time required to fix and ...Continue Reading
Nine ways to evaluate automated software testing tools
Evaluate automated software testing tools more thoroughly with these tips for analyzing cost, support, total cost of ownership, usability and more. This tip suggests questions to ask about each attribute of a tool and a vendor's support for it.Continue Reading
Problems caused by skipping analysis stage of SDLC
A requirements expert explains the possible pitfalls of skipping the analysis phase in the software life cycle development (SDLC).Continue Reading
Calculating mean time to failure in performance testing
Calculating MTTF (mean time to failure) can be a difficult for testers in order to develop a performance test pass as there are multiple steps. This expert tip will guide you through process,Continue Reading
Defining report requirements with use cases
This tip offers a new and interesting way to go about defining and reporting requirements for use cases. There are a number of details that need to be attended to in defining requirements such as taking a look at users and then constructing use ...Continue Reading
How requirements use cases facilitate the SDLC
Learn software use case processes and techniques that result in better application requirements in this tip. Takeaways include use case diagrams and user acceptance test case examples.Continue Reading
How to deliver software with an SDLC iterative model
The phases of iterative SDLCs come together to build better software applications faster, as long as the team avoids some common development and planning mistakes.Continue Reading
Expert shows seven ways to improve your project management abilities
Project management offices can benefit when the team has a diverse portfolio of skills. Learn how to become a better project manager by reading these seven suggestions, which range from developing talents and group leaders to better assessing ...Continue Reading
Differentiating between Functional and Nonfunctional Requirements
Many of the difficulties encountered in defining requirements relate to the functional-nonfunctional distinction. As so often happens, some of those difficulties are things of which people are aware, largely realizing after-the-fact that ...Continue Reading
Defining requirements during software project feasibility analysis
There are at least two key points in a software project when requirements should be defined. One point people often miss is during feasibility analysis, and failure to define requirements at this stage can doom a project.Continue Reading
What is test granularity?
Test granularity is the level of detail at which your software tests and test cases address your project.Continue Reading
Web application security testing checklist
Testing your Web application security is something that needs be taken seriously. The best way to be successful is to prepare in advance and know what to look for. Here's an essential elements checklist to help you get the most out of your Web ...Continue Reading
How to avoid requirements creep
Despite all the attention placed on defining requirements, creep continues to plague software projects. Learn how a different approach to requirements can curtail that creep.Continue Reading
Making requirements walkthroughs more effective (and fun)
Do you have to twist arms to get people to attend your requirements review sessions? It doesn't have to be this way. Learn how to use a simulation model to get everyone engaged in the walkthrough.Continue Reading
Template for requirements use cases
A user is looking for a template for writing requirements use cases. Robin Goldsmith walks through a few interpretations of this question.Continue Reading
Formulating test status reports based on daily status criteria
A user requests help deriving the daily status criteria for the test execution of a software project, with status criteria including test execution criteria, test case failure rate and bug rate.Continue Reading
Using proactive test design methods to catch requirements issues early
Proactive test design allows QA testers to identify requirements and design problems at an earlier stage than with traditional test cases.Continue Reading
Is a requirements freeze in a software project a bad idea?
Learn why imposing a requirements freeze in an application project is usually a misguided idea.Continue Reading
Integration testing: Is it black box or white box testing?
Integration testing of software systems can be black box or white box testing. Learn how each can be used in this Ask the Expert Q&A with testing expert Mike Kelly.Continue Reading
Use cases and SRS for requirements gathering
Before comparing use cases and software requirements specifications, you should know what each is. Requirements expert Robin Goldsmith explains how use cases and SRS work and how to use them for requirements engineering.Continue Reading
How to match the test environment to the production environment
Testers often find a gulf between test results in a test environment and test results in a production environment. Testing expert John Overbaugh offers strategies for ensuring that test results in different environments match.Continue Reading
Running UAT and system testing in parallel
Conducting user acceptance testing and system testing at the same time may or may not be a good choice. Expert Baher Malek discusses the factors that testers need to consider when attempting a parallel UAT process.Continue Reading
Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?
Agile software development calls on developers to write clean code, according to Robert "Uncle Bob" Martin. This free chapter introduces the concepts and methods programmers can adopt to write truly clean code.Continue Reading
How to estimate change requests in requirements
Software requirements are often subject to change; using a sound estimation process helps greatly to manage change. Requirements expert Betty Luedke explains, in detail, how to implement good estimation techniques.Continue Reading
Use cases: Who writes them, what data do you include?
Typically a business analyst writes the use cases for a software project. But who writes them doesn't matter as much as what is included in them, says expert Robin Goldsmith.Continue Reading
Scrum and requirements gathering
Scrum, an agile methodology, offers great advantages for certain software project teams. Expert Betty Luedke explains the basic tenets of Scrum and how they affect requirements engineering.Continue Reading
Software testers: Identity crisis or delusions of grandeur?
Without a clear understanding of what software testers do, it's only natural that people try to interpret what they do from their job title. The problem is the number of different titles people have creates confusion, says Scott Barber.Continue Reading
The scope of user acceptance testing
User acceptance testing is ineffective if testers don't allocate the proper time and resources. Expert Karen N. Johnson explains how to avoid shortchanging UAT.Continue Reading
Testability requirements and verification work
Testability and verifiability are a category of nonfunctional requirements. Expert Roxanne Miller explains how these concepts fit into software requirements engineering.Continue Reading
Testing for performance, part 1: Assess the problem space
In the first article of this series on testing for performance, Mike Kelly outlines ways for you to understand your content and the system and figure out where to start testing.Continue Reading
Prioritizing software testing on little time
Too many test cases and too little time? Expert Scott Barber explains how to prioritize testing.Continue Reading
Requirements gathering for payroll application
Engineering requirements for a payroll or similar application demands careful consideration. Expert Rob Apmann explains how to approach this complicated task.Continue Reading
Testers' involvement in requirements gathering important
In this increasingly complex software development era, it is important to include testing as early in the project as possible. And that means starting with requirements gathering.Continue Reading
The state of performance testing
Some might say 2007 was the year the software industry started taking performance testing seriously. In this month's Peak Performance column, Scott Barber takes a look at what happened in the performance testing field in 2007 that made that so, and ...Continue Reading
Usability testing vs. user acceptance testing
Usability testing and user acceptance testing may sound similar, but these tests have different focuses and are executed at different times in the SDLC. Expert Karen N. Johnson explains how these tests work.Continue Reading
How to define the scope of functional security testing
With a many internal threats originating from applications, functional security testing is one of the most reliable ways to identify internal security vulnerabilities.Continue Reading
Five steps for performing an effective software product review
Review or inspection is an important activity in any project implementation. Performing a good review of the developed product, along with capturing metrics, helps in building a quality product. In this member-submitted article, Murugan Srinivasa ...Continue Reading
How to write an effective test report
This member-submitted tip provides a guideline for essential information that should be included in a test report.Continue Reading
Don't mistake user acceptance testing for acceptance testing
Despite the many references that concur on the definition of acceptance testing, people still get confused. Scott Barber clarifies things in this month's Peak Performance column.Continue Reading
How to create a testing scorecard
A software testing scorecard can be a good tool for managing a team's progress. Expert John Overbaugh explains how to create a testing scorecard and that fits yours and the customer's needs.Continue Reading
Free load and performance testing tools
What is a good choice for a free load testing tool? Expert Dan Cornell offers his advice and explains how to get started with your testing tool.Continue Reading
Who does what in a Testing Center of Excellence?
With a Testing Center of Excellence (TCE) an organization can improve its software testing. Learn how and what each TCE participant does in this article from David W. JohnsonContinue Reading
How to structure a software requirements document
Effective requirements documentation is essential for any good software project. Expert Karl E. Wiegers explains how to structure your software requirements documents.Continue Reading
Test plan and test strategy
Software testing is helped by a good test plans, strategies and logistics. Expert Scott Barber explains what these aspects of the testing methodology are.Continue Reading
Software requirements specification and IEEE standards
What does the IEEE outline for requirements specifications, and how strictly should you abide by that standard? Expert Karl E. Wiegers digs into the details of an SRS.Continue Reading
What to look for in a Web application security testing tool
If you do a lot of Web application security scanning, any testing tool you use must have these features, says security expert Kevin Beaver. They will save you lots of time and effort and will increase the number of valid vulnerabilities found.Continue Reading
How to test Web site login security
Input validation is critical for the security of Web sites. Here's a techniques you can use to make sure your site isn't vulnerable to SQL injection.Continue Reading
Software testing deliverables: From test plans to status reports
Core sets of deliverable are required for any software testing phase. In many cases they include a test plan, test case, defect documentation and status report. Learn what is required for each in this tip from David W. Johnson.Continue Reading
Rewarding team members for outstanding work
Recognizing or rewarding team members for jobs well done helps build morale. Your sincere appreciation can go a long way, says project management expert David Christiansen.Continue Reading
How to document system, software requirements
There are various formats you can use to document system and software requirements. However, no single one is sufficient to represent all requirements. You need to follow an integrated approach.Continue Reading
The role of a software test manager
Effective software test managers not only understand the discipline of testing, but they are also able to manage and implement a testing process in their organizations. That requires team leading skills, communication skills, and being able to ...Continue Reading
Software requirements: Using models to understand users' needs
Successful software projects involve users early and often to explore and reach closure on requirements. Using analysis models you can depict user needs with a combination of diagrams and structure text such as tables or templated text.Continue Reading
I don't want a Web application security product; I want a solution
The number of Web application security products available is enough to make your head spin. A better option is a total solution that handles all of your Web application security needs, says application security expert Anurag Agarwal.Continue Reading
How to create a secure login page using ASP.NET
A secure ASP.NET login page is easier to create than one might assume. Expert Dan Cornell explains how to use authentication and authorization to ensure your login page is safe.Continue Reading