Skip to content

Commit 29b74ea

Browse files
committed
Change the source to make e8baa1e permanent
1 parent fb59370 commit 29b74ea

File tree

7 files changed

+9
-10
lines changed

7 files changed

+9
-10
lines changed

_sources/development.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -123,10 +123,10 @@ Regression tests
123123

124124
Regression tests ensure that bugs, once fixed, stay fixed. These are real-life files that at some point broke a cclib parser, and are stored in folders like ``data/regression/Jaguar/Jaguar6.4``. The files associated with regression tests are not stored stored together with the source code as they are often quite large. A separate repository on github, `cclib-data`_, is used to track these files, and we do not distribute them with any releases.
125125

126-
For every bug found in the parsers, there should be a corresponding regression test that tests this bug stays fixed. The process is automated by `regression.py`_, which runs through all of our test data, both the basic data and regression files, opens them, tries to parse, and runs any relevant regression tests defined for that file. New regression tests are added by creating a function ``testMyFileName_out`` according to the examples at the start of `regression.py`_.
126+
For every bug found in the parsers, there should be a corresponding regression test that tests this bug stays fixed. The process is automated by `run_regressions.py`_, which runs through all of our test data, both the basic data and regression files, opens them, tries to parse, and runs any relevant regression tests defined for that file. New regression tests are added by creating a function ``testMyFileName_out`` according to the examples at the start of `run_regressions.py`_.
127127

128128
.. _`cclib-data`: https://github.com/cclib/cclib-data
129-
.. _`regression.py`: https://github.com/cclib/cclib/blob/master/test/regression.py
129+
.. _`run_regressions.py`: https://github.com/cclib/cclib/blob/master/test/run_regressions.py
130130

131131
Doctests
132132
~~~~~~~~~

_sources/tutorial.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ What next?
102102

103103
* Read the list and specifications of the `parsed data`_ and related `data notes`_
104104
* Test the program using the test data files included in the full source distribution
105-
* Run the unit and regression tests in the test directory (``testall.py`` and ``regression.py``)
105+
* Run the unit and regression tests in the test directory (``testall.py`` and ``run_regressions.py``)
106106
* Send any questions to the cclib-users mailing list at https://lists.sourceforge.net/lists/listinfo/cclib-users.
107107
* Write some computational chemistry algorithms using information parsed from cclib and donate the code to the project
108108

development.html

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -336,5 +336,4 @@ <h2>Developers<a class="headerlink" href="#developers" title="Permalink to this
336336

337337

338338
</body>
339-
</html>
340-
339+
</html>

searchindex.js

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

sphinx/development.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -123,10 +123,10 @@ Regression tests
123123

124124
Regression tests ensure that bugs, once fixed, stay fixed. These are real-life files that at some point broke a cclib parser, and are stored in folders like ``data/regression/Jaguar/Jaguar6.4``. The files associated with regression tests are not stored stored together with the source code as they are often quite large. A separate repository on github, `cclib-data`_, is used to track these files, and we do not distribute them with any releases.
125125

126-
For every bug found in the parsers, there should be a corresponding regression test that tests this bug stays fixed. The process is automated by `regression.py`_, which runs through all of our test data, both the basic data and regression files, opens them, tries to parse, and runs any relevant regression tests defined for that file. New regression tests are added by creating a function ``testMyFileName_out`` according to the examples at the start of `regression.py`_.
126+
For every bug found in the parsers, there should be a corresponding regression test that tests this bug stays fixed. The process is automated by `run_regressions.py`_, which runs through all of our test data, both the basic data and regression files, opens them, tries to parse, and runs any relevant regression tests defined for that file. New regression tests are added by creating a function ``testMyFileName_out`` according to the examples at the start of `run_regressions.py`_.
127127

128128
.. _`cclib-data`: https://github.com/cclib/cclib-data
129-
.. _`regression.py`: https://github.com/cclib/cclib/blob/master/test/regression.py
129+
.. _`run_regressions.py`: https://github.com/cclib/cclib/blob/master/test/run_regressions.py
130130

131131
Doctests
132132
~~~~~~~~~

sphinx/tutorial.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ What next?
102102
103103
* Read the list and specifications of the `parsed data`_ and related `data notes`_
104104
* Test the program using the test data files included in the full source distribution
105-
* Run the unit and regression tests in the test directory (``testall.py`` and ``regression.py``)
105+
* Run the unit and regression tests in the test directory (``testall.py`` and ``run_regressions.py``)
106106
* Send any questions to the cclib-users mailing list at https://lists.sourceforge.net/lists/listinfo/cclib-users.
107107
* Write some computational chemistry algorithms using information parsed from cclib and donate the code to the project
108108

tutorial.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -300,4 +300,4 @@ <h2>What next?<a class="headerlink" href="#what-next" title="Permalink to this h
300300

301301

302302
</body>
303-
</html>
303+
</html>

0 commit comments

Comments
 (0)