One command, tdd, in front of every Tabsdata developer tool, each tool in its own isolated
environment, so that tool dependencies never touch a project's dependencies.
It holds the developer tools of tabsdata: setup, build
and test (tdd). Among them is the tool that creates the databases and storage the tests of
tabsdata run against.
Python tools live in per-toolset virtual environments, and tdd dispatches each command into its own. Shell commands, the ones that must change your shell, like entering a virtual environment, are functions loaded into it. Nothing is installed globally, and nothing has to be active.
The tdd tool is meant to be used together with
tabsdata, checked out side by side. Clone this
repository into a folder named tabsdata-dt, and install tdd as steps 2 and 4 of
Developing Tabsdata
describe.
List every command:
tdd --helpThe smoke-test scripts run tabsdata end to end: a fresh virtual environment, tabsdata,
tdkserver and the XP test suites. The script for km runs on every platform, while the scripts for eks, gke
and aks run against a cloud Kubernetes cluster from macOS or Linux.
List the scripts, with what each one does:
tdd smoke listShow how to run the km script:
tdd smoke run --script km --helpExport the scripts, to read and edit your own copies.
macOS and Linux:
tdd smoke export-scripts --dir ~/smokeWindows:
tdd smoke export-scripts --dir $HOME\smokeThe tdd apidoc command reads the public API of tabsdata statically, and writes it as one structured JSON document. Tabsdata DevTools: API Description explains the format. Run it in a virtual environment that has tabsdata installed:
tdd apidoc generate --out api.jsonDeveloping Tabsdata DevTools covers the tasks, the tests and how to add a command.
Licensed under the Apache License, Version 2.0.