SigComp torture test naming inconsistent

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Running of torture tests or visual inspection of test_tortures.h
2.
3.

What is the expected output? What do you see instead?
Expect naming convention for tests to be consistent

What version of the product are you using? On what operating system?
2.0.132.811

Please provide any additional information below.

With recent changes to tortures tests the test title naming convention is no 
longer consistent.

For example

A.1.5.(1)   LOAD and MULTILOAD
A.1.5.(2)   LOAD and MULTILOAD
etc.

A.1.15.   State Creation_1
A.1.15.   State Creation_2
etc.

The above are examples only the pattern of mixed naming is continued elsewhere 
in the torture tests.

Original issue reported on code.google.com by alistair...@gmail.com on 4 Feb 2013 at 2:52

[GoogleCodeExporter]

Original comment by boss...@yahoo.fr on 5 Feb 2013 at 4:55

• Changed state: Accepted
• Added labels: SigComp

[GoogleCodeExporter]

What do you expect?

Original comment by boss...@yahoo.fr on 6 Feb 2013 at 9:47

[GoogleCodeExporter]

I do not have a strong preference other than using the same naming convention 
for each test.

I personally think that A.x.y.(1) is clearer.

Original comment by alistair...@gmail.com on 6 Feb 2013 at 10:58

[GoogleCodeExporter]

Original comment by boss...@yahoo.fr on 6 Feb 2013 at 11:11

• Changed state: NextRelease

[GoogleCodeExporter]

Fixed by r814

Original comment by boss...@yahoo.fr on 6 Feb 2013 at 12:10

• Changed state: Fixed