QA Training and Consulting to improve practices and processes

Corporate QA Training Curriculum 

QA training designed for flexibility and customized to your needs

LogiGear University’s corporate training program helps organizations equip their testers with the relevant concepts, strategies, test methods and skills needed to effectively test increasingly complex software applications.  Blending our training classes with your internal process create an optimal body of testing knowledge that enable development teams to resolve testing challenges faster, find bugs sooner, and create a culture of software testing excellence.

  • Do more in less time with fewer resources
  • Test larger and more complex systems
  • Collaborate with team members around the world
  • Communicate among teams using different tools, processes and terminology
  • Be more Agile


Programs often include creating content for the company's internal bug tracking tool, test plans, technical glossary, new automation framework/tools, or test case management system.

Corporate Curriculum

Working with offshore test teams

This two-day course focuses on developing many of the soft skills needed to lead and manage offshore teams.

Description:

The course is directed towards developing a strategic approach to distributed test project management, effective communication, bug-database management and metrics, resource evaluation, and successful test execution, as well as many of the "soft" skills needed to lead and manage offshore teams. Implementation and use of test management tools and documentation is also covered. Application of these concepts is demonstrated in class examples, discussions and exercises. In this class you will learn how to best prepare yourself for leading and managing offshore teams to maximize test productivity while minimizing quality risks and stress.

Who should attend:

Experienced software testers, test engineers, and project managers who will be planning for and executing the testing of a software development project, or anyone who wants to develop practical test-planning and test-group management skills for successful management of software test projects.

Course materials (included):

We provide a handbook (approximately 400 pages) that includes copies of the course slides, sample test plan materials, sample matrices and graphs, and lists of useful print and online resources.

What you will learn:

At the completion of this course, students should be able to:

  • Understand how distributed development differs from single site development.
  • Understand models of offshoring and common issues for offshore resources.
  • Analyze differences in development lifecycles, such as waterfall and Agile, and their unique differences with offshore teams.
  • Assess staff skill set and experience for optimal task distribution and management.
  • Build and execute a variety of test strategies.
  • Build communication infrastructure to support visibility into testing.
  • Set up communication for project success, reduced stress and to build trust.
  • Understand and manage the politics of leading test projects.
  • Report on project progress and test-coverage.
  • Use risk analysis to improve visibility and software quality.
  • Understand the essentials of test management documentation.
  • Write and communicate meaningful test plans.
  • Better manage the bug database.
  • Make use of meaningful project and bug database metrics.
  • Understand the test tools available for use on a project.
  • Use leadership skills for better test execution and staff retention.
  • Explore and understand a wide variety of cross-cultural issues.
  • Focus on areas of “working with Americans” key to test and software development projects.
  • Use leadership, coaching and team building techniques.
  • Use training to build skill, prevent problems, mitigate risk, retain staff and reduce turnover.
  • Successfully close the test project.
  • Conduct useful project postmortems and collect feedback for continuous process improvement.

Course outline:

Overview of Leading Offshore Test Projects

  • How are they different?
  • A new understanding for the role of a test lead and manager

The Big Picture

  • Getting your own house in order: standardize, formalize, and document your software development and testing process
  • Unique issues with offshore testing and QA not found in development
  • Setting expectations for best performance
  • Build transfer process and “What we do each week. “

Analyzing your Staff

  • Examine the skill sets for offshore test engineers and the impact on task distribution and execution
  • Developer testing vs. Tester testing
  • Understanding of the end-user
  • Common software project problems and their effect on testing
  • What is high quality? Customer satisfaction? What is a bug?

Test Strategy and Test Plan

  • Test strategy and how to test
  • Coverage and the goals of testing
  • Risk-based testing, prioritizing and test selection
  • Making a meaningful and useful test plan

Test Project Documentation and Deliverables

  • Test case management tool/QC
  • The bug tracking system
  • Project and defect measurement and metrics
  • Reporting progress: status reports

Common Issues for Test Leads

  • Leadership
  • Coaching
  • Team-building
  • Working with the team at home

Excellent Communication: The Key to Successful Projects

  • Fostering good communication
  • Communication tools and infrastructure
  • Dealing with “tribal knowledge”
  • Knowledge transfer

Soft Skills

  • Building trust
  • Working across cultures and “Working with Americans”
  • Potential cultural problems
  • Delivering bad news; saying "no" to keeping secrets—transparency and visibility in work
  • Being on-time and issues of time, criticality of work and deadlines

Using Training to Solve Problems

  • Mechanics of training and coaching to set yourself up for success
  • How training can solve process and practice issues
  • Definition of areas for training
  • Staff retention and turnover

Closing Out the Test Project

  • Activities during final phase
  • Post release and preparing for the next project
  • How to conduct useful post mortems

Prerequisites:

One year of experience in software testing, a year of experience in software development management, or equivalent. A full understanding of quality theory, project sizing and estimation, various test strategies, and experience documenting test projects.

 

Exploratory testing

This two-day course gives test engineers a global understanding of exploratory testing.

Description:

From why we do it and its uses to how we do it and the value of measurement, Exploratory Testing will be examined and practiced to empower test engineers in using this method, finding better bugs earlier, focusing on customer satisfaction and making exploratory testing more manageable and easier to use as a necessary and important test method.

What you will learn:

  • How to test earlier and find better bugs!
  • What is exploratory testing and why is there so much argument about its value?
  • The psychology of good testers and cultural issues with exploratory testing
  • When and how it can best be used in your test strategy
  • Incorporating effective exploratory testing into your test strategy
  • Management and measurement issues about exploratory testing
  • Problems and misconceptions
  • Further study

Course outline:

Part 1   Exploratory Testing: What is it?

  • Why do it?
    • Testing vs. Validation
  • What is it used for? Goals of exploratory testing?
  • What are the common practices?
    • Focus on the user
    • The importance of exploratory testing in Agile development

Part 2   The Exploratory Testing Approach

  • Project politics and “ad hoc” testing
  • Testing psychology for exploratory testing
  • Team culture and exploratory testing
  • Risks of exploratory testing
  • Problems and misconceptions

Part 3   How to do Exploratory Testing

  • Black box, white box and gray box testing
  • Discussion and exercises on varieties of exploratory testing including:
    • User scenario testing
    • Modeling
    • How to Break Software (by James Whittaker)
    • Error guessing
  • Heuristics test oracles
  • Focus on test data
  • Common types of issues found in exploratory testing

Part 4   Management and Measurement Issues in Exploratory Testing

  • Planning and communicating on exploratory testing
  • Tips for managing and measuring exploratory testing
  • Communicating coverage in exploratory testing
  • When is testing done?
  • Fostering a management and development team culture to support exploratory testing

Each section will have examples and exercises

 

Testing in Agile development

This class provides effective strategies and tactics to support the goals of Agile development.

Description:

Most agile discussion now focuses on practices. Scrum, for managing product development, and eXtreme Programming (XP), for software development practices, are the most common. Both Scrum and XP exclude traditional software testing from their practices. Testing in XP revolves around test driven development (TDD), unit testing.  How and where does the test engineer/traditional testing fit in? Traditional testers are involved with code much earlier than in traditional-style projects. In this class we offer effective strategies and tactics, specific test practices, experience and possible points-of-conflict so that the test team supports the goals of agile development and provides the most effective technical service to the product team.

We begin with essential understandings of Agile — for example, better not necessarily faster, people over process — that impact the everyday work of test teams.

Most of the class focuses on how traditional test teams provide value and fit into Agile projects.

This includes:

  • New planning activities
  • New test strategies
  • Increased volume of code, and faster code deployment
  • Different ideas on test artifacts
  • New ideas on test automation
  • Different issues with offshore and outsourced teams
  • Examples, exercises and mini-scrums

What you will learn:

  • Foundational Agile concepts
  • Scrum basics
  • Common XP Practices
  • Problems and misconceptions of agile
  • Mis-implementations of agile that impact test teams and solutions
  • Important QA and test ideas and practices that need to be remembered on agile projects
  • New test practices and strategies for testing on agile projects
  • With significant automated Unit testing and Acceptance testing, what is left for traditional test teams?
  • How to cope with a significant increase in delivered code
  • Continuous Integration
  • Building a new test strategy from our old practices
  • Significant changes to test artifacts; specifically test cases and test plans
  • New project management tools specifically for agile projects
  • Test and project measurement on agile projects
  • A new level of communication as the foundation of agile development
  • Automation strategies in an agile world
  • New complexities and solutions for agile offshore testing
  • Further study

Course outline:

Chapter 1   Agile: What is it?

  • How did we get here?
  • What are the common practices?
  • Some Scrum and XP practices directly related to testing (examples)
  • TDD/Unit testing
  • Continuous Integration
  • Acceptance testing in XP
  • Ideas about Done
  • Role of “team” and test/QE
  • Problems and misconceptions of Agile

Chapter 2   What this can Mean for Testing

  • How does Agile impact testing?
  • Important Agile and quality concepts we need in Agile testing
  • Limitations of unit testing, acceptance testing
  • Test methods and techniques for Agile
    • Exploratory testing skills
    • The tasks traditional test teams did; who does them now?
    • Better estimation skills
  • Skills for Agile test engineers

Chapter 3   Test Artifacts in Agile

  • Does Agile mean we stop documenting?
  • User stories and test cases
  • Importance of the conversation with user stories

Chapter 4   Tools

  • New classes of tools

Chapter 5   Test Automation in Agile: It’s Absolutely Essential…and Different.

  • Importance of large-scale automated regression
  • Test design and framework implementation for rapid projects
  • Action Based Testing and keyword-driven testing

Chapter 6   Agile Offshore

  • Agile projects with outsourced and/or offshore teams
  • Some of the old obvious problems exacerbated
  • Solutions
Chapter 7   Agile Testing Roundtable
  • Common testing problems in Agile
  • Some politics to watch out for in Agile projects
  • ScrumButts and Agilefalls warnings!
  • Using the sprint retrospective for process improvement


Testing computer software

This three-day course focuses on strategic and tactical approaches to software testing.

The course surveys the essential theory and foundations of software quality, as well as the practical skill-building necessary to be an effective and active contributor to the software development process. It covers software testing and test project management techniques that are applied daily by successful software development companies.

Smarter testing leads to improved quality. To test smarter, we start by looking at how various development methods affect testing and test documentation. We then cover a wide variety of test methods from regression and acceptance testing to exploratory and scenario testing. This course includes requirements-based testing, as well as requirements stability and traceability. The goal here is to arm you with the best practices for efficient test design and test case documentation. You will learn how to create useful test matrices and decision tables. In addition, we focus on effective defect communication.

perkinelmer"Testing Computer Software is an excellent course. My entire staff is encouraged to take this course."
Emily Campbell, Product Test Manager - Perkin Elmer
 


Who should attend:

Software testers, business analysts, test managers, test specialists, quality assurance specialists, project managers and software-knowledgeable individuals who want to develop practical testing and test result reporting skills — anyone who wants to improve effectiveness in testing, test case design, test-planning, project management, and test-group management.

Course materials (included):

A complimentary copy of Testing Computer Software by Cem Kaner, Jack Falk and Hung Q. Nguyen, (2nd Edition, Wiley, 1999) is included with this course. The bestselling software testing book of all time, Testing Computer Software set the standard for test engineering.

A handbook (approximately 500 pages) is also provided. The handbook includes copies of the course slides, sample test plan materials (including several testing templates), a few recent publications, and a list of useful print and online resources.

What you will learn:

  • Essentials of product development
  • The role of test engineers in product development
  • The importance and use of phase milestone criteria
  • How and where testing fits in the software development lifecycle
  • Value of quality & cost of quality and testing
  • Boundary value analysis & equivalence class partitioning
  • Objectives and limits of testing; testing coverage
  • Distinctions of white box, black box & gray box testing
  • Test terminology
  • Essential test types and test methodologies
  • Requirements-based, regression, fault injection/forced error handling, and other test methods
  • Understanding software errors, types of errors
  • How to report software errors
  • Techniques for analyzing and reproducing errors
  • Good black box test case design
  • Creating decision tables and other test case documentation
  • Basic testing tools
  • Basic uses of test automation
  • The objectives of test planning
  • Test plans and a review of test plan templates

Course outline:

  • Lessons learned in software testing
  • An overview of product development
  • The software development lifecycle
  • An overview of a testing organization
  • Costs associated with testing and quality
  • An example test series: The program’s first tests
  • The impossibility of complete testing / problems of coverage
  • Objectives of testing
  • Getting started: terminology, test types and test methods
  • Software errors
  • How to report software errors
  • Analyzing software errors
  • Reproducing software errors
  • Introduction to black, gray and white box testing
  • Test planning materials
  • Black box test case design
  • Essential test case development methods
  • Combination testing
  • Model-based Testing
  • A brief survey of software testing tools
  • Basics of test automation
  • The test plan

Optional/Reference:

  • Testing product documentation
  • Testing the installer
  • Testing printers and other devices

Prerequisites:

There are no formal prerequisites for this course. The course assumes familiarity with computers and a strong practical interest in software development or quality assurance. This course is multi-layered. It provides a strong introduction for those who have just accepted jobs as software test engineers, and offers material of interest to senior test engineers, test managers, programmers, and project managers.

Download software testing white papers



Lead software test projects with confidence

This two-day course focuses on developing a strategic approach to test project management, effective communication, bug-database management, resource planning, and successful test execution, as well as some of the "soft" skills needed to lead and manage a team. Implementation and use of test management tools are also covered.

Application of these concepts will be demonstrated in class exercises. Learn to maximize test productivity while minimizing quality risks and stress.

Who should attend:

Experienced software testers, test engineers, and project managers who will be planning for and executing the testing of a software development project — anyone who wants to develop practical test-planning and test-group management skills for successful management of software test projects.

Course materials (included):

We provide a handbook (approximately 400 pages) that includes copies of the course slides, sample project test schedules and project map, sample test plan materials, sample matrices and graphs, practical exercises and lists of useful print and online resources.

What you will learn:

At the completion of this course, students should be able to:

  • Develop project analysis skills
  • Define tasks and deliverables
  • Perform resource planning
  • Understand test project size estimation methods
  • Understand project mapping and scheduling
  • Effectively communicate
  • Understand and manage the politics of leading test projects
  • Report on project progress and test coverage
  • Understand risk-based testing methodology
  • Understand the essentials of test-management documentation
  • Write meaningful test plans
  • Manage the bug database
  • Manage test resources
  • Understand the essentials of outsourcing and the issues of offshore resources
  • Understand aspects of building a successful outsource/offshore team
  • Make effective use of meaningful project and bug-database metrics
  • Understand the test tools available for use on a project
  • Be well-versed in team-building techniques
  • Know hiring strategies
  • Perform project postmortems

Course outline:

Overview of Test Project Planning

  • What is a test lead?
  • A different understanding of quality

Understanding a Software Project

  • The Big Picture
  • The Software Development Lifecycle
  • The Small Picture: Getting the Details for a Project
  • Test Project Size Estimation Methods
  • Coverage, Test Goals
  • Risk-based Testing, Prioritizing and Test Selection
  • Negotiations and Agreements
  • Making a Project Map

The Test Plan

  • General Discussion
  • Making a Meaningful Test Plan
  • LogiGear 1-page Test Plan

Test Project Documentation or Deliverables

  • Test Case Management Tool
  • The Bug Tracking System
  • Project & Bug Metrics
  • Reporting Progress: Status Reports

Common Issues for Test Leads

  • Leadership
  • Fostering Good Communication
  • Hiring
  • Outsourcing
  • Activity During Final
  • Post Release, Preparing for the Next Project

Prerequisites:

Completion of Testing Computer Software, six months of experience in testing, a year of experience in software development management, or equivalent.

Download software testing white papers



Effective test case design and management

This 2-day hands-on course offers an intensive workshop in a wide variety of testing methods and test case development strategies.

The course is designed for those who already have a solid understanding of software quality and testing. In it, we provide thorough hands-on examples and practical state-of-the art methods for effective software testing and test communication through the complete software development lifecycle. It also includes best practices for documenting test cases for automation.

For better effectiveness and test coverage we must be armed with a wider variety of methodologies and approaches than only requirements-based or ad hoc testing. Many testers and test leads dread the greater demand for documenting their work, even as more groups move to use test management tools. This course discusses strategies to deal with this problem.

You will learn how to create useful test cases, test matrices and models as well as how to move from spreadsheets and matrices to test case management (TCM) tools.

Who should attend:

Software testers, business analysts, test managers, testers, test engineers, quality assurance specialists, project managers and software-knowledgeable individuals who will be planning the testing effort, developing test plans or test cases for software development projects.

Course materials (included):

We provide a handbook (approximately 300 pages) that includes copies of the course slides, a few recent publications, and a list of useful print and online resources.

What you will learn:

  • Essential test case development
  • Full lifecycle test strategies
  • How various development methods affect testing and test documentation
  • A variety of test methods:
    • Requirements-based testing, including requirements traceability and requirements stability
    • Test case basics
    • Keyword-driven or Action-Based Testing (ABT) methodology
    • State transition/state model-based testing
    • Exploratory and effective ad hoc testing approach
    • Equivalence class partitioning and boundary value analysis
    • Regression testing
    • Fault injection / forced error / negative testing
    • DAST- Diagnostic Approach to Software Testing
    • Data-DriventTesting(DDT)
  • Tips for writing excellent test scenarios
  • Keys to develop test cases for automation
  • Test selection
  • Risk-based testing
  • Data selection
  • Best practices for test case maintenance
    • Dealing with shifting requirements
    • How to formulate reusable test suites
  • How test case management tools are used

Course outline:

  • Full lifecycle test strategies
  • Glossary - Putting the concepts together
  • Test case essentials
  • Test methods
  • Test case development
  • Test cases for automation
  • Equivalent class partitioning and boundary value analysis data selection
  • Test selection
  • Test case management systems

Prerequisites:

Completion of Testing Computer Software, six months of experience in testing, a year of experience in software development management, or equivalent.

Download software testing white papers



Applied testing for test engineers

This two-day hands-on course provides test engineers with useful techniques and applications of technologies that enable them to get the right testing done at the right time, with better focus, and more intelligence.

The techniques and knowledge presented in this class help test teams get more testing done, and most importantly, get the right testing done at the right time. These techniques also provide the tools for testing on Agile or RUP development projects.

The goal of this class is to develop strategies and skills for analyzing and running unit and integration tests, from the perspective of learning what tests to take on, what tests a developer ought to be running, and some tools for testers to accomplish these tests. Many of the same techniques can be applied to API and interoperability testing. They are particularly useful for testing on newer, faster development projects using eXtreme, Agile, Test-First, Test Driven or UML/Use Case SDLCs. The goal is to demystify early testing and look for ways to maximize your testing effort. Test teams can also use alternative test design methodologies other than the requirements-based testing approach. We will introduce test case design using gray-box and action-based/keyword-driven testing, and other approaches. You will be equipped with new skills that enable you to select and perform the most effective testing practices to expose software errors, improve coverage and reduce execution time.

Topics include:

  • Review of software development life cycle and development phases
  • Differences between developer and QA/tester testing
  • Unit testing solutions for black-box testers
  • Interoperability/integration testing techniques

Course materials (included):

We provide an extensive handbook that includes copies of the course slides, recent articles, and lists of print and online resources.

What you will learn:

At the conclusion of the course, participants should be able to:

  • Bridge the gap of testing from a developer’s perspective to a tester’s perspective
  • Understand basic unit testing methods: i.e., what your developers do
  • Be familiar with unit, system, integration, and user acceptance development and testing paradigm: tasks, tools and methods used during each phases
  • Know which bugs unit tests can expose and which they will miss
  • Leverage (as a tester, not a developer) unit tests to find more bugs earlier
  • Effectively use developer tools (including harnesses, stubs, drivers, development platform-specific tools) in black-box testing
  • Plan testing on Agile development projects
  • Understand API testing: What is it? How it is used and how does one perform API testing effectively
  • Know some new and sometimes forgotten strategies and test design methods including attack-based testing, model-based testing, and keyword-driven testing
  • Perform more effective test-case design with a gray-box testing approach
  • Use log files in testing
  • Create useful logs to find and analyze application and system failures
  • Select the most effective practices to find bugs, and optimize test planning and execution time

Course outline:

Software Development Lifecycles

  • Waterfall
  • Spiral
  • Rapid Application Development (RAD)
  • Spiral/Iterative/Incremental
  • Agile, eXtreme, RUP, Test-first, Test Driven

Development Phases: Unit, Integration, System and User

  • Attributes of each type of testing
  • When to execute each type of test

Smarter Testing

  • Tips and techniques for improving your testing
  • White-box vs. gray-box vs. black-box testing
  • Developer testing vs. tester testing

Test Methodology

  • James Whittaker’s How To Break Software
  • Model-based/State-transition testing
  • Testing use cases
  • Action-based/keyword-driven testing

Unit Testing

  • Test harnesses, stubs, mock objects
  • Common strategies for unit testing
  • Common unit testing frameworks

Interoperability/Integration Testing

  • Case study of a web-based application

API Testing

  • Differences between API testing and unit testing
  • Reasons and methods for API testing
  • API test case design techniques

Logs

  • Types of information that can be found in logs
  • Benefits of logs to testing
  • Different types of logs
  • Techniques for finding useful information in logs

Prerequisites:

Experience with software testing (completion of Testing Computer Software and six months of experience testing applications or one year of software testing experience), either as a tester or a manager. Some familiarity with programming is helpful for understanding the more technical examples. However, non-technical people are also encouraged to enroll.

Download software testing white papers



Mobile testing

This two-day, hands-on course offers an intensive experience in a new way of thinking for mobile testing.

The course is designed to provide test engineers with useful techniques and applications of technologies that enable them to test earlier, with better focus, and more astutely. The techniques and knowledge presented in this class help test teams get more testing done, and most importantly, get the right testing done at the right time. These techniques also provide the tools for testing on Agile or RUP development projects.

The goal of this class is to develop strategies and skills for analyzing and running unit and integration tests, from the perspective of learning what tests to take on, what tests a developer ought to be running, and some tools for testers to accomplish these tests. Many of the same techniques can be applied to API and interoperability testing. They are particularly useful for testing on newer, faster development projects using eXtreme, Agile, Test-First, Test Driven or UML/Use Case SDLCs. The goal is to demystify early testing and look for ways to maximize your testing effort. Test teams can also use alternative test design methodologies other than the requirements-based testing approach. We will introduce test case design using gray-box and action-based/keyword-driven testing, and other approaches. You will be equipped with new skills that enable you to select and perform the most effective testing practices to expose software errors, improve coverage and reduce execution time.

Topics include:

  • Review of software development life cycle and development phases
  • Differences between developer and QA/tester testing
  • Unit testing solutions for black-box testers
  • Interoperability/integration testing techniques

Course materials (included):

We provide an extensive handbook that includes copies of the course slides, recent articles, and lists of print and online resources.

What you will learn:

  • At the conclusion of the course, participants should be able to:

    • How to bridge the gap of testing from a developer’s perspective vs. from a tester’s perspective
    • An introduction to unit testing methods—What your developers do
    • Unit, system, integration, and user acceptance development and testing paradigm:Tasks, tools and methods used during each phases
    • Bugs that unit tests can expose and ones that they will miss
    • How to leverage (as a tester, not a developer) unit tests to find more bugs earlier
    • Effective use of developer tools (including harnesses, stubs, drivers, development platform-specific tools) in black-box testing
    • How to plan testing on Agile Development projects
    • API Testing: What is it? How it is used and how to perform API testing effectively
    • New and sometimes forgotten strategies and test design methods including attack-based testing, model-based testing, and keyword-driven testing
    • More effective test-case design with a gray-box testing approach
    • How to use log files in testing
    • How to create useful logs to find and analyze application and system failures
    • How to select the most effective practices to find bugs, optimize test planning and execution time

Course outline:

Software Development Lifecycles

  • Waterfall
  • Spiral
  • Rapid Application Development (RAD)
  • Spiral/Iterative/Incremental
  • Agile, eXtreme, RUP, Test-first, Test Driven

Development Phases: Unit, Integration, System and User

  • Attributes of each type of testing
  • When to execute each type of test

Smarter Testing

  • Tips and techniques for improving your testing
  • White-box vs. Gray-box vs. Black-box testing
  • Developer testing vs. Tester testing

Test Methodology

  • James Whittaker’s ‘How To Break Software’
  • Model-based/State-transition testing
  • Testing use cases
  • Action-based/keyword-based testing

Unit Testing

  • Test harnesses, stubs, mock objects
  • Common strategies for unit testing
  • Common unit testing frameworks

Interoperability/Integration Testing

  • Case study of a web-based application

API Testing

  • Differences between API testing and Unit Testing
  • Reasons and methods for API testing
  • API test case design techniques

Logs

  • Types of information that can be found in logs
  • Benefits of logs to testing
  • Different types of logs
  • Techniques for finding useful information in logs

Prerequisites:

Experience with software testing (completion of Testing Computer Software and six months of experience testing applications or one year of software testing experience), either as a tester or a manager. Some familiarity with programming is helpful for understanding the more technical examples. However, non-technical people are also encouraged to enroll.

Download software testing white papers


agile test automation

TOP 10 WAYS

TO MAKE IT SUCCESS

image GET YOUR FREE BOOK
Contact us today to find out
how affordable our services are

QA Management Consulting

Get a clear picture of what's going on

The goal of doing a test strategy assessment is to get a clear picture of what is going on in testing — the good things, the problems, and possible paths to improvement.

Fundamentally, a test assessment is a data-gathering process. To make effective decisions, we gather data about your current test processes and their effectiveness from across organizational and managerial boundaries.

It is important to note that when embarking upon such an assessment, this effort is much larger than the test team alone. Issues will arise over ownership of quality, as well as the goals of testing. And, possibly, work may actually increase.

A successful assessment process requires:

  • Executive sponsorship
  • A measurement program
  • Tools to support change
  • An acceptance of some level of risk
  • Avoidance of blaming testing for project-wide failures
  • Commitment over the goals of testing
  • An understanding of testing or quality assurance across the product team
  • Responsibility for quality

A test strategy is a holistic plan.  We start by gaining a clear understanding of the core objective of testing by performing an assessment to understand the core objective of testing necessary for your success. From this we derive a structure for testing by selecting from many testing styles and approaches available meet your objectives.

Implementing the resulting roadmap for improvement will allow you to substantially improve the performance of your software testing organization and solidify your test strategy.

Contact us today to find out
how affordable our services are