PRICING

HELP

BLOG

APPSTORE

COMPANY

LEGAL

LOGIN

AI Assisted Content Management System

Analytics & Lead Generation

Automation Projects

Browser Extension Apps

Dashboard Theme Analysis: LN1

Data Exchange Automation Tools

Getting Started With Building Hybrid Apps

Izyware Hybrid UX Design Guidelines

Onboarding New Organizations Using Izyware

Quick Visualization and Monitoring

Unified Metrics Stream Pipeline

Legacy Features and Backward Compatibility

How does the legacy frame architecture work

Izyware Legacy UI Circus Engine

Case Studies and Knowledge Center

Angular and React Embedding Guide

Build and deploy a content distribution app in less than five minutes: Part II

Comparison of CSS Preprocessors SASS vs LESS vs STYLUS

Comparison of node.js test frameworks and utilities: lab, chai, sinon

Manage and automate your day to day business tools using IzyCloud Tasks: Part I

MySql Performance Optimization

Onboarding Tutorial: Creating & publishing an app

Rebranding and Customizing Websites

Using IzyCloud on Android: IzyCloud Query App

Technical Resources

.NET SDKCore IzyWare

av-stream README

ElasticSearch IzyWare Data Console Feature

End To End Testing

End To End Testing, Part II

frames and nav (ui/w/shell/navmulti) README

izy-circus README

izy-idman-tools README

izy-pop3 README

izy-proxy README

izy-sync README

IzyIDE README

izymodtask readme

IzyShell readme

ReKey Feature Package README for IzyWare SQL Console

Single Sign-On (SSO) README

Tasks Migration : V5 guidelines

Users & Groups README

V5 Migration : apps/pulse guidelines README

Container Orchestration

Izy Kubernetes Internal Networking Troubleshooting

Application Hosting

Content Publisher

Domain Registration

Email Hosting

Izyware Browser Extension

Izyware Deployment Engine

Izyware Session Management

Messaging System APIs and functionality

Single SignOn

Integration APIs

iOS SDK

Azure and .NET

izy-devops

<< ElasticSearch IzyWare Data Console Feature

End To End Testing, Part II >>

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'],

....