COURSE 3000 | 2-DAY PUBLIC SESSION | 3-DAY VIRTUAL SESSION
Developing Software Testing Techniques

---

Course Outline

Section I. Software Testing Foundations & Conventional Thinking

Every organization has some form of testing. From this basic assumption, a foundational framework is presented for each participant to formulate a personal scorecard and process improvement plan. Utilizing a combination of industry accepted standards and best of practice techniques a strong base is built from which all future testing can occur.

• Test Framework
  • Orientation in Terms of Development Method
  • Test Phases: Planning/Acquisition/Measurement
  • Levels of Testing
  • Candidates for Standardization
• Test Deliverables
  • IEEE 829 Collective (Plans, Design, Scripts, Reporting)
  • Automated Supported Resources and Application
  • Forming Testing Benchmark Standards
• Test Planning
  • Sources
  • Master and Level-Specific Test Planning
  • Purpose and Effective Formatting
  • Elements
• Test Case Design
  • Establishing Objectives
  • Facilitating Requirement Quality Improvements
  • Maintaining Traceability (calibration)
  • Designing Effective Tests
• Communicating Test Results
  • Progress Reporting
  • Adapting to Project Changes
  • Relating Meaningful Status

Practice Session
Each participant, guided by the instructor, will prepare a scorecard reflecting present practices. The scorecard will be used to form a uniform baseline for added discussion throughout the course and provide an action list for further use in company deployment. To reaffirm and establish a basis for implementation (or enhancement) a series of practice exercises will be conducted for:

• Test Planning
• Test Case Construction based on sample requirements
• Practicing the principles of test case calibration and traceability

These three areas will be based upon a single project scenario, leading to a single unified solution set that can be used as an illustrative example.

Section II. Test Planning Development Considerations

Software planning is challenged by the same obstacles that all projects face. There is never enough time, and you are always exposed to risks from the unexpected. Miscalculations and inappropriate decisions (made without sound knowledge) create more risk and lower the value of work performed.

• Key planning considerations
  • Resourcing
  • Scope Definition
  • Formalities
• Test Budgeting Methods
  • Percentage-based methods
  • Task-driven approach
  • Critical chain buffering (CCB)
• Budget Adjustments
  • Delivery-driven projects
  • Synchronizing with development delivery segments
  • Functioning in aggressive or iterative projects

Practice Session
An electronic test planning and budgeting tool will be provided. In groups, students will develop a familiarization with the tool and arrive at a set of conditions that must be taken into consideration once the initial test budget gets formed. Additional discussions will center on the influences of existing testware and overall project team expertise.

Section III. Systematic Software Testing Practices

While applications are seldom used in a systematic way, testing relies heavily on a tactical approach. The operating premise is that a baseline is necessary as the foundation for all other testing, at present and in the future.

• High-Yield and Beneficial Methods
  • Harvesting & Qualifying Test Objectives
  • Calibration Value (even in Agile environments)
  • Leveraging Risk
  • Test Methods & Practices
  • Developing Test Cases
• Effective Regression Testing
  • Managing Effective Testware Repositories
  • Full & Partial Regression Testing
  • Utilizing Exploratory and Ad Hoc Testware

Practice Session
In groups, a software specification will be examined, test objectives formulated, and test developed. This will be carried out using calibration techniques. A final step will be to look for ways to reduce the test set by employing a critical examination of the test calibration matrix.

Section IV. What is Testing Trying to Say?

Exceptional testing is lost if our communications is misdirected, ineffective, or not understandable. Bring new life to the meaning of test communication and excite all stakeholders from management to those in the trenches.

• Effecting Positive Test Communication
  • Low Cost/High Yield Test Reporting Radiators
  • Valuable & Useful Testing Metrics
  • Using Test Information Effectively – Shaping Engineering & Test Practices
  • Drawing Interest Through Participation
• Balancing Content with Form in Test Radiators
  • Overall Visible Reporting Forms
  • Understanding the Test Audience
  • Removing Misguided Assumptions for Testing Services

Practice Session
The class will be broken up into teams, comprised of at least two groups: One group representing testers who will present test results, and the other comprised of stakeholders and project team members who are anxiously awaiting this information (but will pose some interesting confrontational issues which your instructor will guide you through).

Section V. Testing Challenges

Projects are constantly under attack and the effects reverberate throughout the entire team, including testing. The ability of a testing group to adapt to a wide variety of situations will prepare them to respond in an appropriate and efficient fashion.

• Testing Situation Challenges
  • Routine Maintenance
  • Emergency Repair
  • Commercial Off The Shelf (COTS) Solutions
  • Hybrids
• Managing Challenges that Jeopardize Committed Test Projects
  • Test Urgency Management
  • Test Resource Deployment/Redeployment
  • Minimizing Negative Test Cadence

Practice Session

Utilizing a list of test artifacts and tasks, each group will determine under what situations will these items be used. In cases where they are not applicable the group will determine what suitable alternative measures are considered appropriate.

Section VI. Right-Fitting Testing to Various Development Approaches

With more than one way to reach a goal, testing needs to be ‘right-fit’ for the situation. A single approach, while easy to implement, will create erratic demands and missed opportunities for low cost early detection of goodness and of errors.

• Understanding Why One-Size Doesn’t Fit All
• Method Specific Test Adaptations
  • UML
  • Rapid Development Models
  • Iterative Development
  • Outsourced Projects
  • Agile Engineering
• Addressing Multi-Discipline Projects

Practice Session

Open class discussion surrounding the use of various development methods, appropriate use (and misuse), how testing can serve as a sounding board/catalyst for ‘right’ application, and the means of adapting test practices to each development method. This includes projects that utilize multiple development methods.

Section VII. Business Cultural Pressures and Conditions

The longer the project the more change we can expect. Even though we may try and hold change to a minimum the realities of today’s dynamic business climate require change. Some of these adjustments can be postponed while others require midflight adjustments. Test management is challenged to remain responsible while being responsive.

• Understanding HOW BIG Change Is
• The CONE of Uncertainty
• Resourcing
  • Flexible Staffing
  • Adaptive Test Design
  • Employing Testware Assets
• Delivery Variations & Test Adjustments

Practice Session

Utilizing a real-life test plan, test design and a sample of test cases each group will be introduced to a change in project direction. Given limited time, each group will formulate a plan of attack to address this change of direction, and present quantifiable measures for the impact.

Section VIII. Business Dynamics and Control Effects in Testing

Change is a business reality, and projects that fail to plan for it create unnecessary risk for themselves. Often this has a trickle-down effect on both testing and results. Positioning testing to adapt and overcome these dynamics will produce positive results for your project, team and stakeholders.

• Business Value and Delivery Importance
  • Proper Placement of Test Energy
  • Utilizing and Adapting to Changing Baselines
  • Engaging Stakeholders: Accessibility & Engagement

Practice Session

The class will discuss how to engage project stakeholders and determine which critical aspects will make your pursuit a reality. Using this information, your groups will develop various solutions suitable for use at your own companies. (…plans of action, not just words!)

Section IX. Special Niche Testing Areas

A recent International Testing survey revealed that leading companies were marginally testing the basic functions of their software systems. This left a large gap of opportunity for errors in both the foundation elements of the applications, and numerous areas that went totally unattended. In this segment you will gain an awareness of these application aspects, learn the leading reasons why they require at least some examination, and how they may already be giving up information as part of basic foundation tests.

• Sequencing
• Beyond Functional Validation Confirmation
• Testing Targets

Practice Session

Using the 18 possible test targets (beyond functional validation) each group will organize them in order of attack. Areas where parallel attention can be given will be broken out. The final step will be learning how to manage the resourcing required in order to carry out all the testing.

Section X. Supporting World-Class Test Success

Effective test service delivery can be further improved through appropriate use of support technologies. In this segment an examination will be made of ways to improve precision, leverage engagement and increase efficiency without additional overhead burdens.

• (Test) Resource Development & Utilization
• Tools and Related Current Practice Technologies (e.g. Wiki’s, Collaborative Facilities…)
• Testing Methods and Established Techniques
• Dealing with Real-World Test Challenges

Practice Session
As a capstone "wrap-up" exercise, an example test scenario will be presented. You will formulate a complete plan of attack including budget, resource requirements, approach, task and deliverable execution, and an alternative (Plan B) to deal with potential adverse situations.