Get in Touch

Course Outline

Where requirements originate

  • Traditional Business Analysis
  • Use cases, scenarios, and tests
  • Non-functional requirements
  • Performance
  • Compliance
  • UML in Business Analysis

Introduction to testing

  • Functional tests
  • Regression testing
  • User Acceptance Testing (UAT)
  • Unit tests
  • Usability tests
  • Non-functional tests
  • Performance testing
  • Load testing
  • Stress testing
  • Soak testing

Test or not to test

  • Who decides what to test?
  • The cost of testing irrelevant features
  • Calculating ROI (especially if analysis fails)
  • The role of the Test Manager

The testing process

  • Testing as both a process and a strategy
  • Identifying testing needs
  • Gathering requirements (use cases, user stories)
  • Scoping (selecting and prioritizing scenarios)
  • Designing tests
  • Preparing data
  • Preparing the environment
  • Creating or recording tests
  • Executing the test
  • Analysis and reporting
  • Conclusions and improvements
  • Knowing when to stop

Product owner and tests

  • The customer representative and test priority
  • Prioritizing tests
  • Writing effective stories for UAT
  • Acceptance criteria
  • Group exercise: producing customer requirements, writing stories based on those requirements, and creating tests

The sprint

  • Sprint backlog and test user stories
  • Group exercise: planning a sprint

Concluding a sprint

  • The Scrum review meeting serves as a test

Is Agile and Scrum right for you?

  • Review of the Scrum process
  • Comparison with other methodologies
  • Benefits of pair programming
  • Question and answer session

Requirements

None.

 14 Hours

Testimonials (2)

Related Categories