planitest
What is it?
Test helpers for Ops Manager tile developers. Given the set of tile options selected by the operator, what should the generated BOSH manifest look like?
It can be prohibitively expensive to deploy your tile in each of these configurations - planitest lets you make assertions about the staged manifest.
Usage
See the tested example
What do you need?
There are two ways to run planitest, using a real Ops Manager as backend
renderer or using a generator tool to provide faster feedback.
Use om
as renderer
- Set environment variable
RENDERER
to om
- An Ops Manager instance to test against. It should have the BOSH tile deployed.
- The om CLI, n.b. requires
om
0.42.0+
- The bosh CLI
- A config file usable by
om configure-product
, see om
documentation
- The tile you want to test. It should be already uploaded to Ops Manager, along with the stemcell it depends on.
Rough Edges for om
:
- Don't attempt to run tests in parallel as different examples will step on each other
- It runs om with the
--skip-ssl-validation
flag
- Rendering a staged manifest for a large product on Ops Manager can be slooooow
Use ops-manifest
as renderer
- Set environment variable
RENDERER
to ops-manifest
- The ops-manifest CLI
- The metadata.yml file extracted from a tile
- A configuration file exported with
om staged-config
Rough edges for ops-manifest
:
ops-manifest
is also under heavy construction; it may render differently from an Ops Manager
- Config file may be hard to configure. It requires appropriate
product-properties
and network-properties
fields.