Functional test on US level (API, UI, XBRL and reporting) - NextensArelB/SwaggerGenerationTool GitHub Wiki

##Objective To validate that each User Story delivered performs as designed and described in the requirements and acceptance criteria, this could be from API, UI, XBRL and reporting perspective. Do not test only the happy flow, test unhappy flow as well, including hidden fields, deleted fields/objects. See test checklist with the different topics, make your own local copy and add/delete what is applicable.

##Scope UI

  • Test of layout
  • Test of calculations
  • Test of boundary's
  • Test of validations and error/warning/information handling
  • Test of input/output
  • Test of spelling
  • Test of consistency between UI (fieldnames, font types, etc)
  • Test of interactive elements, such as buttons, hovers, etc

API

  • Test of all paths and conditions
  • Test of boundary's
  • Test of validations and error/warning/information handling
  • Test of input/output

XBRL, see link for additional information on testing XBRL

  • Test of all paths and conditions
  • Test of boundary's
  • Test of validations and error/warning/information handling
  • Test that not applicable fields are not in XBRL (e.g. hidden fields)
  • Test of input/output

Reporting

  • Test of all paths and conditions
  • Test of boundary's
  • Test of input/output

These tests could be applicable for automation:

  • Discuss with the dev and compare functional tests with unit test to determine if unit tests are complete in coverage, if not these needs to be added
  • Determine which API tests (if applicable) should be automated
  • Determine which UI tests (if applicable) should be automated

##Who

  • QA

##When When the User Story is delivered in dev environment

##Techniques

  • Boundary value analysis
  • Process cyclus test
  • CRUD
  • Syntactic test
  • Decision table

See more information on the activities.

⚠️ **GitHub.com Fallback** ⚠️