• PRODUCT

    PRODUCT

  • PRICING
    PRICING

  • HELP
    HELP

  • BLOG
    BLOG

  • APPSTORE
    APPSTORE

  • COMPANY
    COMPANY

  • LEGAL
    LEGAL

  • LOGIN
    LOGIN

  • End To End Testing


  • This article describes the end to end testing scenarios supported by the framework.


  • The recommended method for E2E testing is to clone a test app and superimposing it as a trigger to run alongside your app for testing purposes.

    Issues to bear in mind when testing

    • The testing package and its dependencies should not leak into the app being tested.
    • The on-demand IDE should allow access to the tests and the main app

    Example

    Suppose you have just created a browser extension by cloning the izywaretoolbar. The following flows are the ones that need to be verfied for E2E testing:
    1. Initial activation
    * When not logged in, it should ask that they log-in

    * If they they have an account they will log-in

    * If they dont have an account they can create one

    * If they have an account but forgot the password, they should be able to reset it

    * After loggig in, it should show the success message
    1. Post activation behavior
    Load the contentscript and popup* if appropriate

    Communicate with the router and processor*

    Implementation

    The testing engine will work by establishing itself as the root frame for the app, and thus it can intercept and simulate browser and the extension systems functionality:

    ['session_clear'],

    ['frame_navigate', 'izywaretoolbar/register/embedded'],

    ['test_verify', 'message', 'You must login to continue'],

    ....


  • Izyware Help Articles
    Izyware Help Articles