Support testing with different Tempest versions including custom
In web UI, provide a drop-down box allowing users to select the release of OpenStack for certification test:
- Havena
- IceHouse (when refstack support it in future)
- Custom
For non-custom options, the code will use the corresponding pre-defined Tempest URL.
For custom, allow users to enter their own Tempest URL on the web UI.
Note: The custom option is for vendor's own testing and not for certification purpose.
Blueprint information
- Status:
- Complete
- Approver:
- davidlenwell
- Priority:
- Undefined
- Drafter:
- Raymond Wong
- Direction:
- Approved
- Assignee:
- Raymond Wong
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Catherine Diep
Whiteboard
All generated test documents, logs and UIs need to specify either the code branch (stable/Havana, stable/juno, Master, custom, etc) and the commit ID associated with the tests that have been selected to be run. The commit ID provides very accurate version, while the name provides a user friendly approximation of the version.
A question still to be answered is whether/when tag information should also be provided. specifically, the tags that identify the "maintenance releases" of stable branches.
-------
The current model has the github url (which has the branch information) from where we download the tempest code.
We also have the timestamp of when the test is executed.
With the two piece of information, I think we can uniquely identify the tempest code.
-- Raymond Wong 3/31/14
