# Web IDE
The CloudWright Web IDE is the in-browser editor where you build your application. The Web IDE provides live testing, autocomplete, and documentation to make it easy to quickly develop and test applications.
This section highlights the features of the in-browser editor.
CloudWright provides built-in autocompletion for most Modules while using the web editor. When available, fields, methods, and signatures will be displayed:
# In-editor docs
Every CloudWright module ships with examples and links to more complete documentation, available via hyperlink on the module import:
If other Applications on your teams use the selected Module template, the info boxes will link to those applications for concrete usage examples.
# Dry runs
While editing an application, you can at any time test your draft code by performing a dry run against manually specified inputs. To launch a dry run, provide inputs in the 'Input' form in the lower-left panel, and click the blue 'Run' arrow:
Dry runs default to a 10-second time-out. This is configurable by accessing the advanced run settings (the grey cog icon). Dry runs are always run against the latest successful image build, and are not saved to the application history.
Sometimes while building an application, you will want to use a module which has side-effects you do not want to trigger repeatedly or from a development context.
CloudWright.mock is a generic method which can wrap a module and tell you which methods on the module would have been called during a real run.
For example, if we are writing an application which emails customers when their files are ready, but we do not want to send emails while testing, we can mock our company's email module:
After performing a dry run, we can view 'mocked' method calls in the lower-right 'Calls' panel. Here, we can see that we would have sent one email to