Align CTI to PTI
When we talk about the PTI, we tend to say "PTI". In fact, the original filename is "reference/project-testing-interface.rst". However, the pre-language files use the cti acronym, as do all of the title lines. Let's align with the acronym people use when discussing the concept. Also, remove the suffix from the language files - they're in a directory called "pti" already, they don't need a _pti suffix. Change-Id: I53bc82eb2cb2125d7446a5f7d0be622118553732
This commit is contained in:
parent
708f496ccf
commit
41c529c602
|
@ -95,7 +95,7 @@ Current State / Anticipated Impact
|
|||
|
||||
Python 3.5 will be available in all of the long-term-support versions
|
||||
of the operating systems on which we support deployment, and is listed
|
||||
as part of our Python testing interface (:ref:`cti-python`).
|
||||
as part of our Project Testing Interface for Python (:ref:`pti-python`).
|
||||
|
||||
Our CI infrastructure supports Python 3.
|
||||
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
============================
|
||||
Consistent Testing Interface
|
||||
============================
|
||||
=========================
|
||||
Project Testing Interface
|
||||
=========================
|
||||
|
||||
OpenStack has a lot of projects. For each project, the OpenStack CI system
|
||||
needs to be able to perform a lot of tasks. If each project has a slightly
|
||||
|
@ -61,4 +61,4 @@ tests might have to be skipped on these distributions.
|
|||
:maxdepth: 1
|
||||
:glob:
|
||||
|
||||
cti/*
|
||||
pti/*
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
================================
|
||||
Consistent Testing Interface: Go
|
||||
================================
|
||||
=============================
|
||||
Project Testing Interface: Go
|
||||
=============================
|
||||
|
||||
Go language (golang) repositories shall use the following interface
|
||||
for testing and automation purposes. This includes both pure golang
|
|
@ -1,8 +1,8 @@
|
|||
========================================
|
||||
Consistent Testing Interface: JavaScript
|
||||
========================================
|
||||
=====================================
|
||||
Project Testing Interface: JavaScript
|
||||
=====================================
|
||||
|
||||
This document outlines common ways to meet the Consistent Testing Interface
|
||||
This document outlines common ways to meet the Project Testing Interface
|
||||
requirements for JavaScript. Each JavaScript project must be able to do:
|
||||
|
||||
- Codestyle checks.
|
||||
|
@ -145,4 +145,4 @@ output should be placed in the :code:`publish-docs` directory.
|
|||
|
||||
.. _NPM package scripts: https://docs.npmjs.com/misc/scripts
|
||||
.. _ESLint: http://eslint.org
|
||||
.. _eslint-config-openstack: http://git.openstack.org/cgit/openstack/eslint-config-openstack
|
||||
.. _eslint-config-openstack: http://git.openstack.org/cgit/openstack/eslint-config-openstack
|
|
@ -1,8 +1,8 @@
|
|||
.. _cti-python:
|
||||
.. _pti-python:
|
||||
|
||||
====================================
|
||||
Consistent Testing Interface: Python
|
||||
====================================
|
||||
=================================
|
||||
Project Testing Interface: Python
|
||||
=================================
|
||||
|
||||
Each python project must be able to do:
|
||||
|
Loading…
Reference in New Issue