xod
xod copied to clipboard
As a CLI user I want to compile tabtests in the cloud
Rationale
There’s currently no way to run tabtest from xodc
without gcc
and make
. Also, it's useful for the integration tests.
Usage
USAGE
$ xodc tabtest [options] [entrypoint]
ARGUMENTS
ENTRYPOINT
Project and/or patch to operate on. The project should point to a file or
directory on the file system. The patch may either point to file system or
be a XOD patch path. If either is omitted, it is inferred from the current
working directory or another argument. Examples:
* ./path/to/proj.xodball main # xodball + patch name
* ./path/to/proj/main/patch.xodp # just full path to a patch
* main # a patch in the current project
OPTIONS
-V, --version show CLI version
-h, --help show CLI help
-o, --output-dir=path [default: /tmp/xod-tabtest] path to directory where to save tabtest data
-q, --quiet do not log messages other than errors
-w, --workspace=path [default: ~/xod] use the workspace specified, defaults to $HOME/xod
--no-build do not build
--cloud compile in the cloud
--anonymous when compile in the cloud do it anonymously
--api=hostname [default: xod.io] XOD API hostname
--on-behalf=username publish on behalf of the username
--password=password XOD API password
--username=username XOD API username
EXAMPLES
Build tabtests for project in current working directory
$ xodc tabtest
Specify target directory and project, only generate tests
$ xodc tabtest --no-build --output-dir=/tmp/xod-tabtest ./workspace/__lib__/xod/net
Run tabtests for project in current working directory using XOD cloud
$ xodc tabtest --cloud --anonymous
Acceptance criteria
- [ ] I can run all tabtests with exactly same bahaviour without installed dev tools
- [ ]
xodc
exits with non-zero code if a library can’t be installed - [ ] Compilation limits exhausted error is handled gracefully
- [ ] Wrong credentials is nadled gracefully
- [ ] Network problem is handled gracefully