UI test - NextensArelB/SwaggerGenerationTool GitHub Wiki

Objective

To validate functionality on the Userinterface. The Userinterface has it's own specific behaviour that is running in the browser and this funcionality could be implemented in Javascript area's that needs to be tested.

##Scope

  • Test on a story level
  • Test of user interaction
  • Test (input)validation of fields
  • The functionality of buttons, navigation, coboboxes, progressive search, breadcrumb etc. when extended from framework widgets
  • Test of data rendering
  • Test specific for supported browsers
  • Test functionality that is specific for UI (for example on a grid: filters, ordering, search when extended from the framework widgets, dynamic fields and dynamic UI)
  • CRUD

##Who

  • Test engineer (depending on the team), review by peer

##When

  • After delivery of the story, and automated in CICD pipeline

##Tools

  • Karate

##How By implementing checks on:

  • Functionality (click, hover, drag etc)
  • Checks on behaviour (validation) of input fields and how errors are presented
  • Check the handling of success and errors
  • All other factors that have been implemented in Javascript that is not tested in unitTests and runs in the browser

Note: only automate aspects which are not tested or could not be tested in a unit test and focus on high prio features or complex UI, selected tests should have an added value.

##Legacy Some UI test are written using the legacy test tools Cypress and Protractor. These products will be phased out and will be re-written using Karate.

##Measures

  • Coverage of browsers / browser versions
  • Time it takes to test (manual / automated)
  • Peer Review
⚠️ **GitHub.com Fallback** ⚠️