Commit 65b7c937 authored by Jérome Perrin's avatar Jérome Perrin

test result: create test results line in same order

This is in order for tests to have the same id on each test run
parent 30066147
......@@ -302,8 +302,8 @@ class TestTaskDistribution(ERP5TypeTestCase):
line_url, test = self.tool.startUnitTest(test_result_path)
next_line_url, next_test = self.tool.startUnitTest(test_result_path)
# first launch, we have no time optimisations, so tests are
# launched in the given order
self.assertEqual(['testFoo', 'testBar'], [test, next_test])
# launched in alphabetical order
self.assertEqual(['testBar', 'testFoo'], [test, next_test])
status_dict = {}
self.tool.stopUnitTest(line_url, status_dict)
self.tool.stopUnitTest(next_line_url, status_dict)
......@@ -318,7 +318,7 @@ class TestTaskDistribution(ERP5TypeTestCase):
# Make sure second test takes more time
next_line.duration = line.duration + 1
# So if we launch another unit test, it will process first the
# one wich is the slowest
# one which is the slowest
self.assertEqual("stopped", test_result.getSimulationState())
next_test_result_path, revision = self._createTestResult(
......@@ -326,7 +326,7 @@ class TestTaskDistribution(ERP5TypeTestCase):
self.assertNotEquals(next_test_result_path, test_result_path)
line_url, test = self.tool.startUnitTest(next_test_result_path)
next_line_url, next_test = self.tool.startUnitTest(next_test_result_path)
self.assertEqual(['testBar', 'testFoo'], [test, next_test])
self.assertEqual(['testFoo', 'testBar'], [test, next_test])
def test_07_reportTaskFailure(self):
test_result_path, revision = self._createTestResult(node_title="Node0")
......@@ -102,7 +102,9 @@ class TaskDistributionTool(BaseTool):
duration_list.sort(key=lambda x: -x[1])
sorted_test_list = [x[0] for x in duration_list]
for test_name in test_name_list:
# Sort tests by name to have consistent numbering of test result line on
# a test suite.
for test_name in sorted(test_name_list):
index = 0
if sorted_test_list:
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment