Tasks

All the tasks of the course in one place, by module. Each one leads to the lesson that explains what you need.

Tasks from the lessons

Welcome

• Why programs fail: Name the principle
• What quality is: Customer complaints

Requirements

• Who has a say: Who will you ask?
• How requirements are elicited: What do you ask?
• Kinds of requirements: From the goal to the screen
• The good requirement: Promo codes · Delivery · Returns
• When a table is clearer: The missing transition
• When a table is clearer: Fill in the table

Stories and acceptance criteria

• What a story is: Which story states the need?
• The good story: INVEST: Fix the story
• Splitting a big story: The final total · The promo codes
• Acceptance criteria: From the need to acceptance · The missing example
• Example Mapping: rules, examples, questions: The discounts · The return

Scenarios in Gherkin

• Given, When, Then: Exactly 50 € · Three cases
• Scenario Outline and Examples: From copies to an outline
• Scenario Outline and Examples: Two rules
• What, not how: Without the buttons
• What, not how: Two in one
• Bad scenarios: The cart
• Bad scenarios: Then an order of 50 €
• Living documentation

Traceability

• The traceability matrix: Delivery and the cart
• When a requirement changes: The free delivery threshold
• What coverage does not tell you: What to add

Static testing

• Why early: The path of the defect
• Kinds of review: Which question catches it?
• Reviewing a specification: The decision

Test design techniques

• Equivalence partitions: The cart limit
• Boundary values: The cart limit · Days and counts
• Decision tables: What does the table say?
• State transitions: All transitions and the invalid ones
• Pairwise testing: The broken table
• Code coverage: Two conditions, one decision
• Testing from experience: Negative, and what stays

Levels, types and process

• Test levels: Which level catches the bug?
• Test types: Is it maintenance testing?
• Testing in the life cycle: Which quadrant?
• The plan and risk-based testing: Order by risk
• Defects and the defect report: The delivery fee · The eleventh item · The refusal that empties

Non-functional

• Usability and accessibility: Checkout
• Performance and load: Black Friday
• Security as a requirement: The orders

Automation

• Why and what to automate: What first and why
• From scenario to steps: Changes and traps
• Component tests: Which test protects what
• API and user interface: API, UI or further down
• Tests in CI: Causes and fixes

Validating with the client

• Acceptance testing with the business: The plan
• Measuring after the release: How you read the numbers

Project: promo codes

• Promo codes: from the request to the release: The split · The validity period
• Promo codes: from the request to the release
• Promo codes: from the request to the release: The scenarios · The technical cases
• Promo codes: from the request to the release: The report
• Promo codes: from the request to the release: Coverage and impact