| 2015-11-15 06:01:49 |
Eva Balycheva |
bug |
|
|
added bug |
| 2015-11-15 06:02:54 |
Eva Balycheva |
description |
Currently functional test base class "zaqar.tests.functional.base.FunctionalTestBase" is written to recreate Bootstrap object and to open/close database connections on each execution of setUp(self) method.
Functional test base class "zaqar.tests.functional.base.FunctionalTestBase" can be modified to make these things reusable across all test cases of each particular subclass of it.
I tried it and it makes functional tests execution in non-integration mode up to 4-5x times faster! No problems detected.
I can propose a change
Also:
Functional tests in integration mode can be accelerated too up to 7x times.
As you may see class attribute "server" is not actually reusable. The server is terminated after each test case execution:
see: https://github.com/openstack/zaqar/blob/master/zaqar/tests/functional/base.py#L91
But there's a problem. When I make it reusable, 8 tests out of 219 fail - few tests in "TestPools" and "TestHealth" classes.
These tests must be adapted to make them work with reusable "server" if we want to accelerate functional tests in integration mode. |
Currently functional test base class "zaqar.tests.functional.base.FunctionalTestBase" is written to recreate Bootstrap object and to open/close database connections on each execution of setUp(self) method.
Functional test base class "zaqar.tests.functional.base.FunctionalTestBase" can be modified to make these things reusable across all test cases of each particular subclass of it.
I tried it and it makes functional tests execution in non-integration mode up to 4-5x times faster! No problems detected.
I can propose a change so you can test it yourself.
Also:
Functional tests in integration mode can be accelerated too up to 7x times.
As you may see class attribute "server" is not actually reusable. The server is terminated after each test case execution:
see: https://github.com/openstack/zaqar/blob/master/zaqar/tests/functional/base.py#L91
But there's a problem. When I make it reusable, 8 tests out of 219 fail - few tests in "TestPools" and "TestHealth" classes.
These tests must be adapted to make them work with reusable "server" if we want to accelerate functional tests in integration mode. |
|
| 2015-11-15 06:07:25 |
Eva Balycheva |
zaqar: assignee |
|
Eva Balycheva (ubershy) |
|
| 2015-11-15 06:25:03 |
Eva Balycheva |
summary |
Functional tests can execute 4-5x faster |
Functional tests can execute 4-5x faster (non-integration mode) |
|
| 2015-11-15 06:27:57 |
Eva Balycheva |
description |
Currently functional test base class "zaqar.tests.functional.base.FunctionalTestBase" is written to recreate Bootstrap object and to open/close database connections on each execution of setUp(self) method.
Functional test base class "zaqar.tests.functional.base.FunctionalTestBase" can be modified to make these things reusable across all test cases of each particular subclass of it.
I tried it and it makes functional tests execution in non-integration mode up to 4-5x times faster! No problems detected.
I can propose a change so you can test it yourself.
Also:
Functional tests in integration mode can be accelerated too up to 7x times.
As you may see class attribute "server" is not actually reusable. The server is terminated after each test case execution:
see: https://github.com/openstack/zaqar/blob/master/zaqar/tests/functional/base.py#L91
But there's a problem. When I make it reusable, 8 tests out of 219 fail - few tests in "TestPools" and "TestHealth" classes.
These tests must be adapted to make them work with reusable "server" if we want to accelerate functional tests in integration mode. |
Currently functional test base class "zaqar.tests.functional.base.FunctionalTestBase" is written to recreate Bootstrap object and to open/close database connections on each execution of setUp(self) method.
Functional test base class "zaqar.tests.functional.base.FunctionalTestBase" can be modified to make these things reusable across all test cases of each particular subclass of it.
I tried it and it makes functional tests execution in non-integration mode up to 4-5x times faster! 20 seconds vs 5 seconds. I haven't detected any problems.
I can propose a change so you can test it yourself. If problems will be detected, we can abandon the change and mark this bug report as invalid.
Also:
Functional tests in integration mode can be accelerated too up to 7x times.
As you may see class attribute "server" is not actually reusable. The server is terminated after each test case execution:
see: https://github.com/openstack/zaqar/blob/master/zaqar/tests/functional/base.py#L91
But there's a problem. When I make it reusable, 8 tests out of 219 fail - few tests in "TestPools" and "TestHealth" classes.
These tests must be adapted to make them work with reusable "server" if we want to accelerate functional tests in integration mode.
I can open separate bug report/change for this. |
|
| 2015-11-15 12:36:59 |
Eva Balycheva |
description |
Currently functional test base class "zaqar.tests.functional.base.FunctionalTestBase" is written to recreate Bootstrap object and to open/close database connections on each execution of setUp(self) method.
Functional test base class "zaqar.tests.functional.base.FunctionalTestBase" can be modified to make these things reusable across all test cases of each particular subclass of it.
I tried it and it makes functional tests execution in non-integration mode up to 4-5x times faster! 20 seconds vs 5 seconds. I haven't detected any problems.
I can propose a change so you can test it yourself. If problems will be detected, we can abandon the change and mark this bug report as invalid.
Also:
Functional tests in integration mode can be accelerated too up to 7x times.
As you may see class attribute "server" is not actually reusable. The server is terminated after each test case execution:
see: https://github.com/openstack/zaqar/blob/master/zaqar/tests/functional/base.py#L91
But there's a problem. When I make it reusable, 8 tests out of 219 fail - few tests in "TestPools" and "TestHealth" classes.
These tests must be adapted to make them work with reusable "server" if we want to accelerate functional tests in integration mode.
I can open separate bug report/change for this. |
Currently functional test base class "zaqar.tests.functional.base.FunctionalTestBase" is written to recreate Bootstrap object and to open/close database connections on each execution of setUp(self) method.
Functional test base class "FunctionalTestBase" can be modified to make these things reusable across all test cases of each particular subclass of it.
I tried it and it makes functional tests execution in non-integration mode up to 4-5x times faster! 20 seconds vs 5 seconds. I haven't detected any problems.
I can propose a change so you can test it yourself. If problems will be detected, we can abandon the change and mark this bug report as invalid.
Also:
Functional tests in integration mode can be accelerated too up to 7x times.
As you may see class attribute "server" is not actually reusable. The server is terminated after each test case execution:
see: https://github.com/openstack/zaqar/blob/master/zaqar/tests/functional/base.py#L91
But there's a problem. When I make it reusable, 8 tests out of 219 fail - few tests in "TestPools" and "TestHealth" classes.
These tests must be adapted to make them work with reusable "server" if we want to accelerate functional tests in integration mode.
I can open separate bug report/change for this. |
|
| 2015-11-15 19:59:30 |
Eva Balycheva |
description |
Currently functional test base class "zaqar.tests.functional.base.FunctionalTestBase" is written to recreate Bootstrap object and to open/close database connections on each execution of setUp(self) method.
Functional test base class "FunctionalTestBase" can be modified to make these things reusable across all test cases of each particular subclass of it.
I tried it and it makes functional tests execution in non-integration mode up to 4-5x times faster! 20 seconds vs 5 seconds. I haven't detected any problems.
I can propose a change so you can test it yourself. If problems will be detected, we can abandon the change and mark this bug report as invalid.
Also:
Functional tests in integration mode can be accelerated too up to 7x times.
As you may see class attribute "server" is not actually reusable. The server is terminated after each test case execution:
see: https://github.com/openstack/zaqar/blob/master/zaqar/tests/functional/base.py#L91
But there's a problem. When I make it reusable, 8 tests out of 219 fail - few tests in "TestPools" and "TestHealth" classes.
These tests must be adapted to make them work with reusable "server" if we want to accelerate functional tests in integration mode.
I can open separate bug report/change for this. |
Currently functional test base class "zaqar.tests.functional.base.FunctionalTestBase" is written to recreate Bootstrap object and to open/close database connections on each execution of setUp(self) method.
Functional test base class "FunctionalTestBase" can be modified to make these things reusable across all test cases of each particular subclass of it.
I tried it and it makes functional tests execution in non-integration mode up to 4-5x times faster! 20 seconds vs 5 seconds on my machine. I haven't detected any problems.
I can propose a change so you can test it yourself. If problems will be detected, we can abandon the change and mark this bug report as invalid.
Also:
Functional tests in integration mode can be accelerated too up to 7x times. On my machine it's 235 seconds vs 35 seconds.
As you may see class attribute "server" is not actually reusable. The server is terminated after each test class's test case execution:
see: https://github.com/openstack/zaqar/blob/master/zaqar/tests/functional/base.py#L91
But there's a problem. When I make it reusable, 8 tests out of 219 fail - few tests in "TestPools" and "TestHealth" classes.
These tests must be adapted to make them work with reusable "server" if we want to accelerate functional tests in integration mode.
I can open separate bug report/change for this. |
|
