Update URL from "http" to "https"
Most of them can still be visited through http, but the following one is necessary to update, so I change them all by this chance. $ git clone http://git.openstack.org/openstack/tempest Change-Id: I2b4da0670b599666e7151bddfff0fa6655640bc4
This commit is contained in:
parent
7c8dd48f75
commit
ac670dce6d
@ -84,7 +84,7 @@ For example ``self.assertIn`` can include the whole set.
|
||||
It is recommended to use testtools `matcher`_ for the more tricky assertions.
|
||||
You can implement your own specific `matcher`_ as well.
|
||||
|
||||
.. _matcher: http://testtools.readthedocs.org/en/latest/for-test-authors.html#matchers
|
||||
.. _matcher: https://testtools.readthedocs.org/en/latest/for-test-authors.html#matchers
|
||||
|
||||
If the test case fails you can see the related logs and the information
|
||||
carried by the exception (exception class, backtrack and exception info).
|
||||
@ -178,7 +178,7 @@ negative testing should be handled with project function tests.
|
||||
All negative tests should be based on `API-WG guideline`_ . Such negative
|
||||
tests can block any changes from accurate failure code to invalid one.
|
||||
|
||||
.. _API-WG guideline: http://specs.openstack.org/openstack/api-wg/guidelines/http.html#failure-code-clarifications
|
||||
.. _API-WG guideline: https://specs.openstack.org/openstack/api-wg/guidelines/http.html#failure-code-clarifications
|
||||
|
||||
If facing some gray area which is not clarified on the above guideline, propose
|
||||
a new guideline to the API-WG. With a proposal to the API-WG we will be able to
|
||||
|
@ -2,7 +2,7 @@
|
||||
Team and repository tags
|
||||
========================
|
||||
|
||||
.. image:: http://governance.openstack.org/badges/tempest.svg
|
||||
.. image:: https://governance.openstack.org/badges/tempest.svg
|
||||
:target: https://governance.openstack.org/tc/reference/tags/index.html
|
||||
|
||||
.. Change things from this point on
|
||||
@ -61,7 +61,7 @@ as it is simpler, and quicker to work with.
|
||||
#. You first need to install Tempest. This is done with pip after you check out
|
||||
the Tempest repo::
|
||||
|
||||
$ git clone http://git.openstack.org/openstack/tempest
|
||||
$ git clone https://git.openstack.org/openstack/tempest
|
||||
$ pip install tempest/
|
||||
|
||||
This can be done within a venv, but the assumption for this guide is that
|
||||
@ -133,7 +133,7 @@ For more details refer to the library documentation here: :ref:`library`
|
||||
|
||||
Release Versioning
|
||||
------------------
|
||||
`Tempest Release Notes <http://docs.openstack.org/releasenotes/tempest>`_
|
||||
`Tempest Release Notes <https://docs.openstack.org/releasenotes/tempest>`_
|
||||
shows what changes have been released on each version.
|
||||
|
||||
Tempest's released versions are broken into 2 sets of information. Depending on
|
||||
|
@ -2,7 +2,7 @@ Reviewing Tempest Code
|
||||
======================
|
||||
|
||||
To start read the `OpenStack Common Review Checklist
|
||||
<http://docs.openstack.org/infra/manual/developers.html#peer-review>`_
|
||||
<https://docs.openstack.org/infra/manual/developers.html#peer-review>`_
|
||||
|
||||
|
||||
Ensuring code is executed
|
||||
@ -16,7 +16,7 @@ not be accepted.
|
||||
If a new test is added that depends on a new config option (like a feature
|
||||
flag), the commit message must reference a change in DevStack or DevStack-Gate
|
||||
that enables the execution of this newly introduced test. This reference could
|
||||
either be a `Cross-Repository Dependency <http://docs.openstack.org/infra/
|
||||
either be a `Cross-Repository Dependency <https://docs.openstack.org/infra/
|
||||
manual/developers.html#cross-repository-dependencies>`_ or a simple link
|
||||
to a Gerrit review.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user