Age | Commit message (Collapse) | Author |
|
* Activate the correlation correctness tests
* Print out whitespace characters in such a form that allows visual
comparison of differences to help with fixing issues caught by
tests.
|
|
|
|
* test/requests/test-website.py: allow the correlation correctness
tests to run on CI.
|
|
* test/requests/correlation_tests.py: Add proof-of-concept code to run
the checks for correctness.
* test/requests/test-website.py: Add a way to manually run the tests
from the CLI
|
|
|
|
|
|
|
|
|
|
Sometimes the tests might be run before the service has began
running. This commit delays the running of the tests for a while.
|
|
|
|
* test/requests/test-website.py: Run "black test/requests/test
test-website.py".
|
|
* test/requests/test-website.py: Delete parser option "-i" for running
integration tests.
(integration_tests): Delete it.
(integration_suite): Ditto.
(run_integration_tests): Ditto.
* test/requests/test_registration.py: Delete it.
|
|
* test/requests/test-website: These imports were deleted in an earlier
PR here: <https://github.com/genenetwork/genenetwork2/pull/574>
|
|
* test/requests/test-website.py: Delete "from wqflask import
app". This has the undesired effect of starting an instance of
Genenetwork2.
|
|
|
|
See: <https://docs.python.org/2/library/2to3.html#2to3fixer-future>
|
|
* test/requests/link_checker.py (check_packaged_js_files): Add it.
* test/requests/test-website.py: Use above method.
|
|
|
|
* Remove the run-integration-tests.py, and use the test-website.py as
the entry point for all tests. This simplifies running the tests for
the site.
|
|
testing
* Fix conflicts
|
|
|
|
* Add mapping tests, and build the first of the tests.
|
|
|
|
* Use argparse to handle commandline arguments.
* Create initial layout of how the code might end up - lots of the code
is currently commented out.
|
|
|
|
* Navigation depends on Javascript to render the elements being tested.
That would require selenium and its ilk to run such tests, meaning
such packages would need to be defined for Guix first.
|
|
* Start working on navigation tests.
|
|
* Add mapping tests, and build the first of the tests.
|
|
|
|
* Use argparse to handle commandline arguments.
* Create initial layout of how the code might end up - lots of the code
is currently commented out.
|
|
|