Home | About QAI | QAI Canada Home Page | Federated Chapters
Conference Home Page
Manager's Workshop
QUEST Magazine
Get Involved



Better Test Planning Solutions Workshop

 
Topic - Test Case Design

How to improve

  • Gain Knowledge of the business or product

Constraints

  • Time to learn
  • Time to transfer knowledge

Assumptions

  • Tendency to work in silos
  • Assume that you have all of the information

End Results

  • Collaborate with developers and key stakeholders

Back to top

Topic - Agile

How to improve

  • Communication to stake holders
  • Commitment to time lines

Constraints

  • Buy-in from Development Team, PM, LOB
  • Following of processes
  • Lack of Documentation

Assumptions

  • Developers deliver what was promised as deliverables
  • Identify to project team/test team what was not delivered

End Results

  • Agile works with flexibility, goodwill and communication between the project team.

 

Topic - Risk Based Testing

How to improve

  • Scope
  • Create living "application Risk Assessment" document
  • Involve right representatives evaluating risks and priorities between
    • Application
    • Functionality within application

Constraints/Assumptions

  • Management and business willing to accept and approve risks
  • Put the task of creating risk assessment as one of the milestones

End Results

  • Deliver within the deadline.

Back to top

Topic - Managing Change

How to improve

  • Idea in test case
  • Have template of major steps
  • Identify impact/costs
  • Create defects on changes for visibility
  • Communicate with development
  • Ensure regression is run
  • Test around the defect fix not only the fix
  • Identify the risks
  • Lessons learned at end of release

Constraints

  • Requirement ambiguity
  • Final frozen code before regression

Assumptions

  • Tools used are flexible
  • Changes are a given

End Results

  • Better Communication of costs to the stakeholders for the change

Back to top

Topic - Test Planning (this discussion only identified issues that cause problems and identified how to resolve Sketchy requirements)

Issues that need improvement

  • Unknown testing time lines
    • start dates
    • limited test window
  • Not involved early enough in SDLC
  • Sketchy requirements - not well documented *
  • No standard for test plan content
  • Lack of test plan time
  • Changing requirements

How to Improve Sketchy Requirements

  • Approach BA with concern/issue
  • Set up meeting to discuss
  • Try to clarify each requirement
  • Ask for the requirements to be written down
  • Ask about the sign off process
  • Draft traceability matrix mapping requirements to design to test - present to development and clients
  • Draw a picture: logic flow diagram in visio to explain your understanding


"HOT SEAT"

Topic - Test Reports - What are they?  What are they for?

  • Identifies defects not fixed and the amount of defects.
  • Goes to Key stakeholders
  • Identifies the number of test cases planned to execute - how many did get executed and how many did not
  • Reason for not executing test cases
  • Identifies outstanding defects and asks what the resolution is.
  • Explains the reason for deviating from the plan.
  • It is a formal document.
  • Justification to identify how the plan was followed and if you deviated from the plan.

Back to top

Post-Conference: Agile Panel Discussion | Better Test Planning Solutions Workshop | Risk Management Workshop
Building Effective Measurement Solutions Workshop | Challenges of Test Automation Solutions Workshop



Quality Engineered Software & Testing (QUEST) Conference - Copyright © 2008
www.qaiquest.org