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

<< End To End Testing

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

End To End Testing, Part II

In part two of the series, we will discuss guidelines for structuring and organizing your tests.

Goals

In modern cloud services environments software components tend to be consumed in a variety of different ways:

• static library
• packaged static component
• rpc
• as a service

accordingly, the testing associated with components would have to cover all of above, albiet the underlying functionality might be the same.

Izy platform recommends adhering to the izy-proxy JSONIO signature for implementing each test component. The advantages would be as follows:

• Ability to launch the test code from service and non service environments
• No need to manage the HTTP metadata and headers
• JSONIO api security context would be inhertied from the parent context, thus making passing authorization and authentization tokens free in the service environments.
• The component would become consumable anywhere in the environment by referecing izy-proxy
• simple string based launch patterns //service/pkg:path?method could be used to reference the component call, making the component launch similar from

* command line shell and scripting environments

* browser sandbox

* network

* ....

Implementation Guidelines

Framework agnostic test logic

Implement the core logic for the test and component by adhering to the JSONIO signature. This will ensure that the tests can be consumed and deployed in the scenarios discussed above.

tie-in test compoments into the test framework

Use tools like test proxy to properly launch and tie in the tests in the test framework.

Continious Integration (optional)

Enterprise customers can use continous cloud testing by using the Izyware dashboard advanced features. Please contact us for more information regarding using this feature.

test proxy: https://github.com/izyware/izy-proxy

simplified-jsonio-package-launcher-and-invokestring-over-the-api-layer

JSONIO signature: https://github.com/izyware/izy-proxy

simplified-jsonio-package-launcher-and-invokestring-over-the-api-layer