KFS QA Page Original Version

Each stakeholder has test objectives and expectations which they want done effectively, efficiently, and elegantly

• We need to work with stakeholders to articulate and define these objectives and expectations
  • Effectiveness: satisfying objectives and expectations.
  • Efficiency: maximizes value delivered for resources invested.
  • Elegance: achieving effectiveness and efficiency in a graceful, well-executed fashion.
    Unknown macro: {float}

    www.rbcs-us.com

Quality begins in the Team - not the application!

• Follow others lead (Let's not reinvent the wheel)
• Apply previous experience
• Lay the foundation
  • Keep it simple initially, add complexity where it is needed
  • Identify Roles and Responsibilities
  • Common tools and repositories
  • Identify and document processes
  • Start with targeted manual testing, prioritize automation
• Identify risks, determine the execution order of the test cases
• Communications

QA - Seven Step Process Plan

1. Initiation - what are your goals?
2. Planning - asking the right questions.
3. Discovery - build a case.
4. Development - construction phase.
5. Execution - running test case(s).
6. Analysis - did we meet our goals?
7. Closeout

KFS QA Tools

• JIRA for Manual Test Management
• JIRA for Defect Tracking
• CaptureFox Firefox add-on for recoding AVI files of scenarios.
• Cornell DropBox for sending AVI files.
• TestExplorer for converting AVI files into test cases.
• iMacros Firefox add-on for "light" automation, validation and testing.
• IBM Rational Performance Tester (Load Testing)
• HP Quality Center (Business Process Testing)