features

Test scenario's

IMPORTANT:

• A major distinction in every feature is whether the Portal is in TRIGGERED or NON-TRIGGERED mode.
• These distinctions are made within each file.
• A 3rd scenario (currently 'typhoon' only) is EVENT-WITHOUT-TRIGGER (this needs updating)

For IBF-portal user

• Log-in page
  • Use Log in page
• IBF-portal page
  • Use Header section
  • Change own password
  • Use Situational Overview section
  • Use Chat section
  • Use Aggregate section
  • View Area-of-focus summary
  • Use Timeline section
  • Use Admin-level section
  • Use Map section
  • Use Layers section

For Dashboard admin-user

These are actions run from the dev-menu in the dashboard, accessible only to an admin-user.

• Use Dev Menu

For API admin-user

These are actions run from the Swagger UI (/docs).

• Log in
• Create new user
• Change password other user
• Upload mock data
• Update static data

For pipeline (user)

In practice, the pipeline is often time-scheduled and not manually triggered by a user. But nonetheless the processes that follow from this action (such as email) must be described.

• Run pipeline

Automatic (scheduled) processes

• Delete old data

---

Theory

Reference

• The complete definition of the Gherkin syntax: https://cucumber.io/docs/gherkin/reference/
• A comprehensive guide on BDD by Automation Panda:
  • The Gherkin Language
  • Gherkin by example
  • Writing good Gherkin

Tools

• BDD Editor: A 'wizard'-like interface to create feature-files in a browser.
• AssertThat Gherkin editor: An editor, syntax-highlighting and validator in a browser.
• VSCode-extension: Cucumber (Gherkin) Full Support

How to describe features / define scenarios

Features can be added to this folder by:

• Create a .feature-file, named after its title with _ for spaces;
  i.e. Log_in.feature
• Add a reference to the list above at the appropriate actor.