cargo ux e2e

This is a Draft Version

Builds and serves an Angular Rust app, then runs end-to-end tests using Protractor.

cargo ux e2e <project> [options]
cargo ux e <project> [options]


Must be executed from within a workspace directory. When a project name is not supplied, it will execute for all projects.


ArgumentDescriptionValue Type
projectThe name of the project to build. Can be an application or a library.string


OptionDescriptionValue TypeDefault Value
--base-urlBase URL for protractor to connect to.string
--configurationOne or more named builder configurations as a comma-separated list as specified in the "configurations" section of ux.yaml. The builder uses the named configurations to run the given target. For more information, see Setting this explicitly overrides the "--prod" flag. Aliases: -cstring
--dev-server-targetA dev-server builder target to run tests against in the format of project:target[:configuration]. You can also pass in more than one configuration name as a comma-separated list. Example: project:target:production,staging.string
--grepExecute specs whose names match the pattern, which is internally compiled to a RegExp.string
--helpShows a help message for this command in the console.true|false|jsonfalse
--hostHost to listen on.string
--invert-grepInvert the selection specified by the 'grep' option.boolean
--portThe port to use to serve the application.number
--prodShorthand for "--configuration=production". Set the build configuration to the production target. By default, the production target is set up in the workspace configuration such that all builds make use of bundling, limited tree-shaking, and also limited dead code elimination.boolean
--protractor-configThe name of the Protractor configuration file.string
--specsOverride specs in the protractor config.array
--suiteOverride suite in the protractor config.string
--webdriver-updateTry to update webdriver.booleantrue