Action Point Dashboard
  • Action Point Dashboard Documentation
  • INTRODUCTION
    • Glossary / Terminology
    • FAQ
    • Releases / Changelog*
    • Report an Issue / Contact us
  • PRODUCT / END-USER DOCUMENTATION
    • Overview
      • Objectives
      • User roles and permissions
    • Action Points Dashboard Navigation
    • Overall User Interface
    • List of Action Points
    • Action Points Workflow
    • Action Points
      • Creation of Action Point
      • Modification of Action Point
      • Completion of Action Point
      • Additional options for Action Point
    • Connections to other modules
      • Overview
      • Action Points in FAM
      • Action Points in Field Monitoring
      • Action Points in TPM
      • Action Points in Trip Management (T2F)
  • TECHNICAL DOCUMENTATION
    • Architecture
    • Development Setup
    • Deployment / DevOps
    • Data Model
    • Fixtures & management commands
    • API Documentation
      • Error Handling
    • Backend module structure
    • Integration with permissions framework
    • Frontend
      • Module structure
      • Build process
      • Tests
Powered by GitBook
On this page
  • Run tests
  • Tests architecture
  1. TECHNICAL DOCUMENTATION
  2. Frontend

Tests

Run tests

To run the tests you can use this command:

gulp test

It will build all source files including tests and run Web Component Tester.

Tests architecture

All test files will have .spec postfix extention. For instance permission-controller.spec.html . Test files are placed in elements src directories.

Entry point file index.spec.html for tests is located in application_root/src/tests directory. It has only one single line for tests loading :

WCT.loadSuites([<!--testSources-->]);

<!--testSources--> comment will be replaced with resolved tests pathes during build process.

PreviousBuild process

Last updated 6 years ago