[jbossts-issues] [JBoss JIRA] (JBTM-1986) There are some redundant QA crash recovery tests

[Michael Musgrove (JIRA)]

     [ https://issues.jboss.org/browse/JBTM-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove resolved JBTM-1986.
------------------------------------

    Resolution: Won't Fix


Although there is redundancy amongst clients the only way to check for redundancy amongst the crash rec tests as a whole is to ensure that all phases of a test are duplicated: ie the servers and client in the crash phase 1 need to be checked for duplicates and then the servers and client in phase 2 need to be checked. Checking both these would be laborious and since there is no harm in the  occasional duplicate there is no real gain in cleaning up any potential (theoretical) redundancy.
                
> There are some redundant QA crash recovery tests
> ------------------------------------------------
>
>                 Key: JBTM-1986
>                 URL: https://issues.jboss.org/browse/JBTM-1986
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Testing
>    Affects Versions: 5.0.0.M6
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>            Priority: Minor
>             Fix For: 6.0.0.Final
>
>
> I notice that there are some test duplicates in the org.jboss.jbossts.qa.CrashRecovery05Clients1.CrashRecovery05Clients1 group. I did not check any of the other groups so the assignee should also check those too. It is also worth checking whether the duplicates can be tweaked to test a scenario not covered by any of the other tests in the group.
> The duplicates are: 
> - CrashRecovery05Clients1.Client01a and CrashRecovery05Clients1.Client02a 
> - CrashRecovery05Clients1.Client03a, CrashRecovery05Clients1.Client04a and CrashRecovery05Clients1.Client05a

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira