Third Party Monitoring Module
  • Third Party Monitoring Module Documentation
  • INTRODUCTION
    • Glossary / Terminology
    • FAQ
    • Releases / Changelog*
    • Report an Issue / Contact us
  • PRODUCT / END-USER DOCUMENTATION
    • Overview
      • User rights and permissions
    • Third Party Monitoring Module Navigation
    • Overall User Interface
    • Third Party Monitors section
      • List of Third Party Monitors
      • TPM partner details screen
    • List of Visits section
      • List of Visits
      • Visit details
      • Statuses and corresponding actions
        • Draft
        • Assigned
        • TPM Accepted
        • TPM Rejected
        • Cancelled
        • TPM Reported
        • Sent Back to TPM
        • UNICEF Approved
      • Emails notifications flow
    • TPM workflow
  • TECHNICAL DOCUMENTATION
    • Architecture
    • Development Setup
    • Deployment / DevOps
    • Backend Module structure
    • Data Model
    • Fixtures & management commands
    • API Documentation
      • Error Handling
    • Synchronization with VISION
    • Permissions framework
    • FSM Transitions conditions
    • FSM Transitions in view
    • API Metadata
    • Serializer Mixins
    • Model Mixins
    • Tests
    • Attachments
    • Email links & Tokens Authorization
    • 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 the following 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 theapplication_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