An automatic test framework for graphical interface of Installanywhere installer based on JUnit

Introduction to JUnit

JUnit is an open source unit testing framework for writing and running automated tests, developed by Erich Gamma and Kent Beck in 1997. It includes the following features:

The API provided allows you to write out a reusable unit test case with a clear test result;

Provides three ways to display your test results, and can also be extended;

The function of unit test cases running in batches is provided.

Super lightweight and simple to use, no commercial deception and useless wizards;

The whole frame is well designed and easy to expand.

Installanywhere Introduction

Installanywhere (IA) is a multiplatform installer development tool that can be used to install software on any platform, such as a desktop system, enterprise, or multimodal WEB service, and configure these applications to achieve optimal performance. It includes the following features:

Support multi-platform and multi-language, can deploy software on any client or server platform;

Integrated development environment simplifies installation, development and creation;

Support Customization and optimization of installation program;

Simplify and standardize software deployment, reducing the cost of testing and support.

Because of the characteristics of the installer itself, it is always difficult to test it automatically. For IA's predecessor, InstallShield, there has been no good way to apply JUnit to automated tests for setup. IA provides a framework that allows us to apply JUnit to automate the setup process and leave us with the possibility of extending it. This article will be the analysis of it.

Installanywhere installation program graphical interface automatic test frame structure

Automated testing of graphical interface programs based on SWING/AWT has been a challenge for developers because:

The complexity of the underlying graphics framework.

The complexity caused by the combination of the applied business logic and the graphical interface.

Lack of intuitive automated test frameworks.

Automatic testing of the Installer interface based on Installanywhere development also faces these problems. The first two cases have always existed, this article focuses on the third case. Designing an automatic test framework for the Installer interface needs to address the following issues: