Kaydet (Commit) e15807f4 authored tarafından Noel Grandin's avatar Noel Grandin

java: nothing is passing in a "ComplexIni" parameter

Change-Id: Iae7530a52eda020f9074a6de0ef9e4b9779593f6
üst 04e26ca2
......@@ -45,14 +45,6 @@ public class java_complex implements TestBase
public boolean executeTest(TestParameters param)
{
// is there an ini file for the complex tests defined?
String complexIniFileName = ((String) param.get("ComplexIni"));
if (complexIniFileName != null)
{
CfgParser ini = new CfgParser(complexIniFileName);
ini.getIniParameters(param);
}
// get the test job
String testJob = ((String) param.get("TestJob"));
......@@ -69,25 +61,17 @@ public class java_complex implements TestBase
*/
public boolean executeTest(TestParameters param, DescEntry[] entries)
{
// is there an ini file for the complex tests defined?
String complexIniFileName = ((String) param.get("ComplexIni"));
if (complexIniFileName != null)
{
CfgParser ini = new CfgParser(complexIniFileName);
ini.getIniParameters(param);
}
DynamicClassLoader dcl = new DynamicClassLoader();
ComplexTestCase testClass = null;
boolean returnVal = true;
// the concept of the TimeOut depends on runner logs. If the runner log,
// for example to start a test method, the timeout was reset. This is not
// while the test itself log something like "open docuent...".
// while the test itself log something like "open document...".
// An property of complex test could be that it have only one test method
// which works for serveral minutes. Ih this case the TimeOut get not trigger
// which works for several minutes. In this case the TimeOut get not trigger
// and the office was killed.
// In complex tests just use "ThreadTimeOut" as timout.
// In complex tests just use "ThreadTimeOut" as timeout.
for (int i = 0; i < entries.length; i++)
{
......
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