Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.12.0
-
Fix Version/s: None
-
Component/s: Test suite
-
Labels:None
Description
Jalview test suite logic is not quite correct for the testTask...n sets which were introduced to avoid deadlocks.
However, when 'gradle test' is run without any additional arguments we only want 'Functional' tests to run - not 'Network' tests (or any others..).
see e.g. :
jalview.bin.CommandsTest2:
@Test(
groups =
{ "Network", "testTask1" },
dataProvider = "structureOpeningArgsNetworkParams",
singleThreaded = true)
public void do_network_structureOpeningArgsTest(String cmdLine,
int seqNum, int annNum, int pdbPerSeqNum, int viewerNum)
which is being run as part of regular CI builds but shouldn't be.
However, when 'gradle test' is run without any additional arguments we only want 'Functional' tests to run - not 'Network' tests (or any others..).
see e.g. :
jalview.bin.CommandsTest2:
@Test(
groups =
{ "Network", "testTask1" },
dataProvider = "structureOpeningArgsNetworkParams",
singleThreaded = true)
public void do_network_structureOpeningArgsTest(String cmdLine,
int seqNum, int annNum, int pdbPerSeqNum, int viewerNum)
which is being run as part of regular CI builds but shouldn't be.