Application development lifecycle
Dojo provides an end-to-end pipeline for developing web applications. Application authors can quickly create new Dojo applications via the
dojo create app CLI command. Applications can then be built in both development and production modes using the
dojo build app command. The build tool allows for rapid development and iteration by serving the app using a local HTTP server and watching for further changes to project files. Using this mechanism, developers can make changes and see immediate results in a running application.
These commands form part of a modular Dojo CLI toolchain that supports a variety of uses across the development lifecycle. Applications can configure their build pipeline through a
.dojorc configuration file in the project root.
See the Dojo Build reference guide for more information on how to build a variety of applications using Dojo.
Not all errors can be caught through compilers or static type checkers. Features can get written that are syntactically and logically valid, but either don’t anticipate problems at runtime, or do not perform functionality in the intended way. To mitigate this risk, additional testing needs to be performed.
When using the Dojo CLI to scaffold applications, a test runner for the Intern test library is included by default. This allows developers to begin writing test code immediately alongside application functionality.
Intern provides solutions for many testing concerns but may not be sufficient for all testing needs of a project. Dojo also provides a simple testing harness that allows application test code to validate use of the framework and widgets at the VDOM abstraction level. This harness can be used from any test runner such as Intern, Jest, or any others that an application’s testing strategy necessitates.
See the Dojo Testing reference guide reference for more details on how to effectively test Dojo applications.