E2E test - NextensArelB/SwaggerGenerationTool GitHub Wiki

Objective

To validate from an end-user perspective that the application is accessible and the user can perform the main (pre-defined) user workflows from beginning till the end. The E2E test has not the objective to validate calculations or to perform functional testing of the UI itself, as these tests should be covered by the Unit/Component test, API tests or UI tests.

##Scope

  • Test on a (group of) features
  • Test of the main user workflows, to be defined with a group of stakeholders, see also Personas concept
  • CRUD
  • Test is done via the UI

##Who

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

##When

  • After manual testing of a (group of) features
  • With every new release

##What See if you can create an scenario based test script that is as complete as possible. At least the main scenario's for the application sould be identified and automated.

##Tool

  • Karate

##How By implementing checks on:

  • Screen contents for elements that change when a user makes an selection
  • The (work)flow of the application by using the application how the user would do it
  • Other behavioral aspects that are implemented using code

##Measures

  • % of workflows in test
  • % of main workflows in test
  • % of workflows completed without issues

##External resources

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